Merge pull request #259597 from cherylmc/legacy

v-dirichards · web-flow · commit 17be1f9104c4 · 2023-11-28T16:50:08.000-06:00
SKU notes
diff --git a/articles/vpn-gateway/about-gateway-skus.md b/articles/vpn-gateway/about-gateway-skus.md
@@ -4,7 +4,7 @@ description: Learn about VPN Gateway SKUs.
 author: cherylmc
 ms.service: vpn-gateway
 ms.topic: conceptual
-ms.date: 11/20/2023
+ms.date: 11/28/2023
 ms.author: cherylmc 
 
 ---
@@ -88,7 +88,7 @@ If you're using the old SKUs (legacy), the production SKU recommendations are St
 
 ## About legacy SKUs
 
-For information about working with the legacy gateway SKUs (Basic, Standard, and HighPerformance), see [Working with VPN gateway SKUs (legacy SKUs)](vpn-gateway-about-skus-legacy.md).
+For information about working with the legacy gateway SKUs (Basic, Standard, and High Performance), including SKU deprecation, see [Managing legacy gateway SKUs](vpn-gateway-about-skus-legacy.md).
 
 ## Specify a SKU
 
@@ -101,7 +101,7 @@ You specify the gateway SKU when you create your VPN Gateway. See the following
 ## <a name="resizechange"></a>Change or resize a SKU
 
 > [!NOTE]
-> If you are working with a legacy gateway SKU and are using the classic deployment model (Service Management), the SKU rules are different. See [Working with legacy classic deployment model SKUs](vpn-gateway-about-skus-legacy.md).
+> If you're working with a legacy gateway SKU (Basic, Standard, and High Performance), see [Managing Legacy gateway SKUs](vpn-gateway-about-skus-legacy.md).
 
 [!INCLUDE [changing vs. resizing](../../includes/vpn-gateway-sku-about-change-resize.md)]
 
diff --git a/articles/vpn-gateway/vpn-gateway-about-skus-legacy.md b/articles/vpn-gateway/vpn-gateway-about-skus-legacy.md
@@ -1,10 +1,10 @@
 ---
 title: Legacy Azure virtual network VPN gateway SKUs
-description: How to work with the old virtual network gateway SKUs; Basic, Standard, and HighPerformance.
+description: How to work with the old virtual network gateway SKUs; Basic, Standard, and High Performance.
 author: cherylmc
 ms.service: vpn-gateway
 ms.topic: article
-ms.date: 02/13/2023
+ms.date: 11/28/2023
 ms.author: cherylmc 
 ---
 # Working with virtual network gateway SKUs (legacy SKUs)
@@ -17,6 +17,23 @@ This article contains information about the legacy (old) virtual network gateway
 
 You can view legacy gateway pricing in the **Virtual Network Gateways** section, which is located in on the [ExpressRoute pricing page](https://azure.microsoft.com/pricing/details/expressroute).
 
+## SKU deprecation
+
+The Standard and High Performance SKUs will be deprecated September 30, 2025. The product team will make a migration path available for these SKUs by November 30, 2024. **At this time, there's no action that you need to take**.
+
+There are no [price](https://azure.microsoft.com/pricing/details/vpn-gateway/) changes if you migrate to Standard (VpnGw1) and High Performance (VpnGw2) gateways. As a benefit, there's a performance improvement after migrating:
+
+* **Standard** 6.5x
+* **High Performance** 5x
+
+If you don't migrate your gateway by September 30, 2025, your gateway will be automatically upgraded to AZ gateways: VpnGw1AZ (Standard) or VpnGw2AZ (High Performance).
+
+Important Dates:
+
+* **December 1, 2023**: No new gateway creations possible on Standard / High Performance SKUs
+* **November 30, 2024**: Begin migrating gateways to other SKUs
+* **September 30, 2025**: Standard/High Performance SKUs will be retired and gateways will be automatically migrated
+
 ## <a name="agg"></a>Estimated aggregate throughput by SKU
 
 [!INCLUDE [Aggregated throughput by legacy SKU](../../includes/vpn-gateway-table-gwtype-legacy-aggtput-include.md)]
@@ -27,29 +44,30 @@ You can view legacy gateway pricing in the **Virtual Network Gateways** section,
 
 ## <a name="resize"></a>Resize a gateway
 
-With the exception of the Basic SKU, you can resize your gateway to a gateway SKU within the same SKU family. For example, if you have a Standard SKU, you can resize to a HighPerformance SKU. However, you can't resize your VPN gateway between the old SKUs and the new SKU families. For example, you can't go from a Standard SKU to a VpnGw2 SKU, or a Basic SKU to VpnGw1.
+Except for the Basic SKU, you can resize your gateway to a gateway SKU within the same SKU family. For example, if you have a Standard SKU, you can resize to a High Performance SKU. However, you can't resize your VPN gateway between the old SKUs and the new SKU families. For example, you can't go from a Standard SKU to a VpnGw2 SKU, or a Basic SKU to VpnGw1.
 
 ### Resource Manager
 
-To resize a gateway for the [Resource Manager deployment model](../azure-resource-manager/management/deployment-models.md) using PowerShell, use the following command:
+You can resize a gateway for the [Resource Manager deployment model](../azure-resource-manager/management/deployment-models.md) using the Azure portal or PowerShell. For PowerShell, use the following command:
 
 ```powershell
 $gw = Get-AzVirtualNetworkGateway -Name vnetgw1 -ResourceGroupName testrg
 Resize-AzVirtualNetworkGateway -VirtualNetworkGateway $gw -GatewaySku HighPerformance
 ```
 
-You can also resize a gateway in the Azure portal.
-
 ### <a name="classicresize"></a>Classic
 
-To resize a gateway for the classic deployment model, you must use the Service Management PowerShell cmdlets. Use the following command:
+To resize 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:
 
 ```powershell
 Resize-AzureVirtualNetworkGateway -GatewayId <Gateway ID> -GatewaySKU HighPerformance
 ```
 
 ## <a name="change"></a>Change to the new gateway SKUs
 
+> [!NOTE]
+> Standard and High Performance SKUs will be deprecated September 30, 2025. While you can choose to change to the new gateway SKUs at any point, there is no requirement to do so at this time. The product team will make a migration path available for these SKUs by November 30, 2024. See [Legacy SKU deprecation](#sku-deprecation) for more information.
+
 [!INCLUDE [Change to the new SKUs](../../includes/vpn-gateway-gwsku-change-legacy-sku-include.md)]
 
 ## Next steps
diff --git a/includes/vpn-gateway-gwsku-change-legacy-sku-include.md b/includes/vpn-gateway-gwsku-change-legacy-sku-include.md
@@ -5,7 +5,7 @@
  author: cherylmc
  ms.service: vpn-gateway
  ms.topic: include
- ms.date: 04/07/2023
+ ms.date: 11/27/2023
  ms.author: cherylmc
  ms.custom: include file
 ---
@@ -27,4 +27,4 @@ Considerations:
 * To move to the new SKUs, your VPN gateway must be in the Resource Manager deployment model.
 * If you have a classic VPN gateway, you must continue using the older legacy SKUs for that gateway, however, you can resize between the legacy SKUs. You can't change to the new SKUs.
 * When you change from a legacy SKU to a new SKU, you'll have connectivity downtime.
-* When changing to a new gateway SKU, the public IP address for your VPN gateway changes. This happens even if you specify the same public IP address object that you used previously.
+* When changing to a new gateway SKU, the public IP address for your VPN gateway changes. This happens even if you specified the same public IP address object that you used previously.
diff --git a/includes/vpn-gateway-sku-about-change-resize.md b/includes/vpn-gateway-sku-about-change-resize.md
@@ -1,13 +1,13 @@
 ---
 author: cherylmc
 ms.author: cherylmc
-ms.date: 11/20/2023
+ms.date: 11/28/2023
 ms.service: vpn-gateway
 ms.topic: include
 ---
 
 When you want to move to another SKU, there are multiple methods to choose from. The method you choose depends on the gateway SKU that you're starting from. 
 
-* **Resize a SKU:** When you resize a SKU, you incur very little downtime. You don't need to follow a workflow to resize a SKU. You can resize a SKU quickly and easily in the Azure portal. Or, you can use PowerShell or the Azure CLI. You don't need to reconfigure your VPN device or your P2S clients.
+* **[Resize a SKU](../articles/vpn-gateway/gateway-sku-resize.md):** When you resize a SKU, you incur very little downtime. You don't need to follow a workflow to resize a SKU. You can resize a SKU quickly and easily in the Azure portal. Or, you can use PowerShell or the Azure CLI. You don't need to reconfigure your VPN device or your P2S clients.
 
-* **Change a SKU:** If you can't resize your SKU, you can change your SKU using a specific [Workflow](../articles/vpn-gateway/gateway-sku-change.md#workflow). Changing a SKU incurs more downtime than resizing. Additionally, there are multiple resources that need to be reconfigured when using this method.
+* **[Change a SKU](../articles/vpn-gateway/gateway-sku-change.md):** If you can't resize your SKU, you can change your SKU using a specific [Workflow](../articles/vpn-gateway/gateway-sku-change.md#workflow). Changing a SKU incurs more downtime than resizing. Additionally, there are multiple resources that need to be reconfigured when using this method.
diff --git a/includes/vpn-gateway-sku-resize-restrictions.md b/includes/vpn-gateway-sku-resize-restrictions.md
@@ -1,15 +1,16 @@
 ---
 author: cherylmc
 ms.author: cherylmc
-ms.date: 10/24/2023
+ms.date: 11/28/2023
 ms.service: vpn-gateway
 ms.topic: include
 ---
 
 * You can't resize to downgrade a SKU.
-* You can't resize a legacy SKU to one of the newer Azure SKUs (VpnGw1, VpnGw2AZ etc.) Legacy SKUs for the Resource Manager deployment model are: Basic, Standard, and HighPerformance.
+* You can't resize a legacy SKU to one of the newer Azure SKUs (VpnGw1, VpnGw2AZ etc.) Legacy SKUs for the Resource Manager deployment model are: Basic, Standard, and High Performance. You must instead, change the SKU.
 * You can resize a gateway SKU as long as it is in the same generation, except for the Basic SKU.
 * You can change a Basic SKU to another SKU.
 * When you change from a legacy SKU to a new SKU, you'll have connectivity downtime.
-* When you change to a new gateway SKU, the public IP address for your VPN gateway changes. This happens even if you specify the same public IP address object that you used previously.
+* When you change to a new gateway SKU, the public IP address for your VPN gateway changes. This happens even if you specified the same public IP address object that you used previously.
 * If you have a classic VPN gateway, you must continue using the older legacy SKUs for that gateway. However, you can resize between the legacy SKUs available for classic gateways. You can't change to the new SKUs.
+* Standard and High Performance legacy SKUs are being deprecated. See [Legacy SKU deprecation](../articles/vpn-gateway/vpn-gateway-about-skus-legacy.md#sku-deprecation) for SKU migration and upgrade timelines.
