Migrating to Azure VPN Load Balancer Standard SKU

Follow these steps to migrate from the Basic Azure VPN Load Balancer SKU to the Standard Azure VPN Load Balancer SKU. Azure is deprecating the Basic Load Balancer in September 2025.

Aviatrix recommends migrating when you need to replace your VPN gateway.

  1. In your Azure portal, search for "Load balancer" or "public IP addresses" and identify the Azure VPN Basic Load Balancers that need to be migrated.

    migrate lb sku
    migrate lb sku2

  1. In Aviatrix CoPilot, under Cloud Fabric > Use VPN > Users, identify the VPN users connected to the existing load balancer.

    migrate lb sku3
You can also check and detach the VPN users in the Aviatrix Controller under OpenVPN > Users. Remember that the Aviatrix Controller is being deprecated in 2025.

  1. Detach the VPN users from the associated VPN gateway.

    migrate lb sku4

  2. On the Cloud Fabric > UserVPN > VPN Gateways tab, delete the VPN gateway.

    migrate lb sku4a

    After all VPN users are detached from the associated VPN gateway, and the VPN gateway itself is deleted, this automatically deletes the Load Balancer from the Azure portal.

  1. In Aviatrix CoPilot, under Cloud Fabric > UserVPN > VPN Gateways, recreate the VPN gateway. This automatically creates a new Load Balancer in the Azure portal with a standard SKU.

    migrate lb sku4b

  2. On the Cloud Fabric > UserVPN > VPN Users tab, reattach the VPN users to the recreated VPN gateway.

    migrate lb sku5

  3. Reissue the certificate for the VPN users.

    migrate lb sku6

  4. For each VPN user, verify the VPN connectivity by trying to connect to the VPN Client.