Skip to content

Commit 68795ec

Browse files
cherylmccherylmc
committed
new article
1 parent 8ef0f4b commit 68795ec

File tree

2 files changed

+98
-0
lines changed

2 files changed

+98
-0
lines changed

‎articles/vpn-gateway/TOC.yml

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -58,6 +58,10 @@
5858
items:
5959
- name: About SKU consolidation & migration
6060
href: gateway-sku-consolidation.md
61+
- name: Basic SKU public IP address migration
62+
items:
63+
- name: About Basic SKU public IP address migration
64+
href: basic-public-ip-migrate-about.md
6165
- name: Resize a gateway SKU
6266
href: gateway-sku-resize.md
6367
- name: Change a gateway SKU

‎articles/vpn-gateway/basic-public-ip-migrate-about.md

Lines changed: 94 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,94 @@
1+
---
2+
title: About migrating a Basic SKU public IP address to Standard SKU
3+
titleSuffix: Azure VPN Gateway
4+
description: This article explains the migration process from a Basic SKU public IP address to a Standard SKU public IP address for VPN Gateway deployments that are currently using a Basic SKU public IP address. This doesn't pertain to deployments that are already using a Standard SKU public IP address.
5+
author: raboilla
6+
ms.service: azure-vpn-gateway
7+
ms.topic: concept-article
8+
ms.custom: references_regions
9+
ms.date: 04/03/2025
10+
ms.author: cherylmc
11+
---
12+
13+
# About migrating a Basic SKU public IP address to Standard SKU for VPN Gateway
14+
15+
This article explains the migration process from a Basic SKU public IP address to a Standard SKU public IP address for VPN Gateway deployments. For more information, see the [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).
16+
17+
## Supported migration scenarios
18+
19+
There are separate migration timelines, depending on the VPN Gateway SKU that your gateway is currently configured to use.
20+
21+
* For the VPN Gateway Basic SKU, see the [VPN Gateway Basic SKU](#basicsku-timeline) section.
22+
* For other supported VPN Gateway SKUs, see the [Gateway SKUs VpnGw1-5](#skus-timeline) section.
23+
24+
> [!NOTE]
25+
> Timelines are subject to change.
26+
27+
### <a name="skus-timeline"></a>Gateway SKUs VpnGw1-5
28+
29+
This section applies to the following VPN Gateway SKUs that are supported for migration from a Basic SKU public IP address to a Standard SKU public IP address:
30+
31+
* VpnGw1
32+
* VpnGw2
33+
* VpnGw3
34+
* VpnGw4
35+
* VpnGw5
36+
37+
|Considerations | Anticipated timelines | Customer action/ prerequisites | Documentation | Announcement links |
38+
|---|---|---|---|---|
39+
|- New [pricing changes](https://azure.microsoft.com/pricing/details/ip-addresses/).<br>- Customers will have three 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 correct gateway IP address space and subnet size.<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) |
40+
41+
### <a name="basicsku-timeline"></a>Basic gateway SKU
42+
43+
Migration plans for VPN gateways that use a Basic gateway SKU with a Basic SKU public IP address will be announced by **April 30, 2025**.
44+
45+
## Migration considerations
46+
47+
To migrate your gateway, you first need to validate whether your resource is capable of migration. Here are some common situations to be aware of:
48+
49+
* If your current gateway subnet is /28 or smaller, the migration tool will error out. You need to [resize the gateway subnet](../virtual-network/virtual-network-manage-subnet.md#change-subnet-settings) to /27 or larger before you can proceed with migration.
50+
51+
* Before your initiate migration for your VPN gateway, verify that your gateway subnet has at least *three* available IP addresses in your current prefix.
52+
53+
## FAQ
54+
55+
### How will my gateway SKU be impacted after the Basic SKU public IP address migration?
56+
57+
After you upgrade from a Basic SKU public IP address to a Standard SKU public IP address, your VPN gateway SKU VPNGW1-5 will be migrated to VPNGW1AZ-5. As a result, you might see the SKU changed from a Non-AZ to an AZ-SKU. For more information about SKU impact, see the [Gateway SKU migration](gateway-sku-consolidation.md) article.
58+
59+
### Will my VPN gateway IP address change after my public IP address is migrated?
60+
61+
* If you use the Microsoft-provided migration experience, your gateway IP address won't change.
62+
* If you manually delete your current VPN gateway that has a Basic SKU public IP address and create a new VPN gateway using a Standard SKU public IP address, your gateway IP address changes.
63+
64+
### Will there be any downtime?
65+
66+
Up to 10 minutes of downtime is expected during the Microsoft-provided migration experience.
67+
68+
### Do I need to take any actions to migrate?
69+
70+
The Microsoft-provided migration experience is a customer-initiated migration. You'll need to initiate the migration process. The migration process is expected to take up to 10 minutes.
71+
72+
### Are there any migration prerequisites?
73+
74+
Ensure that your gateway subnet has right IP address space and subnet size. You'll need at least three available IP addresses in your current prefix before you perform the migration.
75+
76+
### Can I create a Basic SKU VPN gateway with a Basic SKU public IP address after March 31, 2025?
77+
78+
Yes, you can create a VPN gateway using the gateway Basic SKU and a Basic SKU public IP address until June 2025.
79+
80+
### When will I be able to create a Basic SKU VPN gateway with a Standard SKU public IP address?
81+
82+
The Standard SKU public IP address parameter for the VPN Gateway Basic SKU is currently being rolled out and will be completed in April 2025. After this date, you'll be able to create a Basic SKU VPN gateway with a Standard SKU public IP address.
83+
84+
### Can I change to a Standard SKU public IP address manually?
85+
86+
Yes, you can. If you choose to do this manually, you'll need to delete the old gateway and then create a new gateway in your virtual network. When you create a new gateway, your gateway will automatically use a Standard SKU public IP address. However, if you choose to use this process, you'll incur downtime while the old gateway is deleted and the new gateway is created. For more information, see [Change a gateway SKU](gateway-sku-change.md).
87+
88+
### If I delete and re-create my gateway, will my IP address change?
89+
90+
Yes, the IP address will change with this approach. This means that you'll have to ensure the new IP address is updated in all of your internal tooling as needed.
91+
92+
## Next steps
93+
94+
For more information, see the [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).

0 commit comments

Comments
 (0)