An Azure service that enables the connection of on-premises networks to Azure through site-to-site virtual private networks.
Microsoft will automatically migrate your gateways with Standard Public IPs to AZ SKUs, but you must ensure your gateway subnet is at least /27 or larger. If your subnet is /28, the automated process will fail, and you will be forced to perform a manual migration.
The migration will include regions like South India that do not currently have Availability Zones. Microsoft is deploying AZ SKUs universally across all regions (even those without physical zones). More at https://learn.microsoft.com/en-us/azure/vpn-gateway/gateway-sku-consolidation
Can I deploy availability zone SKUs in all regions?
Yes. If a region doesn't currently support availability zones, you can still create VPN Gateway SKUs supported by availability zones, but the deployment will remain regional. When the region supports availability zones, we'll enable zone redundancy for the gateways.
If you do not migrate manually and your setup fails the automated requirements, your existing non-AZ gateways will likely experience connection disruptions after the September 30, 2026 deadline.
You can migrate from a legacy VpnGw1 directly to a higher tier like VpnGw2AZ, VpnGw3AZ, VpnGw4AZ, or VpnGw5AZ. The automatic tool maps to the direct equivalent (VpnGw1AZ), but you can manually upgrade to these higher performance tiers using the Azure Portal, PowerShell, or CLI.
If the above response helps answer your question, remember to "Accept Answer" so that others in the community facing similar issues can easily find the solution. Your contribution is highly appreciated.
hth
Marcin