Skip to content

Commit 1efd598

Browse files
aybatraaybatra
authored
Revise Basic SKU public IP migration details
Updated the deprecation timeline for Basic SKU public IP addresses and clarified migration details for Basic SKU Gateway.
1 parent b2591a0 commit 1efd598

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -33,7 +33,7 @@ You can also find the latest VPN Gateway updates and subscribe to the RSS feed [
3333
| Event | Customer impact| Anticipated timelines | Customer action/ prerequisites | Documentation | Announcement Links |
3434
|---|---|---|---|---|---|
3535
|Basic SKU public IP address migration - For all VPN SKUs 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 at least ~3 months to migrate after the release of the migration tool.|- **Starting January 30th, 2026**: Basic SKU public IP address-to-Standard SKU public IP address migration tool is in **Generally Available** for **active-passive** gateways in Public cloud and National Clouds with some limitations, see [known Issues](basic-public-ip-migrate-howto.md#known-issues) . <br> - **Active-Active** Public Preview in Mar'26 with plan to announce GA in Apr’26 <br>- **July 2026**: Basic SKU public IP addresses are deprecated. <br> - **Deprecation timeline of Basic IP for all VPN Gateways is moved to End of June 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) |
36-
|Basic SKU public IP address migration - For Basic SKU Gateway | - Your actual IP address won't change, and connectivity won't be interrupted. | An automated capability to remove the Basic public IP from your gateway will be available **March'2026** <br> - **Deprecation timeline of Basic IP for all VPN Gateways is moved to end of June 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 won't change, and connectivity won't 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 won't change, and connectivity won't be interrupted. | An automated capability to remove the Basic public IP from your gateway will be available **March'2026** <br> - Jun 2026: **New Deprecation timeline** | - 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 won't change, and connectivity won't 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) |
3737
|Non-AZ gateway SKU retirement |- New AZ SKUs pricing applied since Jan 2025.<br>- No downtime expected.<br>- New Non-AZ SKU creates blocked in 2025. |- **Jan 2025**: New pricing activated.<br> - **May 2025 - Sep 2026**: Non-AZ SKU migration.<br> - **Sep 2026**: Non-AZ SKU retirement.|- Migrate Basic IP address to Standard IP if applicable. <br> - Upgrade the gateway SKU from portal |[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)|
3838
|Legacy SKU retirement: Standard and High Performance SKUs.|- New creations blocked in 2024.<br> - Up to 10 minutes of downtime.|- **May 2025 - Jun 2026**: Migration.<br>- **Jun 2026**: Legacy SKU retirement.| - **Nov 2025** Migrate Basic IP address (Active-Passive gateway) <br>- **Jan 2026** Migrate Basic IP address (Active-Active gateway) |[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)|
3939
|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)