New article- Remove Basic SKU public IP- Basic VPN Gateway

Author: cherylmc

articles/vpn-gateway/TOC.yml

@@ -64,8 +64,10 @@
       items:
         - name: About Basic SKU public IP address migration
           href: basic-public-ip-migrate-about.md
-        - name: How to migrate a Basic SKU public IP address to Standard
+        - name: Migrate a Basic SKU public IP address to Standard
           href: basic-public-ip-migrate-howto.md
+        - name: Remove the Basic SKU public IP reference - Basic SKU VPN gateways
+          href: basic-sku-public-ip-remove.md
     - name: About active-active mode gateways
       href: about-active-active-gateways.md
     - name: VPN Gateway configuration settings

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

@@ -6,14 +6,14 @@ author: raboilla
 ms.service: azure-vpn-gateway
 ms.topic: concept-article
 ms.custom: references_regions
-ms.date: 01/21/2026
+ms.date: 03/06/2026
 ms.author: cherylmc
 # Customer intent: As a network administrator, I want to migrate my VPN Gateway from a Basic SKU public IP address to a Standard SKU, so that I can ensure continued service and optimize performance as Basic SKU is phased out.
 ---
 
 # About migrating a Basic SKU public IP address to Standard SKU
 
-This article explains the migration process from a Basic SKU public IP address to a Standard SKU public IP address for VPN Gateway deployments. There are separate migration timelines, depending on the VPN Gateway SKU that your gateway is currently configured to use. 
+This article explains the migration process from a Basic SKU public IP address to a Standard SKU public IP address for VPN Gateway deployments. There are separate migration timelines, depending on the VPN Gateway SKU that your gateway is currently configured to use.
 
 > [!IMPORTANT]
 > For anticipated migration timelines, see the [VPN Gateway - What's new](whats-new.md) article.
@@ -22,65 +22,80 @@ This article explains the migration process from a Basic SKU public IP address t
 
 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:
 
-* Before your initiate migration for your VPN gateway, verify that your gateway subnet has at least **three** available IP addresses in your current prefix.
-  
-* If your current gateway subnet is /28 or smaller, the migration tool may error out. You can use this to [add multiple prefixes for subnet](../virtual-network/how-to-multiple-prefixes-subnet.md) to /27 or larger before you can proceed with migration.
+* For VPN Gateway Basic gateway SKU:
+
+  * If your Basic SKU VPN gateway has a Basic SKU public IP reference, you don't use the migration process. You only need to remove the Basic SKU public IP reference from your gateway.
+  * For steps to remove the Basic SKU public IP reference, see [Remove the Basic SKU public IP reference from a Basic SKU VPN gateway](basic-sku-public-ip-remove.md).
 
-* If you have ExpressRoute and VPN coexisting. We'd like to recommend customers to consider migrating the Basic IP resources to Standard IP on **VPN** first. 
+* For VPN Gateway SKUs VpnGw1-5:
 
+  * Before your initiate migration for your VPN gateway, verify that your gateway subnet has at least **three** available IP addresses in your current prefix.
+  
+  * If your current gateway subnet is /28 or smaller, the migration tool may error out. You can use this to [add multiple prefixes for subnet](../virtual-network/how-to-multiple-prefixes-subnet.md) to /27 or larger before you can proceed with migration.
 
+  * If you have ExpressRoute and VPN coexisting: We recommend considering migrating the Basic IP resources to Standard IP on **VPN** first.
 
 ## FAQ
 
-### How long does the end-to-end migration typically take?
-* The entire migration process usually takes up to 2 hours, depending on the size and configuration of your deployment.
+Depending on your current VPN gateway SKU, you might have different questions about the migration process. Here are some frequently asked questions to help you understand the migration better.
+
+### VPN gateway SKUs VpnGw1-5
+
+#### How long does the end-to-end migration typically take?
+
+The entire migration process usually takes up to 2 hours, depending on the size and configuration of your deployment.
+
+#### How long does each migration step take?
 
-### How long does each migration step take?
-* Migration step durations can vary based on environment complexity. On average:
+Migration step durations can vary based on environment complexity. On average:
 
-Prepare: Typically up to 40 minutes, with a maximum of 1 hour.<br>
-Execute: Takes around 5–10 minutes. (This is the only step where brief downtime is expected.)<br>
-Commit: Typically up to 30 minutes, with a maximum of 1 hour.
+* Prepare: Typically up to 40 minutes, with a maximum of 1 hour.
+* Execute: Takes around 5–10 minutes. (This is the only step where brief downtime is expected.)
+* Commit: Typically up to 30 minutes, with a maximum of 1 hour.
 
-### How will my gateway SKU be impacted after the Basic SKU public IP address migration?
+#### How will my gateway SKU be impacted after the Basic SKU public IP address migration?
 
 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.
 
-### Will my VPN gateway IP address change after my public IP address is migrated?
+#### Will my VPN gateway IP address change after my public IP address is migrated?
 
 * If you use the Microsoft-provided migration experience, your gateway IP address won't change.
 * 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.
 
-### Will there be any downtime?
+#### Will there be any downtime?
 
 Up to 10 minutes of downtime is expected during the Microsoft-provided migration experience.
 
-### Do I need to take any actions to migrate?
+#### Do I need to take any actions to migrate?
 
 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.
 
-### Are there any migration prerequisites?
+#### Are there any migration prerequisites?
 
 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.
 
-### Can I create a Basic SKU VPN gateway with a Basic SKU public IP address after March 31, 2025?
+#### Can I change to a Standard SKU public IP address manually?
 
-Yes, you can create a VPN gateway using the gateway Basic SKU and a Basic SKU public IP address until June 2025.
+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.
 
-### When will I be able to create a Basic SKU VPN gateway with a Standard SKU public IP address?
+#### If I delete and re-create my gateway, will my IP address change?
 
-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.
+Yes, the IP address changes 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.
 
-### Can I change to a Standard SKU public IP address manually?
+### VPN gateway Basic SKU
 
-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.
+#### Can I create a Basic SKU VPN gateway with a Basic SKU public IP address?
 
-### If I delete and re-create my gateway, will my IP address change?
+No, you can't create a Basic SKU VPN gateway with a Basic SKU public IP address after June 2025. New Basic SKU VPN gateways require a Standard public IP address SKU.
 
-Yes, the IP address changes 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.
+#### Do I need to migrate if I have a Basic SKU VPN gateway?
+
+Basic SKU VPN gateways that currently show as using a Basic SKU public IP address **do not** use the migration process to move to a Standard public IP address SKU. The only action you need to take is to remove the Basic SKU public IP reference from your gateway. 
+
+For steps to remove the Basic SKU public IP reference, see [Remove the Basic SKU public IP reference from a Basic SKU VPN gateway](basic-sku-public-ip-remove.md). Your gateway continues to use the same public IP address. Only the reference to the Basic SKU public IP resource is removed from your gateway.
 
 ## Next steps
 
 * 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).
-
-* For migration steps, see [How to migrate a Basic SKU public IP address to Standard SKU](basic-public-ip-migrate-howto.md).
+* For migration steps for non-Basic SKU VPN Gateways, see [How to migrate a Basic SKU public IP address to Standard SKU](basic-public-ip-migrate-howto.md).
+* To remove the Basic SKU public IP reference from a Basic SKU VPN gateway, see [Remove the Basic SKU public IP reference from a Basic SKU VPN gateway](basic-sku-public-ip-remove.md).

articles/vpn-gateway/basic-public-ip-migrate-howto.md

@@ -12,10 +12,11 @@ ms.author: cherylmc
 
 # How to migrate a Basic SKU public IP address to Standard SKU for VPN Gateway 
 
-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 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).
+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 more information about 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).
 
 > [!IMPORTANT]
-> Basic SKU public IP address migration for VPN Gateway is currently Generally Available for Active-Passive with some limitations (see known issues). <br> For Active-Active Gateways this is in Preview.
+> * Basic SKU public IP address migration for VPN Gateway is currently Generally Available for Active-Passive with some limitations (see known issues). <br> For Active-Active Gateways this is in Preview.
+> * The steps on this page apply to VPN gateways using gateway SKUs other than the Basic gateway SKU. If your gateway uses the Basic gateway SKU, see [Remove the Basic SKU public IP reference from a Basic SKU VPN gateway](basic-sku-public-ip-remove.md).
 
 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.
 

articles/vpn-gateway/basic-sku-public-ip-remove.md

@@ -0,0 +1,35 @@
+---
+title: Remove the Basic Public IP Reference from a Basic SKU VPN Gateway - Azure portal
+description: Learn how to remove the Basic public IP resource reference from an existing Basic SKU VPN gateway using the Azure portal.
+author: cherylmc
+ms.author: cherylmc
+ms.service: azure-vpn-gateway
+ms.topic: how-to
+ms.date: 03/06/2026
+---
+
+# Remove the Basic public IP reference from a Basic SKU VPN gateway - Azure portal
+
+Basic public IP addresses are being retired in Azure. The steps in this article help you remove the Basic SKU public IP resource reference from an existing Basic SKU VPN gateway. This change doesn't update the gateway's public IP address and doesn't interrupt connectivity.
+
+These steps apply only to Basic SKU VPN gateways that have a Basic SKU public IP resource reference. If your gateway doesn't have a Basic public IP reference, see [About migrating a Basic SKU public IP address to a Standard SKU public IP address](basic-public-ip-migrate-about.md) for information about public IP addresses and VPN Gateway.
+
+> [!NOTE]
+> * Your gateway's public IP address remains the same.
+> * There's no network interruption when you make this change.
+
+## Remove the Basic SKU public IP reference
+
+Use the following steps to remove the Basic SKU public IP resource reference from a Basic SKU VPN gateway in the Azure portal.
+
+1. In the [Azure portal](https://portal.azure.com), go to your **Virtual network gateway** resource.
+1. On the left menu, under **Settings**, select **Configuration**.
+1. On the Configuration page, verify that in the Validation section, all of the resources are showing as **Succeeded**.
+
+   :::image type="content" source="media/basic-sku-public-ip-remove/delete-reference.png" alt-text="Screenshot that shows the Configuration page with the Delete Basic Public iP Reference option.":::
+
+1. If the resources are showing as **Succeeded**, you can delete the Basic SKU public IP reference. Click **Delete Basic Public Ip Reference**.
+
+## Next steps
+
+[Learn about VPN Gateway settings](vpn-gateway-about-vpn-gateway-settings.md)