Skip to content

Commit 394e052

Browse files
authored
Merge pull request #306694 from aybatra/patch-40
Revise VPN gateway SKU deprecation FAQ
2 parents ca2de26 + 5d4dbdb commit 394e052

1 file changed

Lines changed: 9 additions & 26 deletions

File tree

Lines changed: 9 additions & 26 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
ms.author: cherylmc
33
author: cherylmc
4-
ms.date: 06/23/2025
4+
ms.date: 10/08/2025
55
ms.service: azure-vpn-gateway
66
ms.topic: include
77
---
@@ -12,43 +12,26 @@ No. As of December 1, 2023, you can't create gateways that use Standard or High
1212

1313
### How long will my existing gateways be supported on the Standard and High Performance SKUs?
1414

15-
All existing gateways that use the Standard or High Performance SKU will be supported until September 30, 2025.
15+
All existing gateways that use the Standard or High Performance SKU will be supported until February 28, 2026 (extended from initial September 30, 2025 timeline).
1616

17-
### Will my IP address change when my Legacy VPN gateway SKU (Standard or HighPerformance) is migrated to a Non-AZ SKU (VpnGw1 or VpnGw2)?
17+
### Will my IP address change when my Legacy VPN gateway SKU (Standard or HighPerformance) is migrated as part of Basic IP address migration initiated through Azure portal?
1818

19-
No, the IP address will not change when the Legacy SKU is migrated to a Non-AZ SKU. After SKU migration, you can choose to migrate the Basic SKU IP address to Standard SKU IP address through a customer controlled portal experience. For more information about Basic SKU IP migration, see [About migrating a Basic SKU public IP address to Standard SKU for VPN Gateway](../articles/vpn-gateway/basic-public-ip-migrate-about.md) article.
19+
No, the IP address won't change when you migrate Basic IP using Azure portal experience. You can choose to migrate the Basic SKU IP address to Standard SKU IP address through a customer controlled portal experience. For more information about Basic SKU IP migration, see [About migrating a Basic SKU public IP address to Standard SKU for VPN Gateway](../articles/vpn-gateway/basic-public-ip-migrate-about.md) article.
2020

2121
### Do I need to migrate my gateways from the Standard or High Performance SKU right now?
2222

23-
No, there's no action required right now. You can migrate your gateways starting in December 2024. We'll send communication with detailed documentation about the migration steps.
23+
No, you're required to migrate the Basic IP address on your gateway using the portal experience if you want to retain the IP address. As part of this migration, your gateways are automatically migrated to AZ SKUs.
2424

25-
### Which SKU can I migrate my gateway to?
26-
27-
When gateway SKU migration becomes available, SKUs can be migrated as follows:
28-
29-
* Standard to VpnGw1
30-
* High Performance to VpnGw2
31-
32-
### What if I want to migrate to an AZ SKU?
33-
34-
You can't migrate your deprecated SKU to an AZ SKU. However, all gateways that are still using the Standard or High Performance SKU after September 30, 2025, will be migrated and upgraded automatically to the AZ SKUs as follows:
35-
36-
* Standard to VpnGw1AZ
37-
* High Performance to VpnGw2AZ
38-
39-
You can use this strategy to have your SKUs automatically migrated and upgraded to an AZ SKU. You can then resize your SKU within that SKU family if necessary. For AZ SKU pricing, see the [pricing page](https://azure.microsoft.com/pricing/details/vpn-gateway/). For throughput information by SKU, see [About gateway SKUs](https://go.microsoft.com/fwlink/?linkid=2256302).
4025

4126
### Will there be any pricing difference for my gateways after migration?
4227

43-
If you migrate your SKUs by September 30, 2025, there will be no pricing difference. VpnGw1 and VpnGw2 SKUs are offered at the same price as Standard and High Performance SKUs, respectively.
44-
45-
If you don't migrate by that date, your SKUs will automatically be migrated and upgraded to AZ SKUs. In that case, there's a pricing difference.
28+
Your SKUs are automatically migrated and upgraded to AZ SKUs as part of Basic IP migration. See [VPN Gateway pricing](https://azure.microsoft.com/pricing/details/vpn-gateway/) for more details.
4629

4730
### Will there be any performance impact on my gateways with this migration?
4831

49-
Yes. You get better performance with VpnGw1 and VpnGw2. Currently, VpnGw1 at 650 Mbps provides a 6.5x performance improvement at the same price as the Standard SKU. VpnGw2 at 1 Gbps provides a 5x performance improvement at the same price as the High Performance SKU. For more information about SKU throughput, see [About gateway SKUs](https://go.microsoft.com/fwlink/?linkid=2256302).
32+
Yes. You get better performance with VpnGw1AZ and VpnGw2AZ. For more information about SKU throughput, see [About gateway SKUs](https://go.microsoft.com/fwlink/?linkid=2256302).
5033

51-
### What happens if I don't migrate by September 30, 2025?
34+
### What happens if I don't migrate by February 28, 2026?
5235

5336
All gateways that still use the Standard or High Performance SKU will be migrated automatically and upgraded to the following AZ SKUs:
5437

@@ -59,6 +42,6 @@ We'll send communication before initiating migration on any gateways.
5942

6043
### Is the VPN Gateway Basic SKU also retiring?
6144

62-
No, the VPN Gateway Basic SKU is not retiring. You can create a VPN gateway by using the Basic SKU via Azure PowerShell or the Azure CLI.
45+
No, the VPN Gateway Basic SKU isn't retiring. You can create a VPN gateway by using the Basic SKU via Azure PowerShell or the Azure CLI.
6346

6447
Currently, the VPN Gateway Basic SKU supports only the Basic SKU public IP address resource (which is on a path to retirement). We're working on adding support for the Standard SKU public IP address resource to the VPN Gateway Basic SKU.

0 commit comments

Comments
 (0)