reliability updates

Author: mbender-ms

articles/reliability/reliability-load-balancer.md

@@ -11,7 +11,7 @@ ms.date: 10/31/2024
 
 # Reliability in Load Balancer
 
-This article contains detailed information on Load Balancer regional resiliency with [availability zones](#availability-zone-support) and [cross-region disaster recovery and business continuity](#cross-region-disaster-recovery-and-business-continuity). 
+This article contains detailed information on Load Balancer regional resiliency with [availability zones](#availability-zone-support) and [global disaster recovery and business continuity](#global-disaster-recovery-and-business-continuity). 
 
 
 
@@ -29,7 +29,7 @@ Although it's recommended that you deploy Load Balancer with zone-redundancy, a
 
 ### Prerequisites
 
-- To use availability zones with Load Balancer, you need to create your load balancer in a region that supports availability zones.  To see which regions support availability zones, see the [list of supported regions](availability-zones-region-support.md). 
+- To use availability zones with Load Balancer, you need to create your load balancer in a region that supports availability zones. To see which regions support availability zones, see the [list of supported regions](availability-zones-region-support.md). 
 
 - Use Standard SKU for load balancer and Public IP for availability zones support.
 
@@ -63,7 +63,7 @@ Members in the backend pool of a load balancer are normally associated with a si
 ### Zonal load balancer
 
 
-You can choose to have a frontend guaranteed to a single zone, which is known as a *zonal*.  With this scenario,  a single zone in a region serves all inbound or outbound flow.  Your frontend shares fate with the health of the zone.  The data path is unaffected by failures in zones other than where it was guaranteed. You can use zonal frontends to expose an IP address per Availability Zone.  
+You can choose to have a frontend guaranteed to a single zone, which is known as a *zonal*. With this scenario,  a single zone in a region serves all inbound or outbound flow. Your frontend shares fate with the health of the zone. The data path is unaffected by failures in zones other than where it was guaranteed. You can use zonal frontends to expose an IP address per Availability Zone. 
 
 Additionally, the use of zonal frontends directly for load-balanced endpoints within each zone is supported. You can use this configuration to expose per zone load-balanced endpoints to individually monitor each zone. For public endpoints, you can integrate them with a DNS load-balancing product like [Traffic Manager](../traffic-manager/traffic-manager-overview.md) and use a single DNS name.
 
@@ -77,7 +77,7 @@ For an internal load balancer frontend, add a **zones** parameter to the interna
 
 ### Non-zonal load balancer
 
-Load Balancers can also be created in a non-zonal configuration by use of a "no-zone" frontend. In these scenarios, a public load balancer would use a public IP or public IP prefix, an internal load balancer would use a private IP.  This option doesn't give a guarantee of redundancy. 
+Load Balancers can also be created in a non-zonal configuration by use of a "no-zone" frontend. In these scenarios, a public load balancer would use a public IP or public IP prefix, an internal load balancer would use a private IP. This option doesn't give a guarantee of redundancy. 
 
 >[!NOTE]
 >All public IP addresses that are upgraded from Basic SKU to Standard SKU will be of type "no-zone". Learn how to [Upgrade a public IP address in the Azure portal](../virtual-network/ip-services/public-ip-upgrade-portal.md).
@@ -127,11 +127,11 @@ Review [Azure cloud design patterns](/azure/architecture/patterns/) to improve t
 In the case where a region is augmented to have availability zones, any existing IPs would remain non-zonal like IPs used for load balancer frontends. To ensure your architecture can take advantage of the new zones, it's recommended that you create a new frontend IP. Once created, you can replace the existing non-zonal frontend with a new zone-redundant frontend. To learn how to migrate a VM to availability zone support, see [Migrate Load Balancer to availability zone support](./migrate-load-balancer.md).
 
 
-## Cross-region disaster recovery and business continuity
+## Global disaster recovery and business continuity
 
 [!INCLUDE [introduction to disaster recovery](includes/reliability-disaster-recovery-description-include.md)]
 
-Azure Standard Load Balancer supports cross-region load balancing enabling geo-redundant high availability scenarios such as:
+Azure Standard Load Balancer supports global load balancing enabling geo-redundant high availability scenarios such as:
 
 
 * Incoming traffic originating from multiple regions.
@@ -140,25 +140,25 @@ Azure Standard Load Balancer supports cross-region load balancing enabling geo-r
 * Ability to [scale up/down](#ability-to-scale-updown-behind-a-single-endpoint) behind a single endpoint.
 * Static anycast global IP address
 * [Client IP preservation](#client-ip-preservation)
-* [Build on existing load balancer](#build-cross-region-solution-on-existing-azure-load-balancer) solution with no learning curve
+* [Build on existing load balancer](#build-global-solution-on-existing-azure-load-balancer) solution with no learning curve
 
-The frontend IP configuration of your cross-region load balancer is static and advertised across [most Azure regions](#participating-regions).
+The frontend IP configuration of your global load balancer is static and advertised across [most Azure regions](#participating-regions).
 
-:::image type="content" source="../load-balancer/media/cross-region-overview/cross-region-load-balancer.png" alt-text="Diagram of cross-region load balancer." border="true":::
+:::image type="content" source="../load-balancer/media/cross-region-overview/cross-region-load-balancer.png" alt-text="Diagram of global load balancer." border="true":::
 
 > [!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. 
+> The backend port of your load balancing rule on global load balancer should match the frontend port of the load balancing rule/inbound nat rule on regional standard load balancer. 
 
 ### Disaster recovery in multi-region geography
 
 
 #### Regional redundancy
 
-Configure regional redundancy by seamlessly linking a cross-region load balancer to your existing regional load balancers.
+Configure regional redundancy by seamlessly linking a global load balancer to your existing regional load balancers.
 
-If one region fails, the traffic is routed to the next closest healthy regional load balancer.  
+If one region fails, the traffic is routed to the next closest healthy regional load balancer. 
 
-The health probe of the cross-region load balancer gathers information about availability of each regional load balancer every 5 seconds. If one regional load balancer drops its availability to 0, cross-region load balancer detects the failure. The regional load balancer is then taken out of rotation. 
+The health probe of the global load balancer gathers information about availability of each regional load balancer every 5 seconds. If one regional load balancer drops its availability to 0, global load balancer detects the failure. The regional load balancer is then taken out of rotation. 
 
 :::image type="content" source="../load-balancer/media/cross-region-overview/global-region-view.png" alt-text="Diagram of global region traffic view." border="true":::
 
@@ -169,50 +169,50 @@ The geo-proximity load-balancing algorithm is based on the geographic location o
 
 Traffic started from a client hits the closest participating region and travel through the Microsoft global network backbone to arrive at the closest regional deployment. 
 
-For example, you have a cross-region load balancer with standard load balancers in Azure regions:
+For example, you have a global load balancer with standard load balancers in Azure regions:
 
 * West US
 * North Europe
 
 If a flow is started from Seattle, traffic enters West US. This region is the closest participating region from Seattle. The traffic is routed to the closest region load balancer, which is West US.
 
-Azure cross-region load balancer uses geo-proximity load-balancing algorithm for the routing decision. 
+Azure global load balancer uses geo-proximity load-balancing algorithm for the routing decision. 
 
-The configured load distribution mode of the regional load balancers is used for making the final routing decision when multiple regional load balancers are used for geo-proximity.  
+The configured load distribution mode of the regional load balancers is used for making the final routing decision when multiple regional load balancers are used for geo-proximity. 
 
 For more information, see [Configure the distribution mode for Azure Load Balancer](../load-balancer/load-balancer-distribution-mode.md).
 
 Egress traffic follows the routing preference set on the regional load balancers.
 
 ### Ability to scale up/down behind a single endpoint
 
-When you expose the global endpoint of a cross-region load balancer to customers, you can add or remove regional deployments behind the global endpoint without interruption. 
+When you expose the global endpoint of a global load balancer to customers, you can add or remove regional deployments behind the global endpoint without interruption. 
 
 #### Static anycast global IP address
 
-Cross-region load balancer comes with a static public IP, which ensures the IP address remains the same. To learn more about static IP, read more [here](../virtual-network/ip-services/public-ip-addresses.md#ip-address-assignment)
+Global load balancer comes with a static public IP, which ensures the IP address remains the same. To learn more about static IP, read more [here](../virtual-network/ip-services/public-ip-addresses.md#ip-address-assignment)
 
 #### Client IP Preservation
 
-Cross-region load balancer is a Layer-4 pass-through network load balancer. This pass-through preserves the original IP of the packet.  The original IP is available to the code running on the virtual machine. This preservation allows you to apply logic that is specific to an IP address.
+Global load balancer is a Layer-4 pass-through network load balancer. This pass-through preserves the original IP of the packet. The original IP is available to the code running on the virtual machine. This preservation allows you to apply logic that is specific to an IP address.
 
 #### Floating IP
 
 Floating IP can be configured at both the global IP level and regional IP level. For more information, visit [Multiple frontends for Azure Load Balancer](../load-balancer/load-balancer-multivip-overview.md)
 
-It is important to note that floating IP configured on the Azure cross-region Load Balancer operates independently of floating IP configurations on backend regional load balancers. If floating IP is enabled on the cross-region load balancer, the appropriate loopback interface needs to be added to the backend VMs. 
+It's important to note that floating IP configured on the Azure global Load Balancer operates independently of floating IP configurations on backend regional load balancers. If floating IP is enabled on the global load balancer, the appropriate loopback interface needs to be added to the backend VMs. 
 
 #### 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 Global Load Balancer utilizes the health of the backend regional load balancers when deciding where to distribute traffic to. Health checks by global load balancer are done automatically every 5 seconds, given that a user configures health probes on their regional load balancer. 
 
 ## Build cross region solution on existing Azure Load Balancer
 
-The backend pool of cross-region load balancer contains one or more regional load balancers. 
+The backend pool of global load balancer contains one or more regional load balancers. 
 
-Add your existing load balancer deployments to a cross-region load balancer for a highly available, cross-region deployment.
+Add your existing load balancer deployments to a global load balancer for a highly available, global deployment.
 
-**Home region** is where the cross-region load balancer or Public IP Address of Global tier is deployed. 
+**Home region** is where the global load balancer or Public IP Address of Global tier is deployed. 
 This region doesn't affect how the traffic is routed. If a home region goes down, traffic flow is unaffected.
 
 ### Home regions
@@ -227,13 +227,13 @@ This region doesn't affect how the traffic is routed. If a home region goes down
 * West US
 
 > [!NOTE]
-> You can only deploy your cross-region load balancer or Public IP in Global tier in one of the listed Home regions.
+> You can only deploy your global load balancer or Public IP in Global tier in one of the listed Home regions.
 
-A **participating region** is where the Global public IP of the load balancer is being advertised.
+A **participating region** is where the global public IP of the load balancer is being advertised.
 
 Traffic started by the user travels to the closest participating region through the Microsoft core network. 
 
-Cross-region load balancer routes the traffic to the appropriate regional load balancer.
+Global load balancer routes the traffic to the appropriate regional load balancer.
 
 :::image type="content" source="../load-balancer/media/cross-region-overview/multiple-region-global-traffic.png" alt-text="Diagram of multiple region global traffic.":::
 
@@ -262,27 +262,27 @@ Cross-region load balancer routes the traffic to the appropriate regional load b
 * West US 2 
 
 > [!NOTE]
-> The backend regional load balancers can be deployed in any publicly available Azure Region and is not limited to just participating regions.
+> The backend regional load balancers can be deployed in any publicly available Azure Region and isn't limited to just participating regions.
 
 ## Limitations
 
-* Cross-region frontend IP configurations are public only. An internal frontend is currently not supported.
+* Global frontend IP configurations are public only. An internal frontend is currently not supported.
 
-* Private or internal load balancer can't be added to the backend pool of a cross-region load balancer 
+* Private or internal load balancer can't be added to the backend pool of a global load balancer 
 
 * NAT64 translation isn't supported at this time. The frontend and backend IPs must be of the same type (v4 or v6).
 
-* UDP traffic isn't supported on Cross-region Load Balancer for IPv6.
+* UDP traffic isn't supported on a global Load Balancer for IPv6.
 
-* UDP traffic on port 3 isn't supported on Cross-Region Load Balancer
+* UDP traffic on port 3 isn't supported on a global Load Balancer
 
-* Outbound rules aren't supported on Cross-region Load Balancer. For outbound connections, utilize [outbound rules](../load-balancer/outbound-rules.md) on the regional load balancer or [NAT gateway](../nat-gateway/nat-overview.md).
+* Outbound rules aren't supported on a global Load Balancer. For outbound connections, utilize [outbound rules](../load-balancer/outbound-rules.md) on the regional load balancer or [NAT gateway](../nat-gateway/nat-overview.md).
 
 ## Pricing and SLA
-Cross-region load balancer shares the [SLA](https://azure.microsoft.com/support/legal/sla/load-balancer/v1_0/) of standard load balancer.
+Global load balancer shares the [SLA](https://azure.microsoft.com/support/legal/sla/load-balancer/v1_0/) of standard load balancer.
 
 ## Next steps
 - [Reliability in Azure](/azure/reliability/availability-zones-overview)
-- See [Tutorial: Create a cross-region load balancer using the Azure portal](../load-balancer/tutorial-cross-region-portal.md) to create a cross-region load balancer.
-- Learn more about [cross-region load balancer](https://www.youtube.com/watch?v=3awUwUIv950).
+- See [Tutorial: Create a global load balancer using the Azure portal](../load-balancer/tutorial-cross-region-portal.md) to create a global load balancer.
+- Learn more about [global load balancer](https://www.youtube.com/watch?v=3awUwUIv950) in this video.
 - Learn more about [Azure Load Balancer](../load-balancer/load-balancer-overview.md).