Skip to content

Commit 48a03ed

Browse files
aybatraaybatra
authored
Update legacy VPN gateway SKU details and migration info
Updated the deprecation date for Standard and High Performance SKUs and clarified migration details. Removed outdated information and streamlined content for better clarity.
1 parent 9abeb8f commit 48a03ed

1 file changed

Lines changed: 5 additions & 42 deletions

File tree

‎articles/vpn-gateway/vpn-gateway-about-skus-legacy.md‎

Lines changed: 5 additions & 42 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: How to work with the old virtual network gateway SKUs, called Stand
44
author: cherylmc
55
ms.service: azure-vpn-gateway
66
ms.topic: how-to
7-
ms.date: 10/8/2025
7+
ms.date: 2/27/2026
88
ms.author: cherylmc
99
# Customer intent: As a network administrator, I want to manage legacy VPN gateway SKUs so that I can ensure continuity of service and plan for the upcoming deprecation of these SKUs before the migration deadline.
1010
---
@@ -18,8 +18,6 @@ For information about the new SKUs, see [About VPN Gateway](vpn-gateway-about-vp
1818

1919
[!INCLUDE [Legacy gateway SKUs](../../includes/vpn-gateway-gwsku-legacy-include.md)]
2020

21-
You can view legacy gateway pricing on the [Azure ExpressRoute pricing page](https://azure.microsoft.com/pricing/details/expressroute). Select the **ExpressRoute Gateways** tab, and refer to the table in the **Virtual Network Gateways** section.
22-
2321
For SKU deprecation, see the [SKU deprecation](#sku-deprecation) and [FAQs](#sku-deprecation-faqs) sections of this article.
2422

2523
## <a name="agg"></a>Estimated aggregate throughput by SKU
@@ -28,8 +26,6 @@ The following table shows the gateway types and the estimated aggregate throughp
2826

2927
Pricing differs between gateway SKUs. For more information, see [VPN Gateway pricing](https://azure.microsoft.com/pricing/details/vpn-gateway).
3028

31-
The Ultra Performance gateway SKU isn't represented in this table. For information about the Ultra Performance SKU, see the [ExpressRoute](../expressroute/expressroute-about-virtual-network-gateways.md) documentation.
32-
3329
| SKU | VPN Gateway throughput (1) | VPN Gateway max IPsec tunnels (2) | ExpressRoute Gateway throughput | VPN Gateway and ExpressRoute coexist |
3430
| --- | --- | --- | --- | --- |
3531
| Standard SKU (3)(4) | 100 Mbps | 10 | 1,000 Mbps | Yes |
@@ -47,55 +43,22 @@ The Ultra Performance gateway SKU isn't represented in this table. For informati
4743

4844
[!INCLUDE [Table requirements for old SKUs](../../includes/vpn-gateway-table-requirements-legacy-sku-include.md)]
4945

50-
## Move to another gateway SKU
51-
52-
Consider the following points if you want to move to another gateway SKU:
53-
54-
* You can't upgrade a legacy SKU to one of the newer VPN Gateway SKUs (such as VpnGw1AZ or VpnGw2AZ). To use a new SKU, you must delete the gateway, and then create a new one.
55-
* When you go from a legacy SKU to a newer SKU, you incur connectivity downtime.
56-
* When you go from a legacy SKU to a newer SKU, the public IP address for your VPN gateway changes. The IP address change happens even if you specified the same public IP address object that you used previously.
57-
* If you have a classic VPN gateway, you must continue using the older legacy SKUs for that gateway. However, you can upgrade between the legacy SKUs available for classic gateways. You can't change to the new SKUs.
58-
* Standard and High Performance legacy SKUs are being deprecated. See [Legacy SKU deprecation](vpn-gateway-about-skus-legacy.md#sku-deprecation) for SKU migration and upgrade timelines.
59-
60-
### <a name="migrate"></a>Migrate a gateway SKU
61-
62-
As part of Basic IP address migration, your legacy SKU will be migrated to a newer SKU that's supported by availability zones. All legacy SKUs use Basic IP today, and you can use the Azure portal to [migrate a Basic IP address to a Standard IP address](basic-public-ip-migrate-about.md) before the retirement date. For the most up-to-date timeline, see [What's new in Azure VPN Gateway?](whats-new.md).
63-
64-
### <a name="resize"></a>Upgrade to a gateway SKU in the same SKU family
65-
66-
For legacy gateway SKUs, there are limitations. You can only upgrade your gateway to a gateway SKU within the same SKU family (except for the Basic SKU).
67-
68-
For example, if you have a Standard SKU, you can upgrade to a High Performance SKU. However, you can't upgrade your VPN gateway between the old SKUs and the new SKU families.
69-
70-
You can upgrade a gateway for the [Resource Manager deployment model](../azure-resource-manager/management/deployment-models.md) by using the Azure portal or PowerShell. For PowerShell, use the following command:
71-
72-
```powershell
73-
$gw = Get-AzVirtualNetworkGateway -Name vnetgw1 -ResourceGroupName testrg
74-
Resize-AzVirtualNetworkGateway -VirtualNetworkGateway $gw -GatewaySku HighPerformance
75-
```
76-
77-
To upgrade a gateway for the [classic deployment model](../azure-resource-manager/management/deployment-models.md), you must use the Service Management PowerShell cmdlets. Use the following command:
78-
79-
```powershell
80-
Resize-AzureVirtualNetworkGateway -GatewayId <Gateway ID> -GatewaySKU HighPerformance
81-
```
82-
83-
### <a name="change"></a>Change to the new gateway SKUs
46+
### <a name="change"></a> Move to a new gateway SKUs
8447

85-
Standard and High Performance SKUs will be deprecated on March 31, 2026. The product team will migrate the legacy SKUs. For more information, see the [Legacy SKU deprecation](#sku-deprecation) section. You can choose to change from a legacy SKU to one of the new SKUs at any point. However, changing to a new SKU requires more steps than migrating and incurs downtime.
48+
Standard and High Performance SKUs will be deprecated on March 31, 2026. All legacy SKUs use Basic IP address today, and we recommend you use the Azure portal to [migrate a Basic IP address to a Standard IP address](basic-public-ip-migrate-about.md) before the retirement date. As part of Basic IP address migration, your legacy SKU will also be migrated to a newer SKU that's supported by availability zones. For more information, see the [Legacy SKU deprecation](#sku-deprecation) section. For the most up-to-date timeline, see [What's new in Azure VPN Gateway?](whats-new.md).
8649

8750
[!INCLUDE [Change to the new SKUs](../../includes/vpn-gateway-gwsku-change-legacy-sku-include.md)]
8851

8952
## SKU deprecation
9053

91-
The Standard and High Performance SKUs will be deprecated on March 31, 2026. Your legacy SKU will be migrated to a SKU supported by an availability zone as part of Basic IP address migration. All legacy SKUs use Basic IP addresses today, and you can use the Azure portal to [migrate a Basic IP address to a Standard IP address](basic-public-ip-migrate-about.md) before the retirement date.
54+
The Standard and High Performance SKUs will be deprecated on March 31, 2026. All legacy SKUs use Basic IP addresses today, and you can use the Azure portal to [migrate a Basic IP address to a Standard IP address](basic-public-ip-migrate-about.md) before the retirement date. As part of Basic IP migration, your legacy SKU will also be migrated to AZ SKU family.
9255

9356
For more information, you can:
9457

9558
* View the [announcement](https://go.microsoft.com/fwlink/?linkid=2255127).
9659
* See the SKU deprecation [FAQs](#sku-deprecation-faqs).
9760

98-
When the migration path becomes available, as part of Basic IP address migration, your gateway SKU will automatically migrate to the following SKUs:
61+
With the current Basic IP address migration tool, your gateway SKU will automatically migrate to the following SKUs:
9962

10063
* Standard SKU becomes VpnGw1AZ.
10164
* High Performance SKU becomes VpnGw2AZ.

0 commit comments

Comments
 (0)