Merge pull request #253079 from mbender-ms/lb-freshness-september

Load Balancer - freshness updates for september

Author: v-dirichards

articles/load-balancer/ipv6-add-to-existing-vnet-cli.md

@@ -3,14 +3,14 @@ title: Add IPv6 to an IPv4 application in Azure virtual network - Azure CLI
 titlesuffix: Azure Virtual Network
 description: This article shows how to deploy IPv6 addresses to an existing application in Azure virtual network using Azure CLI.
 services: virtual-network
-author: asudbring
+author: mbender-ms
 ms.service: virtual-network
 ms.topic: how-to
-ms.workload: infrastructure-services
-ms.date: 03/31/2020
-ms.author: allensu
+ms.date: 09/27/2023
+ms.author: mbender
 ms.custom: devx-track-azurecli, template-how-to
 ms.devlang: azurecli
+ROBOTS: NOINDEX
 ---
 
 # Add IPv6 to an IPv4 application in Azure virtual network using Azure CLI
@@ -27,7 +27,7 @@ This article shows you how to add IPv6 addresses to an application that is using
 
 ## Create IPv6 addresses
 
-Create public IPv6 address with with [az network public-ip create](/cli/azure/network/public-ip) for your Standard Load Balancer. The following example creates an IPv6 public IP address named *PublicIP_v6* in the *myResourceGroupSLB* resource group:
+Create public IPv6 address with [az network public-ip create](/cli/azure/network/public-ip) for your Standard Load Balancer. The following example creates an IPv6 public IP address named *PublicIP_v6* in the *myResourceGroupSLB* resource group:
 
 ```azurecli-interactive
 az network public-ip create \
@@ -134,18 +134,19 @@ az network nic ip-config create \
 ## View IPv6 dual stack virtual network in Azure portal
 
 You can view the IPv6 dual stack virtual network in Azure portal as follows:
-1. In the portal's search bar, enter *myVnet*.
-2. When **myVnet** appears in the search results, select it. This launches the **Overview** page of the dual stack virtual network named *myVNet*. The dual stack virtual network shows the three NICs with both IPv4 and IPv6 configurations located in the dual stack subnet named *mySubnet*.
+1. In the portal's search bar, enter **virtual networks** and 
+1. In the **Virtual Networks** window, select **myVNet**.
+1.  Select **Connected devices** under **Settings** to view the attached network interfaces. The dual stack virtual network shows the three NICs with both IPv4 and IPv6 configurations.
 
-  ![IPv6 dual stack virtual network in Azure](./media/ipv6-add-to-existing-vnet-powershell/ipv6-dual-stack-vnet.png)
+    :::image type="content" source="media/ipv6-add-to-existing-vnet-powershell/ipv6-dual-stack-addresses.png" alt-text="Screenshot of connected devices settings displaying IPv4 and IPv6 addresses on network interfaces.":::
 
 
 ## Clean up resources
 
-When no longer needed, you can use the [Remove-AzResourceGroup](/powershell/module/az.resources/remove-azresourcegroup) command to remove the resource group, VM, and all related resources.
+When no longer needed, you can use the [az group delete](/cli/azure/group#az-group-delete) command to remove the resource group, VM, and all related resources.
 
 ```azurecli-interactive
-az group delete --name MyAzureResourceGroupSLB
+ az group delete --name MyAzureResourceGroupSLB
 ```
 
 ## Next steps

articles/load-balancer/ipv6-add-to-existing-vnet-powershell.md

@@ -3,14 +3,14 @@ title: Add an IPv4 application to IPv6 in Azure Virtual Network - PowerShell
 titlesuffix: Azure Virtual Network
 description: This article shows how to deploy IPv6 addresses to an existing application in Azure virtual network using Azure PowerShell.
 services: virtual-network
-author: asudbring
-manager: mtillman
+author: mbender-ms
+manager: kumudd
 ms.service: virtual-network
 ms.topic: how-to
-ms.workload: infrastructure-services
-ms.date: 03/31/2020
-ms.author: allensu 
+ms.date: 09/27/2023
+ms.author: mbender
 ms.custom: devx-track-azurepowershell, template-how-to
+ROBOTS: NOINDEX
 ---
 
 # Add an IPv4 application to IPv6 in Azure virtual network using PowerShell
@@ -23,7 +23,7 @@ This article shows you how to add IPv6 connectivity to an existing IPv
 
 [!INCLUDE [cloud-shell-try-it.md](../../includes/cloud-shell-try-it.md)]
 
-If you choose to install and use PowerShell locally, this article requires the Azure PowerShell module version 6.9.0 or later. Run `Get-Module -ListAvailable Az` to find the installed version. If you need to upgrade, see [Install Azure PowerShell module](/powershell/azure/install-azure-powershell). If you are running PowerShell locally, you also need to run `Connect-AzAccount` to create a connection with Azure.
+If you choose to install and use PowerShell locally, this article requires the Azure PowerShell module version 6.9.0 or later. Run `Get-Module -ListAvailable Az` to find the installed version. If you need to upgrade, see [Install Azure PowerShell module](/powershell/azure/install-azure-powershell). If you're running PowerShell locally, you also need to run `Connect-AzAccount` to create a connection with Azure.
 
 ## Prerequisites
 
@@ -150,10 +150,12 @@ $NIC_3 | Set-AzNetworkInterface
 ## View IPv6 dual stack virtual network in Azure portal
 
 You can view the IPv6 dual stack virtual network in Azure portal as follows:
-1. In the portal's search bar, enter *myVnet*.
-2. When **myVnet** appears in the search results, select it. This launches the **Overview** page of the dual stack virtual network named *myVNet*. The dual stack virtual network shows the three NICs with both IPv4 and IPv6 configurations located in the dual stack subnet named *mySubnet*.
+1. In the portal's search bar, enter **virtual networks** and 
+1. In the **Virtual Networks** window, select **myVNet**.
+1.  Select **Connected devices** under **Settings** to view the attached network interfaces. The dual stack virtual network shows the three NICs with both IPv4 and IPv6 configurations.
 
-  ![IPv6 dual stack virtual network in Azure](./media/ipv6-add-to-existing-vnet-powershell/ipv6-dual-stack-vnet.png)
+    :::image type="content" source="media/ipv6-add-to-existing-vnet-powershell/ipv6-dual-stack-addresses.png" alt-text="Screenshot of connected devices settings displaying IPv4 and IPv6 addresses on network interfaces.":::
+ 
 
 ## Clean up resources
 

articles/load-balancer/ipv6-configure-standard-load-balancer-template-json.md

@@ -3,14 +3,15 @@ title: Deploy an IPv6 dual stack application in Azure virtual network - Resource
 titlesuffix: Azure Virtual Network
 description: This article shows how to deploy an IPv6 dual stack application with Standard Load Balancer in Azure virtual network using Azure Resource Manager VM templates.
 services: virtual-network
-author: asudbring
-manager: mtillman
+author: mbender-ms
+manager: kumudD
 ms.service: virtual-network
 ms.topic: how-to
 ms.workload: infrastructure-services
 ms.date: 03/31/2020
-ms.author: allensu
+ms.author: mbender
 ms.custom: template-how-to, devx-track-arm-template
+ROBOTS: NOINDEX
 ---
 
 # Deploy an IPv6 dual stack application in Azure virtual network - Template

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

@@ -5,7 +5,7 @@ author: mbender-ms
 ms.service: load-balancer
 ms.author: mbender
 ms.topic: conceptual
-ms.date: 09/19/2022
+ms.date: 09/27/2023
 ms.custom: template-concept
 #customer-intent: As an cloud engineer with basic Load Balancer services, I need guidance and direction on migrating my workloads off basic to standard SKUs
 ---
@@ -15,7 +15,7 @@ ms.custom: template-concept
 >[!Important]
 >On September 30, 2025, Basic Load Balancer will be retired. For more information, see the [official announcement](https://azure.microsoft.com/updates/azure-basic-load-balancer-will-be-retired-on-30-september-2025-upgrade-to-standard-load-balancer/). If you are currently using Basic Load Balancer, make sure to upgrade to Standard Load Balancer prior to the retirement date. This article will help guide you through the upgrade process. 
 
-In this article, we'll discuss guidance for upgrading your Basic Load Balancer instances to Standard Load Balancer. Standard Load Balancer is recommended for all production instances and provides many [key differences](#basic-load-balancer-sku-vs-standard-load-balancer-sku) to your infrastructure.
+In this article, we discuss guidance for upgrading your Basic Load Balancer instances to Standard Load Balancer. Standard Load Balancer is recommended for all production instances and provides many [key differences](#basic-load-balancer-sku-vs-standard-load-balancer-sku) to your infrastructure.
 
 ## Steps to complete the upgrade
 
@@ -47,7 +47,7 @@ This section lists out some key differences between these two Load Balancer SKUs
 | **[Multiple front ends](load-balancer-multivip-overview.md)** | Inbound and [outbound](load-balancer-outbound-connections.md) | Inbound only |
 | **Management Operations** | Most operations < 30 seconds | Most operations 60-90+ seconds |
 | **SLA** | [99.99%](https://azure.microsoft.com/support/legal/sla/load-balancer/v1_0/) | Not available |
-| **Global VNet Peering Support** | Standard ILB is supported via Global VNet Peering | Not supported |
+| **Global Virtual Network Peering Support** | Standard ILB is supported via Global Virtual Network Peering | Not supported |
 | **[NAT Gateway Support](../virtual-network/nat-gateway/nat-overview.md)** | Both Standard ILB and Standard Public Load Balancer are supported via Nat Gateway | Not supported |
 | **[Private Link Support](../private-link/private-link-overview.md)** | Standard ILB is supported via Private Link | Not supported |
 | **[Global tier (Preview)](cross-region-overview.md)** | Standard Load Balancer supports the Global tier for Public LBs enabling cross-region load balancing | Not supported |

articles/load-balancer/load-balancer-multivip-overview.md

@@ -18,7 +18,7 @@ Azure Load Balancer allows you to load balance services on multiple ports, multi
 
 This article describes the fundamentals of  load balancing across multiple IP addresses using the same port and protocol. If you only intend to expose services on one IP address, you can find simplified instructions for [public](./quickstart-load-balancer-standard-public-portal.md) or [internal](./quickstart-load-balancer-standard-internal-portal.md) load balancer configurations. Adding multiple frontends is incremental to a single frontend configuration. Using the concepts in this article, you can expand a simplified configuration at any time.
 
-When you define an Azure Load Balancer, a frontend and a backend pool configuration are connected with a load balancing rule. The health probe referenced by the load balancing rule is used to determine the health of a VM on a certain port and protocol. Based on the health probe results, new flows are sent to VMs in the backend pool. The frontend is defined by a three-tuple comprised of an IP address (public or internal), a transport protocol (UDP or TCP), and a port number from the load balancing rule. The backend pool is a collection of Virtual Machine IP configurations (part of the NIC resource) which reference the Load Balancer backend pool. 
+When you define an Azure Load Balancer, a frontend and a backend pool configuration are connected with a load balancing rule. The health probe referenced by the load balancing rule is used to determine the health of a VM on a certain port and protocol. Based on the health probe results, new flows are sent to VMs in the backend pool. The frontend is defined using a three-tuple comprised of an IP address (public or internal), a transport protocol (UDP or TCP), and a port number from the load balancing rule. The backend pool is a collection of Virtual Machine IP configurations (part of the NIC resource) which reference the Load Balancer backend pool. 
 
 The following table contains some example frontend configurations:
 
@@ -36,10 +36,10 @@ Azure Load Balancer provides flexibility in defining the load balancing rules. A
 1. The default rule with no backend port reuse.
 2. The Floating IP rule where backend ports are reused.
 
-Azure Load Balancer allows you to mix both rule types on the same load balancer configuration. The load balancer can use them simultaneously for a given VM, or any combination, if you abide by the constraints of the rule. The rule type you choose depends on the requirements of your application and the complexity of supporting that configuration. You should evaluate which rule types are best for your scenario. We'll explore these scenarios further by starting with the default behavior.
+Azure Load Balancer allows you to mix both rule types on the same load balancer configuration. The load balancer can use them simultaneously for a given VM, or any combination, if you abide by the constraints of the rule. The rule type you choose depends on the requirements of your application and the complexity of supporting that configuration. You should evaluate which rule types are best for your scenario. We explore these scenarios further by starting with the default behavior.
 
 ## Rule type #1: No backend port reuse
-:::image type="content" source="media/load-balancer-multivip-overview/load-balancer-multivip.png" alt-text="Diagram of Load Balancer traffice with no backend port reuse.":::
+:::image type="content" source="media/load-balancer-multivip-overview/load-balancer-multivip.png" alt-text="Diagram of Load Balancer traffic with no backend port reuse.":::
 
 In this scenario, the frontends are configured as follows:
 
@@ -76,7 +76,7 @@ If you want to reuse the backend port across multiple rules, you must enable Flo
 
 *Floating IP* is Azure's terminology for a portion of what is known as Direct Server Return (DSR). DSR consists of two parts: a flow topology and an IP address mapping scheme. At a platform level, Azure Load Balancer always operates in a DSR flow topology regardless of whether Floating IP is enabled or not. This means that the outbound part of a flow is always correctly rewritten to flow directly back to the origin. 
 
-With the default rule type, Azure exposes a traditional load balancing IP address mapping scheme for ease of use. Enabling Floating IP changes the IP address mapping scheme to allow for more flexibility as explained below. 
+With the default rule type, Azure exposes a traditional load balancing IP address mapping scheme for ease of use. Enabling Floating IP changes the IP address mapping scheme to allow for more flexibility. 
 
 :::image type="content" source="media/load-balancer-multivip-overview/load-balancer-multivip-dsr.png" alt-text="Diagram of load balancer traffic for multiple frontend IPs with floating IP.":::