You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/vpn-gateway/vpn-gateway-about-skus-legacy.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,7 +9,7 @@ ms.author: cherylmc
9
9
---
10
10
# Working with VPN Gateway legacy SKUs
11
11
12
-
This article contains information about the legacy (old) virtual network gateway SKUs. The legacy SKUs still work in both deployment models for VPN gateways that have already been created. Classic VPN gateways continue to use the legacy SKUs, both for existing gateways, and for new gateways. When creating new Resource Manager VPN gateways, use the new gateway SKUs. For information about the new SKUs, see [About VPN Gateway](vpn-gateway-about-vpngateways.md).
12
+
This article contains information about the legacy (old) virtual network gateway SKUs. The legacy SKUs still work in both deployment models for existing VPN gateways. Classic VPN gateways continue to use the legacy SKUs, both for existing gateways, and for new gateways. When creating new Resource Manager VPN gateways, use the new gateway SKUs. For information about the new SKUs, see [About VPN Gateway](vpn-gateway-about-vpngateways.md).
13
13
14
14
## <aname="gwsku"></a>Legacy gateway SKUs
15
15
@@ -29,8 +29,8 @@ The UltraPerformance gateway SKU isn't represented in this table. For informatio
29
29
30
30
||**VPN Gateway throughput (1)**|**VPN Gateway max IPsec tunnels (2)**|**ExpressRoute Gateway throughput**|**VPN Gateway and ExpressRoute coexist**|
(1) The VPN throughput is a rough estimate based on the measurements between VNets in the same Azure region. It isn't a guaranteed throughput for cross-premises connections across the Internet. It's the maximum possible throughput measurement.
36
36
@@ -75,7 +75,7 @@ A gateway SKU migration process is similar to a resize. It requires fewer steps
75
75
76
76
### <aname="change"></a>Change to the new gateway SKUs
77
77
78
-
Standard and High Performance SKUs will be deprecated September 30, 2025. The product team will make a migration path available for legacy SKUs. See the [Legacy SKU deprecation](#sku-deprecation) section for more information. 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 more downtime.
78
+
Standard and High Performance SKUs will be deprecated September 30, 2025. The product team will make a migration path available for 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.
79
79
80
80
[!INCLUDE [Change to the new SKUs](../../includes/vpn-gateway-gwsku-change-legacy-sku-include.md)]
81
81
@@ -96,7 +96,7 @@ There are no [price](https://azure.microsoft.com/pricing/details/vpn-gateway/) c
96
96
***Standard SKU:** 6.5x
97
97
***High Performance SKU:** 5x
98
98
99
-
Following this, your gateway will be automatically migrated and upgraded to an AZ gateway SKU:
99
+
As next steps, your gateway will be automatically migrated and upgraded to an AZ gateway SKU:
0 commit comments