Revise deprecation dates and migration guidance

Updated migration timeline and recommendations for VPN Gateway SKUs.

Author: aybatra

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

@@ -1,7 +1,7 @@
 ---
 ms.author: cherylmc
 author: cherylmc
-ms.date: 01/12/2025
+ms.date: 03/16/2025
 ms.service: azure-vpn-gateway
 ms.topic: include
 ---
@@ -32,12 +32,12 @@ Yes. You get better performance with the VpnGw1AZ and VpnGw2AZ SKUs. For more in
 
 ### What happens if I don't migrate by February 28, 2026?
 
-To ensure a smooth transition, we strongly recommend that customers use the Basic IP migration tool to migrate their Basic IPs and associated gateways. After March 2026, we'll attempt to migrate automatically all gateways that still use the Standard or High Performance SKU:
+To ensure a smooth transition, we strongly recommend that customers use the Basic IP migration tool to migrate their Basic IPs and associated gateways. After Jun 2026, we'll attempt to automatically migrate all gateways that still use the Standard or High Performance SKU:
 
 * Gateways on the Standard SKU will be automatically upgraded to VpnGw1AZ.
 * Gateways on the High Performance SKU will be automatically upgraded to VpnGw2AZ.
 
-If we encounter limitations such as insufficient subnet size, we won't be able to complete the gateway migration automatically. In this case, you'll need to take appropriate steps to resolve.
+If we encounter constraints such as an insufficient subnet size, the automatic gateway migration cannot be completed. In this case, you’ll need to take the required steps to resolve the issue. You can continue migrating your gateway using the Azure portal until backend migration support is available.
 
 ### Is the VPN Gateway Basic SKU also retiring?