format

Author: cherylmc

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

@@ -4,7 +4,7 @@ description: Learn about VPN Gateway SKUs.
 author: cherylmc
 ms.service: azure-vpn-gateway
 ms.topic: concept-article
-ms.date: 03/31/2025
+ms.date: 06/23/2025
 ms.author: cherylmc 
 
 ---

articles/vpn-gateway/basic-public-ip-migrate-about.md

@@ -6,7 +6,7 @@ author: raboilla
 ms.service: azure-vpn-gateway
 ms.topic: concept-article
 ms.custom: references_regions
-ms.date: 06/10/2025
+ms.date: 06/23/2025
 ms.author: cherylmc
 ---
 
@@ -18,7 +18,7 @@ This article explains the migration process from a Basic SKU public IP address t
 
 To migrate your gateway, you first need to validate whether your resource is capable of migration. Here are some common situations to be aware of:
 
-* If your current gateway subnet is /28 or smaller, the migration tool may error out. You can use this to [add multiple prefixes for subnet](https://learn.microsoft.com/azure/virtual-network/how-to-multiple-prefixes-subnet?tabs=powershell) to /27 or larger before you can proceed with migration.
+* If your current gateway subnet is /28 or smaller, the migration tool may error out. You can use this to [add multiple prefixes for subnet](../virtual-network/how-to-multiple-prefixes-subnet.md) to /27 or larger before you can proceed with migration.
 
 * Before your initiate migration for your VPN gateway, verify that your gateway subnet has at least *three* available IP addresses in your current prefix.
 

articles/vpn-gateway/gateway-sku-upgrade.md

@@ -1,13 +1,15 @@
 ---
-title: 'Upgrade a VPN Gateway SKU'
+title: Upgrade a VPN Gateway SKU
 titleSuffix: Azure VPN Gateway
 description: Learn how to upgrade a VPN Gateway SKU in Azure.
 author: cherylmc
 ms.service: azure-vpn-gateway
 ms.topic: how-to
-ms.date: 06/10/2025
+ms.date: 06/23/2025
 ms.author: cherylmc
 
+#customer intent: As an Azure network engineer, I want to understand the workflow for upgrading a VPN Gateway SKU so that I can plan properly and minimize downtime.
+
 ---
 # Upgrade a gateway SKU
 

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

@@ -4,12 +4,15 @@ description: How to work with the old virtual network gateway SKUs; Standard, an
 author: cherylmc
 ms.service: azure-vpn-gateway
 ms.topic: how-to
-ms.date: 05/08/2025
-ms.author: cherylmc 
+ms.date: 06/23/2025
+ms.author: cherylmc
+
+#customer intent: As an Azure administrator, I want to understand the legacy SKU deprecation timeline so that I can plan for the automatic migration.
+
 ---
 # 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 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).
+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). For the projected gateway SKU deprecation/migration timeline, see the [What's new?](whats-new.md) article.
 
 ## <a name="gwsku"></a>Legacy gateway SKUs
 
@@ -34,7 +37,7 @@ The UltraPerformance gateway SKU isn't represented in this table. For informatio
 
 (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.
 
-(2) The number of tunnels refer to RouteBased VPNs. A PolicyBased VPN can only support one Site-to-Site VPN tunnel.
+(2) The number of tunnels refers to RouteBased VPNs. A PolicyBased VPN can only support one Site-to-Site VPN tunnel.
 
 (3) PolicyBased VPNs aren't supported for this SKU. They're supported for the Basic SKU.
 

includes/vpn-gateway-deprecate-sku-faq.md

@@ -1,7 +1,7 @@
 ---
 ms.author: cherylmc
 author: cherylmc
-ms.date: 03/06/2024
+ms.date: 06/23/2025
 ms.service: azure-vpn-gateway
 ms.topic: include
 ---