|
1 | 1 | --- |
2 | | -title: How to migrate a Basic SKU public IP address to a Standard SKU for VPN Gateway - Preview |
| 2 | +title: How to migrate a Basic SKU public IP address to a Standard SKU for VPN Gateway |
3 | 3 | titleSuffix: Azure VPN Gateway |
4 | 4 | description: Learn how to migrate from a Basic SKU public IP address to a Standard SKU public IP address for VPN Gateway deployment. |
5 | 5 | author: cherylmc |
6 | 6 | ms.service: azure-vpn-gateway |
7 | 7 | ms.topic: how-to |
8 | | -ms.date: 08/25/2025 |
| 8 | +ms.date: 01/30/2026 |
9 | 9 | ms.author: cherylmc |
10 | 10 | #customer intent: As a cloud network administrator, I want to migrate a Basic SKU public IP address to a Standard SKU for VPN Gateway, so that I can ensure optimal performance and compliance with service standards during our infrastructure upgrade. |
11 | 11 | --- |
12 | 12 |
|
13 | | -# How to migrate a Basic SKU public IP address to Standard SKU for VPN Gateway - Preview |
| 13 | +# How to migrate a Basic SKU public IP address to Standard SKU for VPN Gateway |
14 | 14 |
|
15 | 15 | This article helps you migrate a Basic SKU public IP address to a Standard SKU for VPN Gateway deployments that use gateway SKUs VpnGw 1-5 for active-passive gateways (not active-active). For more information about Basic SKU migration, see [About migrating a Basic SKU public IP address to Standard SKU for VPN Gateway](basic-public-ip-migrate-about.md). |
16 | 16 |
|
17 | 17 | > [!IMPORTANT] |
18 | | -> Basic SKU public IP address migration for VPN Gateway is currently in PREVIEW. |
19 | | -> See the [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/) for legal terms that apply to Azure features that are in beta, preview, or otherwise not yet released into general availability. |
| 18 | +> Basic SKU public IP address migration for VPN Gateway is currently Generally Available for Active-Passive with some limitations (see known issues). |
20 | 19 |
|
21 | 20 | During the public IP address SKU migration process, your Basic SKU public IP address resource is migrated to a Standard SKU public IP address resource. The IP address assigned to your gateway doesn't change. |
22 | 21 |
|
@@ -149,7 +148,7 @@ Point-to-Site VPN Gateways that were originally deployed using legacy cloudapp.N |
149 | 148 |
|
150 | 149 | VPN Gateways with legacy cloudapp.NET DNS configurations cannot be migrated using the current migration tools. These gateways require a specialized migration approach that is currently under development. |
151 | 150 |
|
152 | | -A guided migration experience for legacy DNS gateways is planned for release, with the timeline to be announced by the end of January 2026. Until this specialized migration becomes available, these gateways will continue to function normally but cannot be upgraded to Standard SKU public IP addresses. |
| 151 | +A guided migration experience for legacy DNS gateways is planned for release, with the timeline to be announced by the end of February 2026. Until this specialized migration becomes available, these gateways will continue to function normally but cannot be upgraded to Standard SKU public IP addresses. |
153 | 152 |
|
154 | 153 | ### Important considerations |
155 | 154 |
|
|
0 commit comments