|
| 1 | +--- |
| 2 | +title: How to migrate a Basic SKU public IP address to a Standard SKU |
| 3 | +titleSuffix: Azure VPN Gateway |
| 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 | +author: cherylmc |
| 6 | +ms.service: azure-vpn-gateway |
| 7 | +ms.topic: how-to |
| 8 | +ms.date: 04/28/2025 |
| 9 | +ms.author: cherylmc |
| 10 | +--- |
| 11 | + |
| 12 | +# How to migrate a Basic SKU public IP address to Standard SKU - Preview |
| 13 | + |
| 14 | +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). |
| 15 | + |
| 16 | +> [!IMPORTANT] |
| 17 | +> Basic SKU public IP address migration for VPN Gateway is currently in PREVIEW. |
| 18 | +> 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. |
| 19 | +
|
| 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. |
| 21 | + |
| 22 | +Additionally, if your VPN Gateway gateway SKU is VpnGw 1-5, your gateway SKU is migrated to a VPN Gateway AZ SKU (VpnGw 1-5 AZ). For more information, see [About VPN Gateway SKU consolidation and migration](gateway-sku-consolidation.md). |
| 23 | + |
| 24 | +> [!NOTE] |
| 25 | +> Migration functionality is rolling out to regions. If you don't see the **Migrate** tab in the Azure portal, it means that the migration process isn't available yet in your region. |
| 26 | +
|
| 27 | +## Workflow |
| 28 | + |
| 29 | +In the Azure portal, there are three sections for the migration process: |
| 30 | + |
| 31 | +* The first section is used to prepare for the migration. |
| 32 | +* The second section is used for two actions: |
| 33 | + * Migrate the public IP address from the Basic SKU public IP address resource to a Standard SKU public IP address resource. The IP address assigned to your gateway doesn't change. |
| 34 | + * Migrate the VPN Gateway gateway SKU from a non-AZ SKU to an AZ SKU. For example, VpnGw2 becomes VpnGw2AZ. |
| 35 | +* The third section validates the migration and deletes the old Basic SKU public IP address resource. |
| 36 | + |
| 37 | +## <a name="migrate"></a>Migrate to a Standard SKU public IP address |
| 38 | + |
| 39 | +Use the steps in the Azure portal to migrate your Basic SKU public IP address resource to a Standard SKU public IP address resource. |
| 40 | + |
| 41 | +> [!NOTE] |
| 42 | +> When you migrate your public IP address Basic SKU to the Standard SKU, your VPN Gateway SKU is also migrated. Non-AZ SKUs become AZ SKUs. |
| 43 | +
|
| 44 | +### Prepare for migration |
| 45 | + |
| 46 | +1. In the [Azure portal](https://portal.azure.com/), go to your virtual network gateway resource. In the left pane, under **Settings**, click **Configuration**. |
| 47 | +1. On the **Configuration** page, there are two options; Configure, and Migrate. Select **Migrate**. |
| 48 | + |
| 49 | + :::image type="content" source="./media/basic-public-ip-address-migrate-howto/migrate-prepare.png" alt-text="Screenshot of the migrate tab for migrating a virtual network gateway."lightbox="./media/basic-public-ip-address-migrate-howto/migrate-prepare.png"::: |
| 50 | + |
| 51 | +1. The **Migrate** tab lets you prepare for migration, and then migrate. If the environment requires manual preparation steps, you'll see a list of prerequisites that must be met before migration can begin. If these prerequisites aren't met, validation fails and you can't proceed with the migration. You must fix any issues identified in this section before you can proceed with the migration. |
| 52 | + |
| 53 | + For example, if your gateway subnet doesn't have enough available IP addresses, you'll see a message indicating that the gateway subnet size must be increased. To fix this issue, go to your virtual network and [change](../virtual-network/virtual-network-manage-subnet.md#change-subnet-settings) the GatewaySubnet size to /27 or larger. |
| 54 | + |
| 55 | +1. When all the prerequisites are met, you see the **Prepare** button. Click the **Prepare** button to prepare the new Standard SKU public IP address resources. |
| 56 | + |
| 57 | + :::image type="content" source="./media/basic-public-ip-address-migrate-howto/prepare.png" alt-text="Screenshot of the prepare step for migrating a virtual network gateway." lightbox="./media/basic-public-ip-address-migrate-howto/prepare.png"::: |
| 58 | + |
| 59 | +1. After you click Prepare, you'll see a status indicating that the migration preparation is in progress. When the preparation process is complete, you see a message indicating that the migration is ready to proceed. |
| 60 | + |
| 61 | +### Migrate |
| 62 | + |
| 63 | +1. After the Prepare step completes, the option to **Migrate** your resources is available. |
| 64 | + |
| 65 | + :::image type="content" source="./media/basic-public-ip-address-migrate-howto/migrate.png" alt-text="Screenshot of the migrate step for migrating a virtual network gateway."lightbox="./media/basic-public-ip-address-migrate-howto/migrate.png"::: |
| 66 | + |
| 67 | +1. Click the **Migrate** button to migrate your public IP address SKU and your gateway SKU. You'll have 5 minutes of downtime and can't make any changes to your VPN gateway during this time. |
| 68 | + |
| 69 | +### Validate migration |
| 70 | + |
| 71 | +If your VPN Gateway gateway SKU was VpnGw 1-5, your gateway SKU automatically migrated to an AZ SKU (VpnGw 1-5 AZ) as part of the migration process. In this section, you validate that the migration was successful and that traffic is flowing as expected. If you find that your gateway isn't working as expected, you have the opportunity to abort the migration to roll back any migration changes. |
| 72 | + |
| 73 | +> [!IMPORTANT] |
| 74 | +> It's important to validate the migration was successful before you commit the changes in this section. If migration wasn't successful, you have the option to abort and roll back your changes if you haven't committed them in this section. |
| 75 | +
|
| 76 | +1. Click the **Gateway Validation** link to go to the VPN gateway resource **Overview** page. |
| 77 | +1. Verify that your gateway is receiving and transmitting traffic. An easy way to validate traffic is to check the tunnel ingress and egress graphs on the gateway **Overview** page. |
| 78 | +1. If traffic isn't flowing properly or if you need to roll back changes, click **Abort**. This does the following: |
| 79 | + * The Standard SKU public IP address resource is rolled back to the Basic public IP address SKU. The IP address remains the same. |
| 80 | + * The VPN gateway SKU rolls back to a non-AZ SKU. For example, VpnGw2AZ reverts back to VpnGw2. If you accidentally click **Commit**, click **Cancel**, then **Abort** to roll back the changes. |
| 81 | +1. If validation is successful and traffic is flowing as expected, then click **Commit** and **Commit changes** to finalize the migration. If you don't commit the changes in this step, your Basic SKU public IP address resource remains in a pending state and won't be deleted. |
| 82 | + |
| 83 | + :::image type="content" source="./media/basic-public-ip-address-migrate-howto/commit-changes.png" alt-text="Screenshot of the commit changes step for migrating a virtual network gateway."lightbox="./media/basic-public-ip-address-migrate-howto/commit-changes.png"::: |
| 84 | + |
| 85 | +### View resources after migration |
| 86 | + |
| 87 | +When the public IP address migration is complete, you can view your resources on the page for your VPN gateway resource: |
| 88 | + |
| 89 | +* To view the gateway SKU, go to the **Overview** page for your VPN gateway. |
| 90 | + |
| 91 | +* To view the public IP address SKU, go to the **Properties** page for your VPN gateway. Click the IP address value to open the Public IP address resource and view the resource SKU. |
| 92 | + |
| 93 | +## Next steps |
| 94 | + |
| 95 | +* To see the announcement for this migration, see [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). |
| 96 | + |
| 97 | +* To learn more about the Basic SKU public IP address migration, see [About migrating a Basic SKU public IP address to Standard SKU for VPN Gateway](basic-public-ip-migrate-about.md). |
| 98 | + |
| 99 | +* To learn more about Gateway SKU consolidation and migration, see [About VPN Gateway SKU consolidation and migration](gateway-sku-consolidation.md). |
0 commit comments