Upgrading Load Balancer from Basic to Standard SKU

PD 0 Reputation points
2025-07-15T09:31:00.8733333+00:00

An internal load balancer currently uses a basic SKU and needs to be upgraded to a standard SKU without changing the private IP address. One approach considered is to create a new standard SKU internal load balancer with a temporary private IP, delete the existing basic ILB, and then redeploy the standard SKU ILB using the original private IP once it is released. What are other recommended approaches that align with best practices for this upgrade?

Additionally, while running validate-only mode of migration, an error occurs stating that backend pool VMs of a basic SKU external load balancer are part of an availability set. What are the options for this migration?

Azure Load Balancer
Azure Load Balancer
An Azure service that delivers high availability and network performance to applications.
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Obinna Ejidike 2,855 Reputation points
    2025-07-15T11:21:20.5233333+00:00

    Hi Pooja Dahivalkar

    Thanks for using the Q&A platform.

    Upgrading from Basic to Standard SKU Load Balancer in Azure is not a direct in-place upgrade; it requires recreating the resource with the desired SKU. However, preserving the same private IP and minimizing downtime are key challenges.

    The first approach would be to deploy a new Standard SKU ILB with a temporary private IP. Migrate backend pools and health probes, delete the old Basic SKU ILB to release the original IP, and create a new Standard SKU ILB again using the original IP.

    Another approach, if backend VMs support it, is to use an additional NIC or a temporary IP. Register this with the Standard ILB backend pool, gradually move traffic to Standard ILB, and once cutover is complete, decommission the Basic ILB and reuse the IP.

    Regarding the validate-only error, you will need to consolidate VMs into the same availability set if possible, recreate VMs in a Virtual Machine Scale Set (VMSS) for compatibility, and use individual NIC-based backend pool configuration.

    Find additional documentation:
    https://learn.microsoft.com/en-us/azure/load-balancer/skus#backend-pool-configuration
    https://learn.microsoft.com/en-us/azure/load-balancer/upgrade-basic-standard-with-powershell

    If the response was helpful, please feel free to mark it as “Accepted Answer” and consider giving it an upvote. This also benefits others in the community.

    Regards,

    Obinna.


Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.