Merge pull request #279596 from mbender-ms/lb-freshness-june-2024-V

load balancer - Freshness Updates - June 2024 - Part V

Author: denrea

articles/load-balancer/howto-load-balancer-imds.md

@@ -6,7 +6,7 @@ services: load-balancer
 author: mbender-ms
 ms.service: load-balancer
 ms.topic: how-to
-ms.date: 05/08/2023
+ms.date: 06/28/2024
 ms.author: mbender
 ms.custom: template-how-to
 ---
@@ -23,7 +23,7 @@ ms.custom: template-how-to
 
 ## Schema breakdown
 
-| Data | Description | Version introduced |
+| **Data** | **Description** | **Version introduced** |
 |------|-------------|--------------------|
 | `publicIpAddresses` | The instance level Public or Private IP of the specific Virtual Machine instance | 2020-10-01
 | `inboundRules` | List of load balancing rules or inbound NAT rules using which the Load Balancer directs traffic to the specific Virtual Machine instance. Frontend IP addresses and the Private IP addresses listed here belong to the Load Balancer.  | 2020-10-01

articles/load-balancer/load-balancer-multiple-ip-cli.md

@@ -6,7 +6,7 @@ services: virtual-network
 author: mbender-ms
 ms.service: load-balancer
 ms.topic: how-to
-ms.date: 05/30/2023
+ms.date: 06/28/2024
 ms.author: mbender
 ms.custom: template-how-to, devx-track-azurecli
 ---

articles/load-balancer/load-balancer-multiple-ip-powershell.md

@@ -6,7 +6,7 @@ services: load-balancer
 author: mbender-ms
 ms.service: load-balancer
 ms.topic: how-to
-ms.date: 06/27/2023
+ms.date: 06/27/2024
 ms.author: mbender
 ms.custom: template-how-to, devx-track-azurepowershell, engagement-fy23
 ---
@@ -18,7 +18,7 @@ ms.custom: template-how-to, devx-track-azurepowershell, engagement-fy23
 > * [CLI](load-balancer-multiple-ip-cli.md)
 > * [PowerShell](load-balancer-multiple-ip-powershell.md)
 
-This article describes how to use Azure Load Balancer with multiple IP addresses on a secondary network interface (NIC). For this scenario, we have two VMs running Windows, each with a primary and a secondary NIC. Each of the secondary NICs has two IP configurations. Each VM hosts both websites contoso.com and fabrikam.com. Each website is bound to one of the IP configurations on the secondary NIC. We use Azure Load Balancer to expose two frontend IP addresses, one for each website, to distribute traffic to the respective IP configuration for the website. This scenario uses the same port number across both frontends, as well as both backend pool IP addresses.
+This article describes how to use Azure Load Balancer with multiple IP addresses on a secondary network interface (NIC). For this scenario, we have two VMs running Windows, each with a primary and a secondary NIC. Each of the secondary NICs has two IP configurations. Each VM hosts both websites contoso.com and fabrikam.com. Each website is bound to one of the IP configurations on the secondary NIC. We use Azure Load Balancer to expose two frontend IP addresses, one for each website, to distribute traffic to the respective IP configuration for the website. This scenario uses the same port number across both frontends, and both backend pool IP addresses.
 
 ## Steps to load balance on multiple IP configurations
 
@@ -61,9 +61,9 @@ Follow the steps below to achieve the scenario outlined in this article:
     $Subnet1 = Get-AzVirtualNetworkSubnetConfig -Name "mySubnet" -VirtualNetwork $myVnet
     ```
 
-    You do not need to associate the secondary IP configurations with public IPs for the purpose of this tutorial. Edit the command to remove the public IP association part.
+    You don't need to associate the secondary IP configurations with public IPs in this tutorial. Edit the command to remove the public IP association part.
 
-6. Complete steps 4 through 6 of this article again for VM2. Be sure to replace the VM name to VM2 when doing this. Note that you do not need to create a virtual network for the second VM. You may or may not create a new subnet based on your use case.
+6. Complete steps 4 through 6 of this article again for VM2. Be sure to replace the VM name to VM2 when doing this. You don't need to create a virtual network for the second VM. You can create a new subnet based on your use case.
 
 7. Create two public IP addresses and store them in the appropriate variables as shown:
 
@@ -127,7 +127,7 @@ Follow the steps below to achieve the scenario outlined in this article:
     $nic2 | Set-AzNetworkInterface
     ```
 
-13. Finally, you must configure DNS resource records to point to the respective frontend IP address of the Load Balancer. You may host your domains in Azure DNS. For more information about using Azure DNS with Load Balancer, see [Using Azure DNS with other Azure services](../dns/dns-for-azure-services.md).
+13. Finally, you must configure DNS resource records to point to the respective frontend IP address of the Load Balancer. You can host your domains in Azure DNS. For more information about using Azure DNS with Load Balancer, see [Using Azure DNS with other Azure services](../dns/dns-for-azure-services.md).
 
 ## Next steps
 - Learn more about how to combine load balancing services in Azure in [Using load-balancing services in Azure](../traffic-manager/traffic-manager-load-balancing-azure.md).

articles/load-balancer/load-balancer-multiple-ip.md

@@ -6,7 +6,7 @@ author: mbender-ms
 ms.author: mbender
 ms.service: load-balancer
 ms.topic: tutorial
-ms.date: 11/29/2023
+ms.date: 06/28/2024
 ms.custom: template-tutorial, engagement-fy23
 ---
 
@@ -54,7 +54,7 @@ In this section, you create two virtual machines to host the IIS websites.
 
 3. In **Create virtual machine**, enter or select the following information:
 
-    | Setting | Value                                          |
+    | Setting | Value |
     |-----------------------|----------------------------------|
     | **Project Details** |  |
     | Subscription | Select your Azure subscription |
@@ -85,7 +85,7 @@ In this section, you create two virtual machines to host the IIS websites.
     | Subnet | Select **backend-subnet(10.1.0.0/24)** |
     | Public IP | Select **None**. |
     | NIC network security group | Select **Advanced**|
-    | Configure network security group | Select **Create new**. </br> In **Create network security group**, enter **myNSG** in **Name**. </br> In **Inbound rules**, select **+Add an inbound rule**. </br> In **Service**, select **HTTP**. </br> In **Priority**, enter **100**. </br> In **Name**, enter **myNSGrule** </br> Select **Add** </br> Select **OK** |
+    | Configure network security group | Select **Create new**.</br> In **Create network security group**, enter **myNSG** in **Name**.</br> In **Inbound rules**, select **+Add an inbound rule**.</br> In **Service**, select **HTTP**.</br> In **Priority**, enter **100**.</br> In **Name**, enter **myNSGrule**.</br> Select **Add**.</br> Select **OK**. |
 
 6. Select **Review + create**. 
 
@@ -180,7 +180,7 @@ You connect to **myVM1** and **myVM2** with Azure Bastion and configure the seco
 
 6. Select **Allow** for Bastion to use the clipboard.
 
-7. On the server desktop, navigate to Start > Windows Administrative Tools > Windows PowerShell > Windows PowerShell.
+7. On the server desktop, navigate to **Start > Windows Administrative Tools > Windows PowerShell > Windows PowerShell**.
 
 8. In the PowerShell window, execute the `route print` command, which returns output similar to the following output for a virtual machine with two attached network interfaces:
 
@@ -422,14 +422,14 @@ During the creation of the load balancer, you configure:
     | Name | Enter **Frontend-contoso**. |
     | IP version | Select **IPv4**. |
     | IP type | Select **IP address**. |
-    | Public IP address | Select **Create new**. </br> Enter **myPublicIP-contoso** for **Name** </br> Select **Zone-redundant** in **Availability zone**. </br> Leave the default of **Microsoft Network** for **Routing preference**. </br> Select **OK**. |
+    | Public IP address | Select **Create new**.</br> Enter **myPublicIP-contoso** for **Name** </br> Select **Zone-redundant** in **Availability zone**.</br> Leave the default of **Microsoft Network** for **Routing preference**.</br> Select **OK**. |
 
     > [!NOTE]
     > IPv6 isn't currently supported with Routing Preference or Cross-region load-balancing (Global Tier).
     >
     > For more information on IP prefixes, see [Azure Public IP address prefix](../virtual-network/ip-services/public-ip-address-prefix.md).
     >
-    > In regions with [Availability Zones](../availability-zones/az-overview.md?toc=%2fazure%2fvirtual-network%2ftoc.json#availability-zones), you have the option to select no-zone (default option), a specific zone, or zone-redundant. The choice will depend on your specific domain failure requirements. In regions without Availability Zones, this field won't appear. </br> For more information on availability zones, see [Availability zones overview](../availability-zones/az-overview.md).
+    > In regions with [Availability Zones](../availability-zones/az-overview.md?toc=%2fazure%2fvirtual-network%2ftoc.json#availability-zones), you have the option to select no-zone (default option), a specific zone, or zone-redundant. The choice will depend on your specific domain failure requirements. In regions without Availability Zones, this field won't appear.</br> For more information on availability zones, see [Availability zones overview](../availability-zones/az-overview.md).
 
 7. Select **Add**.
 
@@ -442,7 +442,7 @@ During the creation of the load balancer, you configure:
     | Name | Enter **Frontend-fabrikam**. |
     | IP version | Select **IPv4**. |
     | IP type | Select **IP address**. |
-    | Public IP address | Select **Create new**. </br> Enter **myPublicIP-fabrikam** for **Name** </br> Select **Zone-redundant** in **Availability zone**. </br> Leave the default of **Microsoft Network** for **Routing preference**. </br> Select **OK**. |
+    | Public IP address | Select **Create new**.</br> Enter **myPublicIP-fabrikam** for **Name** </br> Select **Zone-redundant** in **Availability zone**.</br> Leave the default of **Microsoft Network** for **Routing preference**.</br> Select **OK**. |
 
 10. Select **Add**.
 
@@ -499,7 +499,7 @@ During the creation of the load balancer, you configure:
     | Protocol | Select **TCP**. |
     | Port | Enter **80**. |
     | Backend port | Enter **80**. |
-    | Health probe | Select **Create new**. </br> In **Name**, enter **myHealthProbe-contoso**. </br> Select **TCP** in **Protocol**. </br> Leave the rest of the defaults, and select **OK**. |
+    | Health probe | Select **Create new**.</br> In **Name**, enter **myHealthProbe-contoso**.</br> Select **TCP** in **Protocol**.</br> Leave the rest of the defaults, and select **OK**. |
     | Session persistence | Select **None**. |
     | Idle timeout (minutes) | Enter or select **15**. |
     | TCP reset | Select **Enabled**. |
@@ -521,7 +521,7 @@ During the creation of the load balancer, you configure:
     | Protocol | Select **TCP**. |
     | Port | Enter **80**. |
     | Backend port | Enter **80**. |
-    | Health probe | Select **Create new**. </br> In **Name**, enter **myHealthProbe-fabrikam**. </br> Select **TCP** in **Protocol**. </br> Leave the rest of the defaults, and select **OK**. |
+    | Health probe | Select **Create new**.</br> In **Name**, enter **myHealthProbe-fabrikam**.</br> Select **TCP** in **Protocol**.</br> Leave the rest of the defaults, and select **OK**. |
     | Session persistence | Select **None**. |
     | Idle timeout (minutes) | Enter or select **15**. |
     | TCP reset | Select **Enabled**. |
@@ -583,4 +583,4 @@ If you're not going to continue to use this application, delete the virtual mach
 Advance to the next article to learn how to create a cross-region load balancer:
 
 > [!div class="nextstepaction"]
-> [Create a cross-region load balancer using the Azure portal](tutorial-cross-region-portal.md)
+> [Create a cross-region load balancer using the Azure portal](tutorial-cross-region-portal.md)

articles/load-balancer/quickstart-load-balancer-standard-internal-portal.md

@@ -6,7 +6,7 @@ services: load-balancer
 author: mbender-ms
 ms.service: load-balancer
 ms.topic: quickstart
-ms.date: 10/19/2023
+ms.date: 06/28/2024
 ms.author: mbender
 ms.custom: mvc, mode-ui, template-quickstart, engagement-fy24
 #Customer intent: I want to create a internal load balancer so that I can load balance internal traffic to VMs.
@@ -97,7 +97,7 @@ During the creation of the load balancer, you configure:
     | Protocol | Select **TCP**. |
     | Port | Enter **80**. |
     | Backend port | Enter **80**. |
-    | Health probe | Select **Create new**. </br> In **Name**, enter **lb-health-probe**. </br> Select **TCP** in **Protocol**. </br> Leave the rest of the defaults, and select **OK**. |
+    | Health probe | Select **Create new**.</br> In **Name**, enter **lb-health-probe**.</br> Select **TCP** in **Protocol**.</br> Leave the rest of the defaults, and select **Save**. |
     | Session persistence | Select **None**. |
     | Idle timeout (minutes) | Enter or select **15**. |
     | Enable TCP reset | Select **checkbox**. |

articles/load-balancer/quickstart-load-balancer-standard-public-portal.md

@@ -1,11 +1,11 @@
 ---
 title: "Quickstart: Create a public load balancer - Azure portal"
 titleSuffix: Azure Load Balancer
-description: This quickstart shows how to create a load balancer using the Azure portal.
+description: Learn how to create a public load balancer using the Azure portal.
 author: mbender-ms
 ms.service: load-balancer
 ms.topic: quickstart
-ms.date: 06/06/2023
+ms.date: 06/28/2024 
 ms.author: mbender
 ms.custom: mvc, mode-ui, template-quickstart, engagement-fy23
 #Customer intent: I want to create a load balancer so that I can load balance internet traffic to VMs.
@@ -81,13 +81,13 @@ During the creation of the load balancer, you configure:
 1. Select **Zone-redundant** in **Availability zone**.
 
     > [!NOTE]
-    > In regions with [Availability Zones](../availability-zones/az-overview.md?toc=%2fazure%2fvirtual-network%2ftoc.json#availability-zones), you have the option to select no-zone (default option), a specific zone, or zone-redundant. The choice will depend on your specific domain failure requirements. In regions without Availability Zones, this field won't appear. </br> For more information on availability zones, see [Availability zones overview](../availability-zones/az-overview.md).
+    > In regions with [Availability Zones](../availability-zones/az-overview.md?toc=%2fazure%2fvirtual-network%2ftoc.json#availability-zones), you have the option to select no-zone (default option), a specific zone, or zone-redundant. The choice will depend on your specific domain failure requirements. In regions without Availability Zones, this field won't appear.</br> For more information on availability zones, see [Availability zones overview](../availability-zones/az-overview.md).
 
 1. Leave the default of **Microsoft Network** for **Routing preference**.
 
-1. Select **OK**.
+1. Select **Save**.
 
-1. Select **Add**.
+1. Select **Save**.
 
 1. Select **Next: Backend pools** at the bottom of the page.
 
@@ -116,7 +116,7 @@ During the creation of the load balancer, you configure:
     | Protocol | Select **TCP** |
     | Port | Enter **80** |
     | Backend port | Enter **80** |
-    | Health probe | Select **Create new**. </br> In **Name**, enter **lb-health-probe**. </br> Select **HTTP** in **Protocol**. </br> Leave the rest of the defaults, and select **Save**. |
+    | Health probe | Select **Create new**.</br> In **Name**, enter **lb-health-probe**.</br> Select **HTTP** in **Protocol**.</br> Leave the rest of the defaults, and select **Save**. |
     | Session persistence | Select **None**. |
     | Idle timeout (minutes) | Enter or select **15** |
     | Enable TCP reset | Select checkbox |

includes/load-balancer-create-bastion.md

@@ -27,10 +27,10 @@ In this section, you create a virtual network with a resource subnet, an Azure B
     |---|---|
     | **Project details** |  |
     | Subscription | Select your subscription. |
-    | Resource group | Select **Create new**. </br> Enter **load-balancer-rg** in Name. </br> Select **OK**. |
+    | Resource group | Select **load-balancer-rg** from the dropdown or **Create new** if it doesn't exist.</br> Enter **load-balancer-rg** in Name.</br> Select **OK**. |
     | **Instance details** |  |
     | Name | Enter **lb-vnet**. |
-    | Region | Select **East US**. |
+    | Region | Select **(US) East US**. |
 
     :::image type="content" source="./media/load-balancer-internal-create-bastion-include/create-virtual-network-basics.png" alt-text="Screenshot of Basics tab of Create virtual network in the Azure portal.":::
 
@@ -42,7 +42,7 @@ In this section, you create a virtual network with a resource subnet, an Azure B
     | **Azure Bastion** |  |
     | Enable Azure Bastion | Select checkbox. |
     | Azure Bastion host name | Enter **lb-bastion**. |
-    | Azure Bastion public IP address | Select **Create new**. </br> Enter **lb-bastion-ip** in Name. </br> Select **OK**. |
+    | Azure Bastion public IP address | Select **Create new**.</br> Enter **lb-bastion-ip** in Name.</br> Select **OK**. |
 
 6. Select the **IP addresses** tab, or **Next** at the bottom of the page.
 7. On **Create virtual network** page, enter or select the following information:
@@ -52,7 +52,8 @@ In this section, you create a virtual network with a resource subnet, an Azure B
     | **Add IPv4 address space** |  |
     | IPv4 address space | Enter **10.0.0.0/16 (65,356 addresses)**. |
     | **Subnets** | Select the **default** subnet link to edit.  |
-    | Subnet template | Leave the default **Default**. |
+    | **Edit subnet** | |
+    | Subnet purpose | Leave the default **Default**. |
     | Name | Enter **backend-subnet**. |
     | Starting address | Enter **10.0.0.0**. |
     | Subnet size | Enter **/24(256 addresses)**. |

includes/load-balancer-nat-gateway.md

@@ -12,7 +12,7 @@
 
 ## Create NAT gateway
 
-In this section, you'll create a NAT gateway for outbound internet access for resources in the virtual network.  For other options for outbound rules, check out [Network Address Translation (SNAT) for outbound connections](/azure/load-balancer/load-balancer-outbound-connections)
+In this section, you create a NAT gateway for outbound internet access for resources in the virtual network. For other options for outbound rules, check out [Network Address Translation (SNAT) for outbound connections](/azure/load-balancer/load-balancer-outbound-connections)
 
 1. Sign in to the [Azure portal](https://portal.azure.com).
 
@@ -26,11 +26,11 @@ In this section, you'll create a NAT gateway for outbound internet access for re
     | ------- | ----- |
     | **Project details** |   |
     | Subscription | Select your subscription. |
-    | Resource group | Select **Create new**. </br> Enter **load-balancer-rg** in Name. </br> Select **OK**. |
+    | Resource group | Select **Create new**.</br> Enter **load-balancer-rg** in Name.</br> Select **OK**. |
     | **Instance details** |    |
     | NAT gateway name | Enter **lb-nat-gateway**. |
     | Region | Select **East US**. |
-    | Availability zone | Select **None**. |
+    | Availability zone | Select **No zone**. |
     | Idle timeout (minutes) | Enter **15**. |
 
     :::image type="content" source="./media/load-balancer-internal-create-bastion-include/create-nat-gateway.png" alt-text="Screenshot of Create network address translation gateway window in the Azure portal.":::