Skip to content

Update whats-new.md #127350

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion articles/vpn-gateway/whats-new.md
Original file line number Diff line number Diff line change
Expand Up @@ -31,7 +31,7 @@ You can also find the latest VPN Gateway updates and subscribe to the RSS feed [

| Event | Customer impact| Anticipated timelines | Customer action/ prerequisites | Documentation | Announcement Links |
|---|---|---|---|---|---|
|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.|- **By end of Jul 2025**: Basic SKU public IP address-to-Standard SKU public IP address migration tool is available for for active-passive gateways.<br>- **Aug 2025**: Basic SKU public IP address-to-Standard SKU public IP address migration tool is available for for active-active gateways.<br>- **By end of Jul 2025 to end Jan 2026**: Customer-controlled migration can be initiated after tool availability.<br>- **Feb 2026**: Basic SKU public IP addresses are deprecated. <br> **Deprecation timeline of Basic IP for VPN Gateways only is moved from Sep 2025 to end of Jan 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.|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) |
|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.|- **By end of Jul 2025**: Basic SKU public IP address-to-Standard SKU public IP address migration tool is available for active-passive gateways.<br>- **Aug 2025**: Basic SKU public IP address-to-Standard SKU public IP address migration tool is available for active-active gateways.<br>- **By end of Jul 2025 to end Jan 2026**: Customer-controlled migration can be initiated after tool availability.<br>- **Feb 2026**: Basic SKU public IP addresses are deprecated. <br> **Deprecation timeline of Basic IP for VPN Gateways only is moved from Sep 2025 to end of Jan 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.|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) |
|Basic SKU public IP address migration - For Basic SKU Gateway | Impact details to be updated by **end of Jul 30, 2025** | Migration approach for Basic IP address for Basic Gateway SKU’s will be published by **end of Jul 30, 2025** | Customer action to be updated by **end of Jul 30, 2025** | 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) |
|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)|
|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)|
Expand Down