Merge pull request #279375 from mbender-ms/lb-freshness-June-2024

prmerger-automator[bot] · web-flow · commit b01ab3ef5be4 · 2024-06-26T19:41:22.000Z
load balancer - June Freshness - part I
diff --git a/articles/load-balancer/backend-pool-management.md b/articles/load-balancer/backend-pool-management.md
@@ -6,22 +6,22 @@ services: load-balancer
 author: mbender-ms
 ms.service: load-balancer
 ms.topic: how-to
-ms.date: 02/03/2023
+ms.date: 06/26/2024
 ms.author: mbender 
 ms.custom: template-how-to, devx-track-azurepowershell, devx-track-azurecli, engagement-fy23
 ---
 
 # Backend pool management
 
-The backend pool is a critical component of the load balancer. The backend pool defines the group of resources that will serve traffic for a given load-balancing rule.
+The backend pool is a critical component of the load balancer. The backend pool defines the group of resources that serve traffic for a given load-balancing rule.
 
 There are two ways of configuring a backend pool:
 
 * Network Interface Card (NIC)
 
 * IP address
 
-To preallocate a backend pool with an IP address range that later will contain virtual machines and Virtual Machine Scale Sets, configure the pool by IP address and virtual network ID.
+To preallocate a backend pool with an IP address range that will contain virtual machines and Virtual Machine Scale Sets, configure the pool by IP address and virtual network ID.
 This article focuses on configuration of backend pools by IP addresses.
 
 ## Configure backend pool by IP address and virtual network
@@ -218,7 +218,7 @@ az vm create \
   * The backend resources must be in the same virtual network as the load balancer for IP based LBs
   * A load balancer with IP based Backend Pool can’t function as a Private Link service
   * [Private endpoint resources](../private-link/private-endpoint-overview.md) can't be placed in an IP based backend pool
-  * ACI containers aren't currently supported by IP based LBs
+  * IP-based load balancers don't support ACI containers
   * Load balancers or services such as Application Gateway can’t be placed in the backend pool of the load balancer
   * Inbound NAT Rules can’t be specified by IP address
   * You can configure IP based and NIC based backend pools for the same load balancer. You can’t create a single backend pool that mixes backed addresses targeted by NIC and IP addresses within the same pool.
diff --git a/articles/load-balancer/concepts.md b/articles/load-balancer/concepts.md
@@ -5,7 +5,7 @@ services: load-balancer
 author: mbender-ms
 ms.service: load-balancer
 ms.topic: conceptual
-ms.date: 05/08/2023
+ms.date: 06/26/2024
 ms.author: mbender
 ms.custom: template-concept
 ---
diff --git a/articles/load-balancer/cross-region-overview.md b/articles/load-balancer/cross-region-overview.md
@@ -6,7 +6,7 @@ services: load-balancer
 author: mbender-ms
 ms.service: load-balancer
 ms.topic: conceptual
-ms.date: 06/23/2023
+ms.date: 06/26/2024
 ms.author: mbender
 ms.custom: template-concept, references_regions
 ---
@@ -29,6 +29,7 @@ The frontend IP configuration of your cross-region load balancer is static and a
 
 > [!NOTE]
 > The backend port of your load balancing rule on cross-region load balancer should match the frontend port of the load balancing rule/inbound nat rule on regional standard load balancer. 
+
 ### Regional redundancy
 
 Configure regional redundancy by seamlessly linking a cross-region load balancer to your existing regional load balancers. 
@@ -82,7 +83,7 @@ It's important to note that floating IP configured on the Azure cross-region Loa
 
 ### Health Probes
 
-Azure cross-region Load Balancer utilizes the health of the backend regional load balancers when deciding where to distribute traffic to. Health checks by cross-region load balancer are done automatically every 5 seconds, given that a user has set up health probes on their regional load balancer.  
+Azure cross-region Load Balancer utilizes the health of the backend regional load balancers when deciding where to distribute traffic to. Health checks by cross-region load balancer are done automatically every 5 seconds, given that health probes are set up on their regional load balancer.  
 
 ## Build cross region solution on existing Azure Load Balancer
 
@@ -118,6 +119,7 @@ Cross-region load balancer routes the traffic to the appropriate regional load b
 :::image type="content" source="./media/cross-region-overview/multiple-region-global-traffic.png" alt-text="Diagram of multiple region global traffic.":::
 
 #### Participating regions in Azure
+
 * Australia East 
 * Australia Southeast 
 * Central India 
diff --git a/articles/load-balancer/distribution-mode-concepts.md b/articles/load-balancer/distribution-mode-concepts.md
@@ -5,7 +5,7 @@ author: mbender-ms
 ms.author: mbender
 ms.service: load-balancer
 ms.topic: conceptual 
-ms.date: 05/30/2023
+ms.date: 06/26/2024
 ms.custom: template-concept 
 #Customer intent: As a administrator, I want to learn about the different distribution modes of Azure Load Balancer so that I can configure the distribution mode for my application.
 ---
@@ -35,7 +35,7 @@ The five-tuple consists of:
 * **Protocol type**
 
 The hash is used to route traffic to healthy backend instances within the backend pool. The algorithm provides stickiness only within a transport session. When the client starts a new session from the same source IP, the source port changes and causes the traffic to go to a different backend instance.
-In order to configure hash based distribution, you must select session persistence to be **None** in the Azure portal. This specifies that successive requests from the same client may be handled by any virtual machine.
+In order to configure hash based distribution, you must select session persistence to be **None** in the Azure portal. This specifies that successive requests from the same client can be handled by any virtual machine.
 
 ![Hash-based distribution](./media/load-balancer-overview/load-balancer-distribution.png)
 
diff --git a/articles/load-balancer/gateway-overview.md b/articles/load-balancer/gateway-overview.md
@@ -5,7 +5,7 @@ description: Overview of gateway load balancer SKU for Azure Load Balancer.
 ms.service: load-balancer
 author: mbender-ms
 ms.author: mbender
-ms.date: 04/20/2023
+ms.date: 06/26/2024
 ms.topic: conceptual
 ms.custom: template-concept, engagement-fy23
 ---
diff --git a/articles/load-balancer/gateway-partners.md b/articles/load-balancer/gateway-partners.md
@@ -4,7 +4,7 @@ description: Learn about partners offering their network appliances for use with
 author: mbender-ms
 ms.service: load-balancer
 ms.topic: conceptual
-ms.date: 05/22/2023
+ms.date: 06/26/2024
 ms.author: mbender
 ms.custom: template-concept
 ---
diff --git a/articles/load-balancer/inbound-nat-rules.md b/articles/load-balancer/inbound-nat-rules.md
@@ -5,7 +5,7 @@ description: Overview of what is inbound NAT rule, why to use inbound NAT rule,
 author: mbender-ms
 ms.service: load-balancer
 ms.topic: conceptual
-ms.date: 05/03/2023
+ms.date: 06/26/2024
 ms.author: mbender
 ms.custom: template-concept, engagement-fy23
 #Customer intent: As a administrator, I want to create an inbound NAT rule so that I can forward a port to a virtual machine in the backend pool of an Azure Load Balancer.
@@ -17,7 +17,7 @@ An inbound NAT rule is used to forward traffic from a load balancer frontend to
 
 ## Why use an inbound NAT rule?
 
-An inbound NAT rule is used for port forwarding. Port forwarding lets you connect to virtual machines by using the load balancer frontend IP address and port number. The load balancer receives the traffic on a port, and based on the inbound NAT rule, forwards the traffic to a designated virtual machine on a specific backend port. Note, unlike load balancing rules, inbound NAT rules do not need a health probe attached to it. 
+An inbound NAT rule is used for port forwarding. Port forwarding lets you connect to virtual machines by using the load balancer frontend IP address and port number. The load balancer receives the traffic on a port, and based on the inbound NAT rule, forwards the traffic to a designated virtual machine on a specific backend port. Note, unlike load balancing rules, inbound NAT rules don't need a health probe attached to it. 
 
 ## Types of inbound NAT rules
 
diff --git a/articles/load-balancer/instance-metadata-service-load-balancer.md b/articles/load-balancer/instance-metadata-service-load-balancer.md
@@ -6,7 +6,7 @@ services: load-balancer
 author: mbender-ms
 ms.service: load-balancer
 ms.topic: conceptual
-ms.date: 05/04/2023
+ms.date: 06/26/2024
 ms.author: mbender
 ms.custom: template-concept, engagement-fy23
 ---
diff --git a/articles/load-balancer/ipv6-dual-stack-standard-internal-load-balancer-powershell.md b/articles/load-balancer/ipv6-dual-stack-standard-internal-load-balancer-powershell.md
@@ -1,13 +1,11 @@
 ---
 title:  Deploy an IPv6 dual stack application using Standard Internal Load Balancer in Azure - PowerShell
-titlesuffix: Azure Virtual Network
 description: This article shows how to deploy an IPv6 dual stack application with Standard Internal Load Balancer in Azure virtual network using Azure PowerShell.
 services: virtual-network
 author: mbender-ms
-manager: mtillman
 ms.service: virtual-network
 ms.topic: how-to
-ms.date: 06/27/2023
+ms.date: 06/27/2024
 ms.author: mbender
 ms.custom: devx-track-azurepowershell, template-how-to, engagement-fy23
 ---
