Merge pull request #294863 from AbdullahBell/vpn-gateway-faq-change

VPN Gateway: Update: VPN Gateway FAQ, get started, and  vnet ip basic upgrade

Author: prmerger-automator[bot]

articles/virtual-network/ip-services/public-ip-basic-upgrade-guidance.md

@@ -40,7 +40,7 @@ We recommend the following approach to upgrade to Standard SKU public IP address
   | Virtual Machine | Use scripts or manually detach and upgrade public IPs. For standalone virtual machines, you can use the [upgrade script](public-ip-upgrade-vm.md) or for virtual machines in an availability set use [this script](public-ip-upgrade-availability-set.md). |
   | Virtual Machine Scale Sets | [Replace basic SKU instance public IP addresses](/azure/virtual-machine-scale-sets/virtual-machine-scale-sets-networking#public-ipv4-per-virtual-machine) with new standard SKU |
   | Load Balancer (Basic SKU) | New Load Balancer SKU required. Use the upgrade script [Upgrade Basic Load Balancer to Standard SKU](../../load-balancer/upgrade-basic-standard-with-powershell.md) to upgrade to Standard Load Balancer |
-  | VPN Gateway (using Basic IPs) | A migration path will be provided in the future. When this migration path is available, we'll update this decision path with migration information and send out a service health alert. |
+  | VPN Gateway (using Basic IPs) | A migration path will be provided in the future. When this migration path is available, we'll update this decision path with migration information and send out a service health alert. For more information, see [Migrating a basic SKU FAQ](../../vpn-gateway/vpn-gateway-vpn-faq.md/#migrating-a-basic-sku-public-ip-address-to-standard-sku |
   |  ExpressRoute Gateway (using Basic IPs) | New ExpressRoute Gateway is required. Follow the [ExpressRoute Gateway migration guidance](../../expressroute/gateway-migration.md) for upgrading from Basic to Standard SKU.  |
   | Application Gateway (v1 SKU) | New AppGW SKU required. Use this [migration script to migrate from v1 to v2](../../application-gateway/migrate-v1-v2.md).  |
 

articles/vpn-gateway/vpn-gateway-vpn-faq.md

@@ -4,7 +4,7 @@ description: Get answers to frequently asked questions about VPN Gateway connect
 author: cherylmc
 ms.service: azure-vpn-gateway
 ms.topic: concept-article
-ms.date: 07/10/2024
+ms.date: 02/18/2025
 ms.author: cherylmc
 ---
 
@@ -138,7 +138,7 @@ No.
 
 ### Can I get my VPN gateway IP address before I create it?
 
-Azure Standard SKU public IP resources must use a static allocation method. You'll have the public IP address for your VPN gateway as soon as you create the Standard SKU public IP resource that you intend to use for it.
+Azure Standard SKU public IP resources must use a static allocation method. You have the public IP address for your VPN gateway as soon as you create the Standard SKU public IP resource that you intend to use for it.
 
 ### Can I request a static public IP address for my VPN gateway?
 
@@ -148,7 +148,7 @@ For non-zone-redundant and non-zonal gateways that were previously created (gate
 
 ### How does the retirement of Basic SKU public IP addresses affect my VPN gateways?
 
-We're taking action to ensure the continued operation of deployed VPN gateways that use Basic SKU public IP addresses until the retirement of Basic IP in September 2025. Before this retirement, we will provide customers with a migration path from Basic to Standard IP. 
+We're taking action to ensure the continued operation of deployed VPN gateways that use Basic SKU public IP addresses until the retirement of Basic IP in September 2025. Before this retirement, we'll provide customers with a migration path from Basic to Standard IP. 
 
 However, Basic SKU public IP addresses are being phased out. Going forward, when you create a VPN gateway, you must use the Standard SKU public IP address. You can find details on the retirement of Basic SKU public IP addresses in the [Azure Updates announcement](https://azure.microsoft.com/updates/upgrade-to-standard-sku-public-ip-addresses-in-azure-by-30-september-2025-basic-sku-will-be-retired).
 
@@ -206,16 +206,43 @@ The Standard and High Performance SKUs will be deprecated on September 30, 2025.
 
 *At this time, there's no action that you need to take.*
 
+
 [!INCLUDE [legacy SKU deprecation](../../includes/vpn-gateway-deprecate-sku-faq.md)]
 
+## Migrating a Basic SKU public IP address to Standard SKU
+
+This section outlines important questions and considerations for migrating from a Basic SKU public IP address to a Standard SKU public IP address for VPN Gateway deployments currently using a Basic SKU public IP address. This does not pertain to deployments that are already using a Standard SKU public IP address. For more information, see [Basic SKU IP deprecation 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).
+ 
+### What is the expected customer impact?
+
+The expected customer impact includes new [pricing](https://azure.microsoft.com/pricing/details/ip-addresses/) changes and up to 10 minutes of downtime during customer-controlled migration. Customers will have three months to migrate after the release of the migration tool. To qualify for a successful migration, ensure you have the correct IP address space and subnet size.
+ 
+### What is the anticipated timeline for the migration?
+
+These timelines may be subject to change. Please revisit this for the most updated timeline. Here's the anticipated timeline for the migration tool availability.
+
+  | Date                | Event                                                      |
+  |---------------------|------------------------------------------------------------|
+  | Apr/May 2025        | Migration tooling availability for Active-Passive Gateways. |
+  | Jul/Aug 2025        | Migration tooling availability for Active-Active Gateways.  |
+  | May 2025 to Sep 2025| Customer-controlled migration can be initiated after tool availability. |
+  | Sep 2025            | Basic SKU IP addresses are deprecated.                     |
+
+
+### What are the required customer actions?
+
+Ensure you have the correct IP address space and subnet size to support the migration. If your gateway is using a Basic IP, you need to migrate it to a Standard IP to avoid service disruption. This migration is necessary because Basic IP addresses will be deprecated by September 2025. If your gateway is already using a Standard IP, no action is required.
+ 
 ## <a name="s2s"></a>Site-to-site connections and VPN devices
 
+
 ### What should I consider when selecting a VPN device?
 
 We've validated a set of standard site-to-site VPN devices in partnership with device vendors. You can find a list of known compatible VPN devices, their corresponding configuration instructions or samples, and device specifications in the [About VPN devices](vpn-gateway-about-vpn-devices.md) article.
 
 All devices in the device families listed as known compatible should work with virtual networks. To help configure your VPN device, refer to the device configuration sample or link that corresponds to the appropriate device family.
 
+
 ### Where can I find VPN device configuration settings?
 
 [!INCLUDE [vpn devices](../../includes/vpn-gateway-configure-vpn-device-rm-include.md)]

articles/vpn-gateway/whats-new.md

@@ -4,14 +4,15 @@ description: Learn what's new with Azure VPN Gateway such as the latest release
 author: cherylmc
 ms.service: azure-vpn-gateway
 ms.topic: concept-article
-ms.date: 08/16/2024
+ms.date: 02/18/2025
 ms.author: cherylmc
 ---
 
 # What's new in Azure VPN Gateway?
 
 Azure VPN Gateway is updated regularly. Stay up to date with the latest announcements. This article provides you with information about:
 
+* Projected changes
 * Recent releases
 * Previews underway with known limitations (if applicable)
 * Known issues
@@ -20,6 +21,19 @@ Azure VPN Gateway is updated regularly. Stay up to date with the latest announce
 
 You can also find the latest VPN Gateway updates and subscribe to the RSS feed [here](https://azure.microsoft.com/updates?filters=%5B%22VPN+Gateway%22%5D).
 
+## Upcoming projected changes
+
+> [!NOTE]
+> Timelines are subject to change.
+
+| Event | Customer impact| Anticipated timelines | Customer action/ prerequisites | Documentation | Annoucement Links |
+|---|---|---|---|---|---|
+|Basic SKU public IP address migration  |- New [pricing changes](https://azure.microsoft.com/pricing/details/ip-addresses/).<br>- To qualify for successful migration, ensure you have the right IP address space and subnet size.<br>- Up to 10 minutes of downtime is expected during customer-controlled migration.<br>- Customers will have 3 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 right IP address space and subnet size, check here.<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.|Available when the migration tool is released. |[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) |
+|Non-AZ gateway SKU retirement |- New pricing for AZ gateway SKUs applied since Jan 2025.<br>- Non-AZ gateway SKUs will be migrated to AZ gateway SKUs with no downtime expected.<br>- Non-AZ gateway SKU creates to be blocked by May 2025. |- **Jan 2025**: New pricing for AZ gatway SKUs activated.<br> - **May 2025 to Sep 2026**: Non-AZ gateway SKU-to-AZ gateway SKU migration available.<br> - **Sep 2026**: Non-AZ gateway SKU retirement.|- If the VPN gateway is using a Basic public IP address SKU, migrate it to a Standard public IP address SKU.|[VPN Gateway SKU consolidation and migration](gateway-sku-consolidation.md)| [Non-AZ gateway SKU retirement](https://azure.microsoft.com/updates?id=vpngw1-5-non-az-skus-will-be-retired-on-30-september-2026)|
+|Gateway SKU retirement: Standard and High Performance SKUs.|- New Standard/High Perf SKU gateway creations blocked Nov 2023.<br> - Standard/High Perf SKU gateways will be migrated to VpnGw1/VpnGw2.<br> - No downtime is expected for migration.|- **May 2025 to Sep 2025**: Standard/HighPerf SKU migration.<br>- **Sep 2025**: Standard/HighPerf SKU retirement.| - No action required|[Working with VPN Gateway legacy SKUs](vpn-gateway-about-skus-legacy.md)|[Standard and HighPerf gateway SKU retirement](https://azure.microsoft.com/updates?id=standard-and-highperformance-vpn-gateway-skus-will-be-retired-on-30-september-2025)|
+|Classic VPN gateways retired|- Classic VPN gateways will be decommissioned.|- **Aug 2024**: Retirement<br>- **By Aug 2025**: Decommission|- Migrate your classic VPN gateway to an Azure Resource Manager gateway|[VPN Gateway classic to Resource Manager migration](vpn-gateway-classic-resource-manager-migration.md)|[Classic resource retirement](https://azure.microsoft.com/updates?id=cloud-services-retirement-announcement)|
+
+
 ## Recent releases and announcements
 
 | Type | Area | Name | Description | Date added | Limitations |