Merge pull request #305078 from mbender-ms/ip-services-acrolinx-fixes

ip services | Acrolinx | Update scores above 80

Author: prmerger-automator[bot]

articles/virtual-network/ip-services/public-ip-upgrade-vm.md

@@ -13,24 +13,26 @@ ms.topic: how-to
 
 # Upgrade public IP addresses attached to VM from Basic to Standard
 
->[!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.
+> [!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.
 
 For more information about the retirement of Basic SKU Public IPs and the benefits of Standard SKU Public IPs, see [here](public-ip-basic-upgrade-guidance.md)
 
 ## Upgrade overview
 
 This script upgrades any Public IP Addresses attached to VM from Basic to Standard SKU. In order to perform the upgrade, the Public IP Address allocation method is set to static before being disassociated from the VM. Once disassociated, the Public IP SKU is upgraded to Standard, then the IP is re-associated with the VM.
 
-Because the Public IP allocation is set to 'Static' before detaching from the VM, the IP address won't change during the upgrade process, even in the event of a script failure. The module double-checks that the Public IP allocation method is 'Static' prior to detaching the Public IP from the VM. 
+Because the Public IP allocation is set to *Static* before detaching from the VM, the IP address won't change during the upgrade process, even if the script fails. The module double-checks that the Public IP allocation method is *Static* prior to detaching the Public IP from the VM.
 
 The module logs all upgrade activity to a file named `PublicIPUpgrade.log`, created in the same location where the module was executed (by default). 
 
 ## Constraints / Unsupported Scenarios
 
 - **VMs with NICs associated to a Load Balancer**: Because the Load Balancer and Public IP SKUs associated with a VM must match, it isn't possible to upgrade the instance-level Public IP addresses associated with a VM when the VM's NICs are also associated with a Load Balancer, either through Backend Pool or NAT Pool membership. Use the scripts [Upgrade a Basic Load Balancer to Standard SKU](../../load-balancer/upgrade-basic-standard-with-powershell.md) to upgrade both the Load Balancer and Public IPs at the same time.
-- **VMs without a Network Security Group**: VMs with IPs to be upgraded must have a Network Security Group (NSG) associated with either the subnet of each IP configuration with a Public IP, or with the NIC directly. This is because Standard SKU Public IPs are "secure by default", meaning that any traffic to the Public IP must be explicitly allowed at an NSG to reach the VM. Basic SKU Public IPs allow any traffic by default. Upgrading Public IP SKUs without an NSG would result in inbound internet traffic to the Public IP previously allowed with the Basic SKU being blocked post-migration. See: [Public IP SKUs](public-ip-addresses.md#sku)
-- **Virtual Machine Scale Sets with Public IP configurations**: If you have a virtual machine scale set (uniform model) with public IP configurations per instance, note these configurations aren't Public IP resources and as such cannot be upgraded. Instead, you can remove the Basic IP configuration and use the SKU property to specify that Standard IP configurations are required for each virtual machine scale set instance as shown [here](/azure/virtual-machine-scale-sets/virtual-machine-scale-sets-networking#public-ipv4-per-virtual-machine).
+
+- **VMs without a Network Security Group**: VMs with IPs to be upgraded must have a Network Security Group (NSG) associated with either the subnet of each IP configuration with a Public IP, or with the NIC directly. This is because Standard SKU Public IPs are "secure by default," meaning that any traffic to the Public IP must be explicitly allowed at an NSG to reach the VM. Basic SKU Public IPs allow any traffic by default. Upgrading Public IP SKUs without an NSG would result in inbound internet traffic to the Public IP previously allowed with the Basic SKU being blocked post-migration. See: [Public IP SKUs](public-ip-addresses.md#sku)
+
+- **Virtual Machine Scale Sets with Public IP configurations**: If you have a virtual machine scale set (uniform model) with public IP configurations per instance, note these configurations aren't Public IP resources and as such can't be upgraded. Instead, you can remove the Basic IP configuration and use the SKU property to specify that Standard IP configurations are required for each virtual machine scale set instance as shown [here](/azure/virtual-machine-scale-sets/virtual-machine-scale-sets-networking#public-ipv4-per-virtual-machine).
 
 ### Prerequisites
 
@@ -52,13 +54,14 @@ PS C:\> Install-Module -Name AzureVMPublicIPUpgrade -Scope CurrentUser -Reposito
     ```powershell
     PS C:\> Connect-AzAccount -Tenant <TenantId> -Subscription <SubscriptionId>
     ```
-2. Locate the VM with the attached Basic Public IPs that you wish to upgrade. Record its name and resource group name.
 
-3. Examine the module parameters:
+1. Locate the VM with the attached Basic Public IPs that you wish to upgrade. Record its name and resource group name.
+
+1. Examine the module parameters:
     - *VMName [string] Required* - This parameter is the name of your VM.
     - *ResourceGroupName [string] Required* - This parameter is the resource group for your VM with the Basic Public IPs attached that you want to upgrade.
 
-4. Run the Upgrade command.
+1. Run the Upgrade command.
 
 ### Example uses of the script
 
@@ -74,7 +77,7 @@ To evaluate upgrading a single VM, without making any changes, add the -WhatIf p
     Start-VMPublicIPUpgrade -VMName 'myVM' -ResourceGroupName 'myRG' -WhatIf
 ```
 
-To upgrade all VMs in a resource group, skipping VMs that do not have Network Security Groups.
+To upgrade all VMs in a resource group, skipping VMs that don't have Network Security Groups.
 
 ```powershell
     Get-AzVM -ResourceGroupName 'myRG' | Start-VMPublicIPUpgrade -skipVMMissingNSG
@@ -92,7 +95,7 @@ To recover from a failed upgrade, pass the recovery log file path to the script
 
 ## Common questions
 
-### How long will the migration take and how long will my VM be inaccessible at its Public IP?
+### How long will the migration take and how long will my virtual machine be inaccessible at its Public IP?
 
 The time it takes to upgrade a VM's Public IPs depends on the number of Public IPs and Network Interfaces associated with the VM. In testing, a VM with a single NIC and Public IP takes between 1 and 2 minutes to upgrade. Each NIC on the VM adds about another minute, and each Public IP adds a few seconds each.
 
@@ -102,22 +105,22 @@ It isn't possible to downgrade a Public IP address from Standard to Basic.
 
 ### Can I test a migration before executing? 
 
-There is no way to evaluate upgrading a Public IP without completing the action. However, this script includes a `-whatif` parameter, which checks that your VM will support the upgrade and walks through the steps without taking action. 
+There's no way to evaluate upgrading a Public IP without completing the action. However, this script includes a `-whatif` parameter, which checks that your VM supports the upgrade and walks through the steps without taking action. 
 
 ### Does the script support Zonal Basic SKU Public IPs? 
 
 Yes, the process of upgrading a Zonal Basic SKU Public IP to a Zonal Standard SKU Public IP is identical and works in the script.
 
 ### If I specify a NIC associated with a public IP targeted for migration in the Application Gateway backend pool, will this script remove it from the pool?
 
-Yes, it will be removed. After running the script, you will need to manually reassign the NIC to the Application Gateway backend pool.
+Yes, it's removed. After running the script, you'll need to manually reassign the NIC to the Application Gateway backend pool.
 Alternatively, you can avoid this issue by explicitly specifying the private IP address in the backend pool configuration before migration.
 
 ## Use Resource Graph to list VMs with Public IPs requiring upgrade
 
 ### Query to list virtual machines with Basic SKU public IP addresses
 
-This query returns a list of virtual machine IDs with Basic SKU public IP addresses attached. 
+This query returns a list of virtual machine IDs with Basic SKU public IP addresses attached.
 
 ```kusto
 Resources