Add link to What's new article.

Author: cherylmc

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

@@ -6,41 +6,13 @@ author: raboilla
 ms.service: azure-vpn-gateway
 ms.topic: concept-article
 ms.custom: references_regions
-ms.date: 04/09/2025
+ms.date: 06/10/2025
 ms.author: cherylmc
 ---
 
 # About migrating a Basic SKU public IP address to Standard SKU
 
-This article explains the migration process from a Basic SKU public IP address to a Standard SKU public IP address for VPN Gateway deployments. For more information, see the [announcement](https://azure.microsoft.com/updates?id=upgrade-to-standard-sku-public-ip-addresses-in-azure-by-30-september-2025-basic-sku-will-be-retired).
-
-## <a name="scenarios"></a>Supported migration scenarios
-
-There are separate migration timelines, depending on the VPN Gateway SKU that your gateway is currently configured to use.
-
-* For the VPN Gateway Basic SKU, see the [VPN Gateway Basic SKU](#basicsku-timeline) section.
-* For other supported VPN Gateway SKUs, see the [Gateway SKUs VpnGw1-5](#skus-timeline) section.
-
-> [!NOTE]
-> Timelines are subject to change.
-
-### <a name="skus-timeline"></a>Gateway SKUs VpnGw1-5
-
-This section applies to the following VPN Gateway SKUs that are supported for migration from a Basic SKU public IP address to a Standard SKU public IP address:
-
-* VpnGw1
-* VpnGw2
-* VpnGw3
-* VpnGw4
-* VpnGw5
-
-|Considerations | Anticipated timelines | Customer action/ prerequisites | Documentation | Announcement links |
-|---|---|---|---|---|
-|- New [pricing changes](https://azure.microsoft.com/pricing/details/ip-addresses/).<br>- Customers will have three months to migrate after the release of the migration tool.|- **Apr/May 2025**: Basic SKU public IP address-to-Standard SKU public IP address migration tool is available for for active-passive gateways.<br>- **Jul/Aug 2025**: Basic SKU public IP address-to-Standard SKU public IP address migration tool is available for for active-active gateways.<br>- **May 2025 to Sep 2025**: Customer-controlled migration can be initiated after tool availability.<br>- **Sep 2025**: Basic SKU public IP addresses are deprecated. |- Ensure you have the correct gateway IP address space and subnet size.<br>- If your VPN gateway is using a Basic SKU public IP address, migrate it to a Standard SKU public IP address.<br> - If your VPN gateway is already using a Standard SKU public IP address, no action is required.|[Migration steps](basic-public-ip-migrate-howto.md) |[Basic SKU public IP address retirement](https://azure.microsoft.com/updates?id=upgrade-to-standard-sku-public-ip-addresses-in-azure-by-30-september-2025-basic-sku-will-be-retired) |
-
-### <a name="basicsku-timeline"></a>Basic gateway SKU
-
-Migration plans for VPN gateways that use a Basic gateway SKU with a Basic SKU public IP address will be announced by **June 15, 2025**.
+This article explains the migration process from a Basic SKU public IP address to a Standard SKU public IP address for VPN Gateway deployments. There are separate migration timelines, depending on the VPN Gateway SKU that your gateway is currently configured to use. For anticipated migration timelines, see the [VPN Gateway - What's new](whats-new.md) article.
 
 ## <a name="considerations"></a>Migration considerations
 
@@ -87,7 +59,7 @@ Yes, you can. If you choose to do this manually, you'll need to delete the old g
 
 ### If I delete and re-create my gateway, will my IP address change?
 
-Yes, the IP address will change with this approach. This means that you'll have to ensure the new IP address is updated in all of your internal tooling as needed.
+Yes, the IP address changes with this approach. This means that you'll have to ensure the new IP address is updated in all of your internal tooling as needed.
 
 ## Next steps