DocMentor title, description, H1 updates + Acrolinx

Author: mbender-ms

articles/virtual-network/ip-services/public-ip-basic-upgrade-guidance.md

@@ -1,22 +1,22 @@
 ---
-title: Upgrading a basic public IP address to standard SKU - Guidance
-description: Overview of upgrade options and guidance for migrating basic public IP to standard public IP for future basic public IP address retirement
+title: Upgrade Basic Public IP Address to Standard SKU in Azure
+description: Upgrade basic public IP addresses to standard SKU in Azure. Learn migration steps, compare SKUs, and prepare for the September 30 2025 retirement.
 ms.service: azure-virtual-network
 ms.subservice: ip-services
 ms.custom: devx-track-azurecli
 ms.topic: overview
 author: mbender-ms
 ms.author: mbender
-ms.date: 01/28/2025
+ms.date: 05/12/2025
 # Customer intent: As an cloud engineer with Basic public IP services, I need guidance and direction on migrating my workloads off basic to Standard SKUs
 ---
 
-# Upgrading a basic public IP address to Standard SKU - Guidance
+# Upgrade Basic Public IP Address to Standard SKU in Azure
 
 >[!Important]
 >On September 30, 2025, Basic SKU public IPs will be retired. For more information, see the [official announcement](https://azure.microsoft.com/updates/upgrade-to-standard-sku-public-ip-addresses-in-azure-by-30-september-2025-basic-sku-will-be-retired/). If you are currently using Basic SKU public IPs, make sure to upgrade to Standard SKU public IPs prior to the retirement date. This article will help guide you through the upgrade process. 
 
-In this article, learn guidance for upgrading your Basic SKU public IPs to Standard SKU. Standard public IPs are recommended for all production instances and provide many [key differences](#basic-sku-vs-standard-sku) to your infrastructure.
+This article explains how to upgrade your Basic SKU public IPs to Standard SKU. Upgrading to Standard public IPs ensures continued support after retirement and [provides enhanced security and availability](#basic-sku-vs-standard-sku) for your workloads.
 ## Steps to complete the upgrade 
 
 We recommend the following approach to upgrade to Standard SKU public IP addresses. 
@@ -42,12 +42,12 @@ We recommend the following approach to upgrade to Standard SKU public IP address
   | Virtual Machine | Use scripts or manually detach and upgrade public IPs. For standalone virtual machines, you can use the [upgrade script](public-ip-upgrade-vm.md) or for virtual machines in an availability set use [this script](public-ip-upgrade-availability-set.md). |
   | Virtual Machine Scale Sets | [Replace basic SKU instance public IP addresses](/azure/virtual-machine-scale-sets/virtual-machine-scale-sets-networking#public-ipv4-per-virtual-machine) with new standard SKU. |
   | Load Balancer (Basic SKU) | New Load Balancer SKU required. Use the upgrade script [Upgrade Basic Load Balancer to Standard SKU](../../load-balancer/upgrade-basic-standard-with-powershell.md) to upgrade to Standard Load Balancer. |
-  | VPN Gateway (using Basic IPs) | A migration path will be provided in the future. When this migration path is available, we'll update this decision path with migration information and send out a service health alert. For more information, see [Migrating a basic SKU FAQ](../../vpn-gateway/vpn-gateway-vpn-faq.md#migrating-a-basic-sku-public-ip-address-to-standard-sku). |
+  | VPN Gateway (using Basic IPs) | A migration path will be provided in the future. When this migration path is available, we update this decision path with migration information and send out a service health alert. For more information, see [Migrating a basic SKU FAQ](../../vpn-gateway/vpn-gateway-vpn-faq.md#migrating-a-basic-sku-public-ip-address-to-standard-sku). |
   |  ExpressRoute Gateway (using Basic IPs) | New ExpressRoute Gateway is required. Follow the [ExpressRoute Gateway migration guidance](../../expressroute/gateway-migration.md) for upgrading from Basic to Standard SKU.  |
   | Application Gateway (v1 SKU) | New AppGW SKU required. Use this [migration script to migrate from v1 to v2](../../application-gateway/migrate-v1-v2.md).  |
 
 > [!NOTE]
-> If you have a virtual machine scale set (uniform model) with public IP configurations per instance, note these are not Public IP resources and as such cannot be upgraded; a new public IP address is required. You can use the SKU property to specify that Standard IP configurations are required for each VMSS instance as shown [here](/azure/virtual-machine-scale-sets/virtual-machine-scale-sets-networking#public-ipv4-per-virtual-machine). 
+> If you have a virtual machine scale set (uniform model) with public IP configurations per instance, note these aren't Public IP resources and as such can't be upgraded; a new public IP address is required. You can use the SKU property to specify that Standard IP configurations are required for each VMSS instance as shown [here](/azure/virtual-machine-scale-sets/virtual-machine-scale-sets-networking#public-ipv4-per-virtual-machine). 
 
 ## Basic SKU vs. Standard SKU 
 
@@ -77,7 +77,7 @@ Use the Azure portal, Azure PowerShell, or Azure CLI to help upgrade from Basic
 ## FAQ
 
 ### Will the Basic SKU public IP retirement impact Cloud Services Extended Support (CSES) deployments?
-No, this retirement will not impact your existing or new deployments on CSES. This means that you can still create (via non-Azure Portal methods; for example, Azure CLI, Powershell, etc) and use Basic SKU public IPs for CSES deployments. However, we advise using Standard SKU on ARM native resources that don't depend on CSES when possible, because Standard has more advantages than Basic.
+No, this retirement won't impact your existing or new deployments on CSES. This means that you can still create (via non-Azure Portal methods; for example, Azure CLI, PowerShell, etc.) and use Basic SKU public IPs for CSES deployments. However, we advise using Standard SKU on ARM native resources that don't depend on CSES when possible, because Standard has more advantages than Basic.
 
 ## Next steps