Merge pull request #234657 from mbender-ms/lb-freshness-01

load balancer - freshness passes

Author: v-dirichards

articles/load-balancer/basic/index.yml

@@ -12,7 +12,7 @@ metadata:
   ms.collection: collection
   author: mbender-ms
   ms.author: mbender
-  ms.date: 03/15/2022
+  ms.date: 04/17/2023
 
 # linkListType: architecture | concept | deploy | download | get-started | how-to-guide | learn | overview | quickstart | reference | tutorial | whats-new
 

articles/load-balancer/upgrade-basic-standard-virtual-machine-scale-sets.md

@@ -3,12 +3,12 @@ title: Upgrade from Basic to Standard for Virtual Machine Scale Sets
 titleSuffix: Azure Load Balancer
 description: This article shows you how to upgrade a load balancer from basic to standard SKU for Virtual Machine Scale Sets.
 services: load-balancer
-author: Welasco
+author: mbender-ms
 ms.service: load-balancer
 ms.topic: how-to
-ms.date: 09/22/2022
-ms.author: vsantana
-ms.custom: template-how-to
+ms.date: 04/17/2023
+ms.author: mbender
+ms.custom: template-how-to, engagement-fy23
 ---
 
 # Upgrade a basic load balancer used with Virtual Machine Scale Sets
@@ -52,7 +52,7 @@ The PowerShell module performs the following functions:
 
 - Install the latest version of [PowerShell](/powershell/scripting/install/installing-powershell)
 - Determine whether you have the latest Az PowerShell module installed (8.2.0)
-  - Install the latest Az PowerShell module](/powershell/azure/install-az-ps)
+  - Install the latest [Az PowerShell module](/powershell/azure/install-az-ps)
 
 ## Install the 'AzureBasicLoadBalancerUpgrade' module
 
@@ -115,7 +115,7 @@ PS C:\> Start-AzBasicLoadBalancerUpgrade -FailedMigrationRetryFilePathLB C:\Reco
 
 ### Will the module migrate my frontend IP address to the new Standard Load Balancer?
 
-Yes, for both public and internal load balancers, the module ensures that front end IP addresses are maintained. For public IPs, the IP is converted to a static IP prior to migration (if necessary). For internal front ends, the module will attempt to reassign the same IP address freed up when the Basic Load Balancer was deleted; if the private IP isn't available the script will fail (see [What happens if my upgrade fails mid-migration?](#what-happens-if-my-upgrade-fails-mid-migration)).
+Yes, for both public and internal load balancers, the module ensures that front end IP addresses are maintained. For public IPs, the IP is converted to a static IP prior to migration (if necessary). For internal front ends, the module attempts to reassign the same IP address freed up when the Basic Load Balancer was deleted; if the private IP isn't available the script fails (see [What happens if my upgrade fails mid-migration?](#what-happens-if-my-upgrade-fails-mid-migration)).
 
 ### How long does the Upgrade take?
 
@@ -140,36 +140,36 @@ The script migrates the following from the Basic Load Balancer to the Standard L
   - Updates the public IP SKU to Standard, if Basic
   - Upgrade all associated public IPs to the new Standard Load Balancer
 - Health Probes:
-  - All probes will be migrated to the new Standard Load Balancer
+  - All probes are migrated to the new Standard Load Balancer
 - Load balancing rules:
-  - All load balancing rules will be migrated to the new Standard Load Balancer
+  - All load balancing rules are migrated to the new Standard Load Balancer
 - Inbound NAT Rules:
-  - All user-created NAT rules will be migrated to the new Standard Load Balancer
+  - All user-created NAT rules are migrated to the new Standard Load Balancer
 - Inbound NAT Pools:
   - All inbound NAT Pools will be migrated to the new Standard Load Balancer
 - Outbound Rules:
-  - Basic load balancers don't support configured outbound rules. The script will create an outbound rule in the Standard load balancer to preserve the outbound behavior of the Basic load balancer. For more information about outbound rules, see [Outbound rules](./outbound-rules.md).
+  - Basic load balancers don't support configured outbound rules. The script creates an outbound rule in the Standard load balancer to preserve the outbound behavior of the Basic load balancer. For more information about outbound rules, see [Outbound rules](./outbound-rules.md).
 - Network security group
-  - Basic Load Balancer doesn't require a network security group to allow outbound connectivity. In case there's no network security group associated with the Virtual Machine Scale Set, a new network security group will be created to preserve the same functionality. This new network security group will be associated to the Virtual Machine Scale Set backend pool member network interfaces. It will allow the same load balancing rules ports and protocols and preserve the outbound connectivity.
+  - Basic Load Balancer doesn't require a network security group to allow outbound connectivity. In case there's no network security group associated with the Virtual Machine Scale Set, a new network security group is created to preserve the same functionality. This new network security group is associated to the Virtual Machine Scale Set backend pool member network interfaces. It allows the same load balancing rules ports and protocols and preserve the outbound connectivity.
 - Backend pools:
-  - All backend pools will be migrated to the new Standard Load Balancer
-  - All Virtual Machine Scale Set network interfaces and IP configurations will be migrated to the new Standard Load Balancer
+  - All backend pools are migrated to the new Standard Load Balancer
+  - All Virtual Machine Scale Set network interfaces and IP configurations are migrated to the new Standard Load Balancer
   - If a Virtual Machine Scale Set is using Rolling Upgrade policy, the script will update the Virtual Machine Scale Set upgrade policy to "Manual" during the migration process and revert it back to "Rolling" after the migration is completed.
 
 **Internal Load Balancer:**
 
 - Private frontend IP configuration
 - Health Probes:
-  - All probes will be migrated to the new Standard Load Balancer
+  - All probes are migrated to the new Standard Load Balancer
 - Load balancing rules:
-  - All load balancing rules will be migrated to the new Standard Load Balancer
+  - All load balancing rules are migrated to the new Standard Load Balancer
 - Inbound NAT Pools:
   - All inbound NAT Pools will be migrated to the new Standard Load Balancer
 - Inbound NAT Rules:
-  - All user-created NAT rules will be migrated to the new Standard Load Balancer
+  - All user-created NAT rules are migrated to the new Standard Load Balancer
 - Backend pools:
-  - All backend pools will be migrated to the new Standard Load Balancer
-  - All Virtual Machine Scale Set network interfaces and IP configurations will be migrated to the new Standard Load Balancer
+  - All backend pools are migrated to the new Standard Load Balancer
+  - All Virtual Machine Scale Set network interfaces and IP configurations are migrated to the new Standard Load Balancer
   - If there's a Virtual Machine Scale Set using Rolling Upgrade policy, the script will update the Virtual Machine Scale Set upgrade policy to "Manual" during the migration process and revert it back to "Rolling" after the migration is completed.
 
 >[!NOTE]
@@ -181,7 +181,7 @@ The module is designed to accommodate failures, either due to unhandled errors o
 
   1. Address the cause of the migration failure. Check the log file `Start-AzBasicLoadBalancerUpgrade.log` for details
   1. [Remove the new Standard Load Balancer](./update-load-balancer-with-vm-scale-set.md) (if created). Depending on which stage of the migration failed, you may have to remove the Standard Load Balancer reference from the Virtual Machine Scale Set network interfaces (IP configurations) and Health Probes in order to remove the Standard Load Balancer.
-  1. Locate the Basic Load Balancer state backup file. This file will either be in the directory where the script was executed, or at the path specified with the `-RecoveryBackupPath` parameter during the failed execution. The file will be named: `State_<basicLBName>_<basicLBRGName>_<timestamp>.json`
+  1. Locate the Basic Load Balancer state backup file. This file will either be in the directory where the script was executed, or at the path specified with the `-RecoveryBackupPath` parameter during the failed execution. The file is named: `State_<basicLBName>_<basicLBRGName>_<timestamp>.json`
   1. Rerun the migration script, specifying the `-FailedMigrationRetryFilePathLB <BasicLoadBalancerbackupFilePath>` and `-FailedMigrationRetryFilePathVMSS <VMSSBackupFile>` parameters instead of -BasicLoadBalancerName or passing the Basic Load Balancer over the pipeline
 
 ## Next steps

articles/load-balancer/upgrade-basic-standard.md

@@ -6,9 +6,9 @@ services: load-balancer
 author: mbender-ms
 ms.service: load-balancer
 ms.topic: how-to
-ms.date: 03/17/2022
+ms.date: 04/17/2023
 ms.author: mbender
-ms.custom: template-how-to
+ms.custom: template-how-to, engagement-fy23
 ---
 
 # Upgrade from a basic public to standard public load balancer
@@ -44,7 +44,7 @@ An Azure PowerShell script is available that does the following procedures:
 
 * If the load balancer doesn't have a frontend IP configuration or backend pool, you'll encounter an error running the script. Ensure the load balancer has a frontend IP and backend pool
 
-* The script cannot migrate Virtual Machine Scale Set from Basic Load Balancer's backend to Standard Load Balancer's backend. For this type of upgrade, see [Upgrade a basic load balancer used with Virtual Machine Scale Sets](./upgrade-basic-standard-virtual-machine-scale-sets.md) for instructions and more information.
+* The script can't migrate Virtual Machine Scale Set from Basic Load Balancer's backend to Standard Load Balancer's backend. For this type of upgrade, see [Upgrade a basic load balancer used with Virtual Machine Scale Sets](./upgrade-basic-standard-virtual-machine-scale-sets.md) for instructions and more information.
 
 ### Change allocation method of the public IP address to static
 
@@ -75,32 +75,32 @@ Download the migration script from the [PowerShell Gallery](https://www.powershe
 
 There are two options depending on your local PowerShell environment setup and preferences:
 
-* If you don’t have the Azure Az modules installed, or don’t mind uninstalling the Azure Az modules, use the `Install-Script` option to run the script.
+* If you don’t have the Az PowerShell module installed, or don’t mind uninstalling the Az PowerShell module, use the `Install-Script` option to run the script.
 
-* If you need to keep the Azure Az modules, download the script and run it directly.
+* If you need to keep the Az PowerShell module, download the script and run it directly.
 
-To determine if you have the Azure Az modules installed, run `Get-InstalledModule -Name az`. If you don't see any installed Az modules, then you can use the `Install-Script` method.
+To determine if you have the Az PowerShell module installed, run `Get-InstalledModule -Name az`. If you don't see any installed Az PowerShell module, then you can use the `Install-Script` method.
 
 ### Install with Install-Script
 
-To use this option, don't have the Azure Az modules installed on your computer. If they're installed, the following command displays an error. Uninstall the Azure Az modules, or use the other option to download the script manually and run it.
+To use this option, don't have the Az PowerShell module installed on your computer. If they're installed, the following command displays an error. Uninstall the Az PowerShell module, or use the other option to download the script manually and run it.
 
 Run the script with the following command:
 
 ```azurepowershell
 Install-Script -Name AzurePublicLBUpgrade
 ```
-This command also installs the required Az modules.  
+This command also installs the required Az PowerShell module.  
 
 ### Install with the script directly
 
-If you do have Azure Az modules installed and can't uninstall them, or don't want to uninstall them,you can manually download the script using the **Manual Download** tab in the script download link. The script is downloaded as a raw **nupkg** file. To install the script from this **nupkg** file, see [Manual Package Download](/powershell/scripting/gallery/how-to/working-with-packages/manual-download).
+If you do have Az PowerShell module installed and can't uninstall it, or don't want to uninstall it,you can manually download the script using the **Manual Download** tab in the script download link. The script is downloaded as a raw **nupkg** file. To install the script from this **nupkg** file, see [Manual Package Download](/powershell/gallery/gallery/how-to/working-with-packages/manual-download)
 
 To run the script:
 
 1. Use `Connect-AzAccount` to connect to Azure.
 
-2. Use `Import-Module Az` to import the Az modules.
+2. Use `Import-Module Az` to import the Az PowerShell module.
 
 3. Examine the required parameters:
 

articles/load-balancer/upgrade-basicInternal-standard.md

@@ -6,7 +6,7 @@ services: load-balancer
 author: mbender-ms
 ms.service: load-balancer
 ms.topic: how-to
-ms.date: 12/15/2022
+ms.date: 04/17/2023
 ms.author: mbender
 ms.custom: template-how-to, engagement-fy23
 ---
@@ -70,7 +70,7 @@ This command also installs the required Az PowerShell module.
 
 ### Install using the Manual Download method
 
-If you do have some Azure Az PowerShell module installed and can't uninstall them (or don't want to uninstall them), you can manually download the script using the **Manual Download** tab in the script download link. The script is downloaded as a raw nupkg file. To install the script from this nupkg file, see [Manual Package Download](/powershell/scripting/gallery/how-to/working-with-packages/manual-download).
+If you do have some Azure Az PowerShell module installed and can't uninstall them (or don't want to uninstall them), you can manually download the script using the **Manual Download** tab in the script download link. The script is downloaded as a raw nupkg file. To install the script from this nupkg file, see [Manual Package Download](/powershell/gallery/gallery/how-to/working-with-packages/manual-download).
 
 ### Run the script
 

articles/load-balancer/upgrade-internalbasic-to-publicstandard.md

@@ -5,9 +5,9 @@ description: Learn how to upgrade a basic internal load balancer to a standard p
 author: mbender-ms
 ms.service: load-balancer
 ms.topic: how-to
-ms.date: 03/17/2022
+ms.date: 04/17/2023
 ms.author: mbender
-ms.custom: template-how-to
+ms.custom: template-how-to, engagement-fy23
 ---
 
 # Upgrade an internal basic load balancer - Outbound connections required
@@ -47,7 +47,7 @@ An Azure PowerShell script is available that does the following procedures:
 
 * If the load balancer doesn't have a frontend IP configuration or backend pool, you'll encounter an error running the script. Ensure the load balancer has a frontend IP and backend pool
 
-* The script cannot migrate Virtual Machine Scale Set from Basic Load Balancer's backend to Standard Load Balancer's backend. For this type of upgrade, see [Upgrade a basic load balancer used with Virtual Machine Scale Sets](./upgrade-basic-standard-virtual-machine-scale-sets.md) for instructions and more information.
+* The script can't migrate Virtual Machine Scale Set from Basic Load Balancer's backend to Standard Load Balancer's backend. For this type of upgrade, see [Upgrade a basic load balancer used with Virtual Machine Scale Sets](./upgrade-basic-standard-virtual-machine-scale-sets.md) for instructions and more information.
 
 ## Download the script
 
@@ -57,32 +57,32 @@ Download the migration script from the [PowerShell Gallery](https://www.powershe
 
 There are two options depending on your local PowerShell environment setup and preferences:
 
-* If you don’t have the Azure Az modules installed, or don’t mind uninstalling the Azure Az modules, use the `Install-Script` option to run the script.
+* If you don’t have the Az PowerShell module installed, or don’t mind uninstalling the Az PowerShell module, use the `Install-Script` option to run the script.
 
-* If you need to keep the Azure Az modules, download the script and run it directly.
+* If you need to keep the Az PowerShell module, download the script and run it directly.
 
-To determine if you have the Azure Az modules installed, run `Get-InstalledModule -Name az`. If you don't see any installed Az modules, then you can use the `Install-Script` method.
+To determine if you have the Az PowerShell module installed, run `Get-InstalledModule -Name az`. If the Az PowerShell module isn't installed, you can use the `Install-Script` method.
 
 ### Install with Install-Script
 
-To use this option, don't have the Azure Az modules installed on your computer. If they're installed, the following command displays an error. Uninstall the Azure Az modules, or use the other option to download the script manually and run it.
+To use this option, don't have the Az PowerShell module installed on your computer. If they're installed, the following command displays an error. Uninstall the Az PowerShell module, or use the other option to download the script manually and run it.
 
 Run the script with the following command:
 
 ```azurepowershell
 Install-Script -Name AzureLBUpgrade
 ```
-This command also installs the required Az modules.  
+This command also installs the required Az PowerShell module.  
 
 ### Install with the script directly
 
-If you do have Azure Az modules installed and can't uninstall them, or don't want to uninstall them,you can manually download the script using the **Manual Download** tab in the script download link. The script is downloaded as a raw **nupkg** file. To install the script from this **nupkg** file, see [Manual Package Download](/powershell/scripting/gallery/how-to/working-with-packages/manual-download).
+If you do have Az PowerShell module installed and can't uninstall them, or don't want to uninstall them,you can manually download the script using the **Manual Download** tab in the script download link. The script is downloaded as a raw **nupkg** file. To install the script from this **nupkg** file, see [Manual Package Download](/powershell/gallery/gallery/how-to/working-with-packages/manual-download).
 
 To run the script:
 
 1. Use `Connect-AzAccount` to connect to Azure.
 
-2. Use `Import-Module Az` to import the Az modules.
+2. Use `Import-Module Az` to import the Az PowerShell module.
 
 3. Examine the required parameters:
 

articles/load-balancer/virtual-network-ipv4-ipv6-dual-stack-standard-load-balancer-cli.md

@@ -1,15 +1,15 @@
 ---
 title: Deploy IPv6 dual stack application - Standard Load Balancer - CLI
 titlesuffix: Azure Virtual Network
-description: This article shows how deploy an IPv6 dual stack application in Azure virtual network using Azure CLI.
+description: This article shows how to deploy an IPv6 dual stack application in Azure virtual network using Azure CLI.
 services: virtual-network
-author: KumudD
+author: mbender-ms
 ms.service: virtual-network
 ms.topic: how-to
 ms.workload: infrastructure-services
-ms.date: 03/31/2020
-ms.author: kumud
-ms.custom: template-how-to, devx-track-azurecli
+ms.date: 04/17/2023
+ms.author: mbender
+ms.custom: template-how-to, devx-track-azurecli, engagement-fy23
 ---
 
 # Deploy an IPv6 dual stack application in Azure virtual network using Azure CLI
@@ -178,7 +178,7 @@ az vm availability-set create \
 
 ### Create network security group
 
-Create a network security group for the rules that will govern inbound and outbound communication in your VNet.
+Create a network security group for the rules that govern inbound and outbound communication in your VNet.
 
 #### Create a network security group
 
@@ -321,7 +321,7 @@ az network nic ip-config create \
 
 ### Create virtual machines
 
-Create the VMs with [az vm create](/cli/azure/vm#az-vm-create). The following example creates two VMs and the required virtual network components if they do not already exist. 
+Create the VMs with [az vm create](/cli/azure/vm#az-vm-create). The following example creates two VMs and the required virtual network components if they don't already exist. 
 
 Create virtual machine *dsVM0* as follows: