VPN Gateway non-AZ SKUs (VpnGw 1–5) will be retired on 30 September 2026

Question

Timo Keuning 20

Hello,

For our Azure environment, we've received a Retirement reminder for VPN Gateway non-AZ SKUs (vpnGw 1-5).

Currently we are using VpnGw1 and need to migrate to VpnGw1AZ. The gateway is already using a standard SKU Public IP.

Reading some documentation, switching from VpnGw1 -> VpnGw1AZ manually, will cause some downtime.

Is it correct we can just wait until it is migrated automatically by Microsoft and we will have no expected downtime?

Many thanks in advance.

Best regards,

Timo Keuning

0 comments

Answer accepted by question author

0 additional answers

Answer 1

Sindhuja Dasari 2,115 Microsoft External Staff Moderator

Thank you for reaching out regarding the VPN Gateway SKU retirement.

There are no actions required from your end. Microsoft will automatically migrate your existing non‑AZ SKU to the corresponding AZ SKU as part of the retirement process.
The migration is designed to be seamless with no expected downtime, and you will be notified in advance before the migration takes place.
As per current guidance, it is recommended not to manually change the SKU in anticipation of this migration unless you intend to upgrade to a higher SKU.

Pleaseand “up-vote” wherever the information provided helps you, **this can be beneficial to other community members.

veli anlama 5 Reputation points

2026-07-06T08:20:37.19+00:00

The documentation states explicitly and unconditionally: "We recommend that you manually upgrade gateway SKUs that aren't supported by availability zones to those that are." Microsoft put this guidance in writing because they want enterprise environments to transition on their own terms.