Merge pull request #297098 from aybatra/patch-30

Standard and HighPerf dates change

Author: prmerger-automator[bot]

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

@@ -9,7 +9,7 @@ ms.author: cherylmc
 ---
 # Working with VPN Gateway legacy SKUs
 
-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).
+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).
 
 ## <a name="gwsku"></a>Legacy gateway SKUs
 
@@ -29,8 +29,8 @@ The UltraPerformance gateway SKU isn't represented in this table. For informatio
 
 |  | **VPN Gateway throughput (1)** | **VPN Gateway max IPsec tunnels (2)** | **ExpressRoute Gateway throughput** | **VPN Gateway and ExpressRoute coexist** |
 | --- | --- | --- | --- | --- |
-| **Standard SKU (3)(4)** |100 Mbps |10 |1000 Mbps |Yes |
-| **High Performance SKU (3)** |200 Mbps |30 |2000 Mbps |Yes |
+| **Standard SKU (3)(4)** |100 Mbps |10 |1,000 Mbps |Yes |
+| **High Performance SKU (3)** |200 Mbps |30 |2,000 Mbps |Yes |
 
 (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.
 
@@ -75,18 +75,18 @@ A gateway SKU migration process is similar to a resize. It requires fewer steps
 
 ### <a name="change"></a>Change to the new gateway SKUs
 
-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.
+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.
 
 [!INCLUDE [Change to the new SKUs](../../includes/vpn-gateway-gwsku-change-legacy-sku-include.md)]
 
 ## SKU deprecation
 
-The Standard and High Performance SKUs will be deprecated on 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**.
+The Standard and High Performance SKUs will be deprecated on September 30, 2025. The product team will do backend seamless migration for these SKUs starting June 2025. This is a change from originally announced November 2024 date **At this time, there's no action that you need to take**.
 
 * View the [Announcement](https://go.microsoft.com/fwlink/?linkid=2255127)
 * See the SKU deprecation [FAQs](#sku-deprecation-faqs)
 
-When the migration path becomes available, you can migrate your legacy SKUs to the following SKUs:
+When the migration path becomes available, the product team will automatically migrate your legacy SKUs to the following SKUs:
 
 * **Standard SKU:** -> **VpnGw1**
 * **High Performance SKU:** -> **VpnGw2**
@@ -96,15 +96,15 @@ There are no [price](https://azure.microsoft.com/pricing/details/vpn-gateway/) c
 * **Standard SKU:** 6.5x
 * **High Performance SKU:** 5x
 
-If you don't migrate your gateway SKUs by September 30, 2025, your gateway will be automatically migrated and upgraded to an AZ gateway SKU:
+As next steps, your gateway will be automatically migrated and upgraded to an AZ gateway SKU:
 
 * **Standard SKU:** -> **VpnGw1AZ**
 * **High Performance SKU:** -> **VpnGw2AZ**
 
 Important Dates:
 
 * **December 1, 2023**: No new gateway creations are possible using Standard or High Performance SKUs.
-* **November 30, 2024**: Begin migrating gateways to other SKUs.
+* **May 31, 2025**: Begin migrating gateways to other SKUs.
 * **September 30, 2025**: Standard/High Performance SKUs will be retired and remaining deprecated legacy gateways will be automatically migrated and upgraded to AZ SKUs.
 
 ## SKU deprecation FAQs