VPN Gateway

Schulz, James 10 Reputation points
2026-08-31T15:13:31.9766667+00:00

Will my VpnGw1 be automatically updated to VpnGw1AZ if I do nothing. It is a /27 network and is already using a standard IP.

Azure VPN Gateway
Azure VPN Gateway

An Azure service that enables the connection of on-premises networks to Azure through site-to-site virtual private networks.

0 comments

2 answers

Sort by: Newest
Most helpful Newest Oldest
  1. TP 163.1K Reputation points Volunteer Moderator
    2026-08-31T15:36:36.72+00:00

    Hi James,

    According to the Azure Update vpngw1-5-non-az-skus-will-be-retired-on-30-september-2026, VpnGw1-5 will be automatically updated by September 30, 2026. Screenshot excerpt below:

    User's image

    At the same time, the FAQ recommends you manually upgrade your SKU to AZ SKU. You shouldn't have downtime since you already have Standard IP and are just moving to AZ-capable SKU. Excerpt from FAQ below:

    What actions do I need to take?

    • We recommend that you manually upgrade gateway SKUs that aren't supported by availability zones to those that are. You can use the Azure portal, PowerShell, or the Azure CLI. There's no downtime expected to manually upgrade SKUs that currently use Standard public IP addresses. If you're still using a Basic IP address, upgrade to a Standard IP address.
    • If your gateway currently uses legacy SKUs, see Working with VPN Gateway legacy SKUs.

    My recommendation is to go ahead and manually upgrade during off hours before the deadline.

    Please click Accept Answer and upvote if the above was helpful.

    Thanks.

    -TP

    Was this answer helpful?

    0 comments

  2. AI answer

    2026-08-31T15:13:45.6066667+00:00

    Yes. If the gateway is already on VpnGw1 and already uses a Standard public IP, no customer action is required. It will be automatically upgraded to Generation 2 as part of regular service updates, and for non-AZ SKUs such as VpnGw1, the migration to the corresponding AZ SKU is described as seamless with no expected downtime.

    The /27 gateway subnet detail is relevant because automatic migration can fail if there are constraints such as insufficient subnet size. Since the subnet is already /27, that specific constraint is already satisfied based on the migration guidance.

    If the gateway were changed manually from VpnGw1 to VpnGw1AZ through a SKU change, documentation says that moving to a new SKU can cause downtime. Waiting for the automatic migration avoids that expected manual migration impact.

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

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