Skip to content

Commit 5c0b175

Browse files
prmerger-automator[bot]prmerger-automator[bot]
authored
Merge pull request #307294 from raboilla/patch-35
Added note and Revise VPN Gateway migration timelines and details
2 parents 60623ae + a0b3179 commit 5c0b175

1 file changed

Lines changed: 3 additions & 2 deletions

File tree

‎articles/vpn-gateway/whats-new.md‎

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -27,12 +27,13 @@ You can also find the latest VPN Gateway updates and subscribe to the RSS feed [
2727
## Upcoming projected changes
2828

2929
> [!NOTE]
30-
> Timelines are subject to change.
30+
> Timelines are subject to change.<br>
31+
> Basic IP deprecation timeline for all **VPN Gateways** is moved to **End of Mar 2026**
3132
3233
| Event | Customer impact| Anticipated timelines | Customer action/ prerequisites | Documentation | Announcement Links |
3334
|---|---|---|---|---|---|
3435
|Basic SKU public IP address migration - For all VPN SKU's except Basic SKU Gateway |- 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 atleast ~3 months to migrate after the release of the migration tool.|- **Starting Aug 4, 2025**: Basic SKU public IP address-to-Standard SKU public IP address migration tool is in **public preview** for **active-passive** gateways in Public cloud. <br> - Tentative **GA** timeline for Public and National cloud support **Mid-Nov 2025** <br>- **Mid-Nov 2025**: Basic SKU public IP address-to-Standard SKU public IP address migration tool tentative **GA** timeline for **active-active** gateways.<br>- **From Aug 4, 2025 to End of Mar 2026**: Customer-controlled migration can be initiated after tool availability.<br>- **April 2026**: Basic SKU public IP addresses are deprecated. <br> - **Deprecation timeline of Basic IP for all VPN Gateways is moved to End of Mar 2026**|- 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.|- [About Basic SKU Public IP address migration](basic-public-ip-migrate-about.md) <br> - [How to migrate Basic SKU public IP address to Standard](basic-public-ip-migrate-howto.md?tabs=portal)|[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) |
35-
|Basic SKU public IP address migration - For Basic SKU Gateway | - Your actual IP address will not change, and connectivity will not be interrupted. | An automated capability to remove the Basic public IP from your gateway will be available **End of Oct 2025** <br> - **Deprecation timeline of Basic IP for all VPN Gateways is moved to end of Mar 2026** | - Because Microsoft is retiring Basic public IP resources, we’re updating the Basic VPN Gateway construct. You’ll see the Basic public IP reference as an attribute on your virtual network gateway. <br> - Your actual IP address will not change, and connectivity will not be interrupted. <br> - If you have scripts, ARM templates, or monitoring solutions that reference the Basic public IP resource, update them to use the IP address property of the virtual network gateway instead. | Available when the migration details are 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) |
36+
|Basic SKU public IP address migration - For Basic SKU Gateway | - Your actual IP address will not change, and connectivity will not be interrupted. | An automated capability to remove the Basic public IP from your gateway will be available **Mid-February'2026** <br> - **Deprecation timeline of Basic IP for all VPN Gateways is moved to end of Mar 2026** | - Because Microsoft is retiring Basic public IP resources, we’re updating the Basic VPN Gateway construct. You’ll see the Basic public IP reference as an attribute on your virtual network gateway. <br> - Your actual IP address will not change, and connectivity will not be interrupted. <br> - If you have scripts, ARM templates, or monitoring solutions that reference the Basic public IP resource, update them to use the IP address property of the virtual network gateway instead. | Available when the migration details are 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) |
3637
|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 gateway 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)|
3738
|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 on non-AZ regions and to VpnGw1AZ/VpnAz2 on AZ regions.<br> - No downtime is expected for migration.|- **May 2025 to Mar 2026**: Standard/HighPerf SKU migration.<br>- **Mar 2026**: Standard/HighPerf SKU retirement (extended from Sep 2025).| - 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)|
3839
|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)|

0 commit comments

Comments
 (0)