Merge pull request #289077 from ShawnJackson/three-load-balancer-articles

[AQ] edit pass: Three Load Balancer articles

Author: ktoliver

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

@@ -1,7 +1,7 @@
 ---
 title: What is Azure Load Balancer?
 titleSuffix: Azure Load Balancer
-description: Overview of Azure Load Balancer features, architecture, and implementation. Learn how the Load Balancer works and how to use it in the cloud.
+description: Get an overview of Azure Load Balancer features, architecture, and implementation. Learn how the service works and how to use it in the cloud.
 services: load-balancer
 author: mbender-ms
 ms.service: azure-load-balancer
@@ -16,70 +16,73 @@ ms.custom: template-overview, engagement-fy23
 
 *Load balancing* refers to efficiently distributing incoming network traffic across a group of backend servers or resources.
 
-Azure Load Balancer operates at layer 4 of the Open Systems Interconnection (OSI) model. It's the single point of contact for clients. Load balancer distributes inbound flows that arrive at the load balancer's front end to backend pool instances. These flows are according to configured load-balancing rules and health probes. The backend pool instances can be Azure Virtual Machines or instances in a Virtual Machine Scale Set.
+Azure Load Balancer operates at layer 4 of the Open Systems Interconnection (OSI) model. It's the single point of contact for clients. The service distributes inbound flows that arrive at the load balancer's frontend to backend pool instances. These flows are distributed according to configured load-balancing rules and health probes. The backend pool instances can be Azure virtual machines (VMs) or virtual machine scale sets.
 
-A **[public load balancer](./components.md#frontend-ip-configurations)** can provide outbound connections for virtual machines (VMs) inside your virtual network. These connections are accomplished by translating their private IP addresses to public IP addresses. Public Load Balancers are used to load balance internet traffic to your VMs.
+A [public load balancer](./components.md#frontend-ip-configurations) can provide both inbound and outbound connectivity for the VMs inside your virtual network. For inbound traffic scenarios, Azure Load Balancer can load balance internet traffic to your VMs. For outbound traffic scenarios, the service can translate the VMs' private IP addresses to public IP addresses for any outbound connections that originate from your VMs.
 
-An **[internal (or private) load balancer](./components.md#frontend-ip-configurations)** is used in scenarios where private IPs are needed at the frontend only. Internal load balancers are used to load balance traffic inside a virtual network. A load balancer frontend can be accessed from an on-premises network in a hybrid scenario.
+Alternatively, an [internal (or private) load balancer](./components.md#frontend-ip-configurations) can provide inbound connectivity to your VMs in private network connectivity scenarios, such as accessing a load balancer frontend from an on-premises network in a hybrid scenario. Internal load balancers are used to load balance traffic inside a virtual network.
 
-:::image type="content" source="media/load-balancer-overview/load-balancer.png" alt-text="Diagram depicts a load balancer directing traffic.":::
+:::image type="content" source="media/load-balancer-overview/load-balancer.png" alt-text="Diagram that depicts a load balancer directing traffic.":::
 
-For more information on the individual load balancer components, see [Azure Load Balancer components](./components.md).
+For more information on the service's individual components, see [Azure Load Balancer components](./components.md).
 
 ## Why use Azure Load Balancer?
-With Azure Load Balancer, you can scale your applications and create highly available services. 
-Load balancer supports both inbound and outbound scenarios. Load balancer provides low latency and high throughput, and scales up to millions of flows for all TCP and UDP applications.
 
-Key scenarios that you can accomplish using Azure Standard Load Balancer include:
+With Azure Load Balancer, you can scale your applications and create highly available services.
 
-- Load balance **[internal](./quickstart-load-balancer-standard-internal-portal.md)** and **[external](./quickstart-load-balancer-standard-public-portal.md)** traffic to Azure virtual machines.
+The service supports both inbound and outbound scenarios. It provides low latency and high throughput, and it scales up to millions of flows for all TCP and UDP applications.
 
-- Pass-through load balancing which results in ultra-low latency. 
+Key scenarios that you can accomplish by using Azure Standard Load Balancer include:
 
-- Increase availability by distributing resources **[within](./tutorial-load-balancer-standard-public-zonal-portal.md)** and **[across](./quickstart-load-balancer-standard-public-portal.md)** zones.
+- Load balance [internal](./quickstart-load-balancer-standard-internal-portal.md) and [external](./quickstart-load-balancer-standard-public-portal.md) traffic to Azure virtual machines.
 
-- Configure **[outbound connectivity](./load-balancer-outbound-connections.md)** for Azure virtual machines.
+- Use pass-through load balancing, which results in ultralow latency.
 
-- Use **[health probes](./load-balancer-custom-probe-overview.md)** to monitor load-balanced resources.
+- Increase availability by distributing resources [within](./tutorial-load-balancer-standard-public-zonal-portal.md) and [across](./quickstart-load-balancer-standard-public-portal.md) zones.
 
-- Employ **[port forwarding](./tutorial-load-balancer-port-forwarding-portal.md)** to access virtual machines in a virtual network by public IP address and port.
+- Configure [outbound connectivity](./load-balancer-outbound-connections.md) for Azure virtual machines.
 
-- Enable support for **[load-balancing](./virtual-network-ipv4-ipv6-dual-stack-standard-load-balancer-powershell.md)** of **[IPv6](../virtual-network/ip-services/ipv6-overview.md)**.
+- Use [health probes](./load-balancer-custom-probe-overview.md) to monitor load-balanced resources.
 
-- Standard load balancer provides multi-dimensional metrics through [Azure Monitor](/azure/azure-monitor/overview). These metrics can be filtered, grouped, and broken out for a given dimension. They provide current and historic insights into performance and health of your service. [Insights for Azure Load Balancer](./load-balancer-insights.md) offers a preconfigured dashboard with useful visualizations for these metrics. Resource Health is also supported. Review **[Standard load balancer diagnostics](load-balancer-standard-diagnostics.md)** for more details.
+- Employ [port forwarding](./tutorial-load-balancer-port-forwarding-portal.md) to access virtual machines in a virtual network by public IP address and port.
 
-- Load balance services on **[multiple ports, multiple IP addresses, or both](./load-balancer-multivip-overview.md)**.
+- Enable support for [load balancing](./virtual-network-ipv4-ipv6-dual-stack-standard-load-balancer-powershell.md) of [IPv6](../virtual-network/ip-services/ipv6-overview.md).
 
-- Move **[internal](./move-across-regions-internal-load-balancer-portal.md)** and **[external](./move-across-regions-external-load-balancer-portal.md)** load balancer resources across Azure regions.
+- Use multidimensional metrics through [Azure Monitor](/azure/azure-monitor/overview). You can filter, group, and break out these metrics for a particular dimension. They provide current and historic insights into performance and health of your service.
 
-- Load balance TCP and UDP flow on all ports simultaneously using **[HA ports](./load-balancer-ha-ports-overview.md)**.
+  [Insights for Azure Load Balancer](./load-balancer-insights.md) offer a preconfigured dashboard with useful visualizations for these metrics. Resource Health is also supported. For more details, review [Standard load balancer diagnostics](load-balancer-standard-diagnostics.md).
+
+- Load balance services on [multiple ports, multiple IP addresses, or both](./load-balancer-multivip-overview.md).
+
+- Move [internal](./move-across-regions-internal-load-balancer-portal.md) and [external](./move-across-regions-external-load-balancer-portal.md) load balancer resources across Azure regions.
+
+- Load balance TCP and UDP flow on all ports simultaneously by using [high-availability ports](./load-balancer-ha-ports-overview.md).
 
 - Chain Standard Load Balancer and [Gateway Load Balancer](./tutorial-gateway-portal.md).
 
-### <a name="securebydefault"></a>Secure by default
+### <a name="securebydefault"></a>Security by default
 
-* Standard load balancer is built on the zero trust network security model.
+- Standard Load Balancer is built on the Zero Trust network security model.
 
-* Standard Load Balancer is secure by default and part of your virtual network. The virtual network is a private and isolated network. 
+- Standard Load Balancer is part of your virtual network, which is private and isolated for security.
 
-* Standard load balancers and standard public IP addresses are closed to inbound connections unless opened by Network Security Groups. NSGs are used to explicitly permit allowed traffic. If you don't have an NSG on a subnet or NIC of your virtual machine resource, traffic isn't allowed to reach this resource. To learn about NSGs and how to apply them to your scenario, see [Network Security Groups](../virtual-network/network-security-groups-overview.md).
+- Standard load balancers and standard public IP addresses are closed to inbound connections, unless network security groups (NSGs) open them. You use NSGs to explicitly permit allowed traffic. If you don't have an NSG on a subnet or network interface card (NIC) of your virtual machine resource, traffic isn't allowed to reach the resource. To learn about NSGs and how to apply them to your scenario, see [Network security groups](../virtual-network/network-security-groups-overview.md).
 
-* Basic load balancer is open to the internet by default. 
+- Basic Load Balancer is open to the internet by default.
 
-* Load balancer doesn't store customer data.
+- Azure Load Balancer doesn't store customer data.
 
 ## Pricing and SLA
 
-For standard load balancer pricing information, see [Load balancer pricing](https://azure.microsoft.com/pricing/details/load-balancer/).
-Basic load balancer is offered at no charge.
-See [SLA for load balancer](https://aka.ms/lbsla). Basic load balancer has no SLA.
+For Standard Load Balancer pricing information, see [Load Balancer pricing](https://azure.microsoft.com/pricing/details/load-balancer/). For service-level agreements (SLAs), see the [Microsoft licensing information for online services](https://aka.ms/lbsla).
+
+Basic Load Balancer is offered at no charge and has no SLA.
 
 ## What's new?
 
 Subscribe to the RSS feed and view the latest Azure Load Balancer updates on the [Azure Updates](https://azure.microsoft.com/updates/?category=networking&query=load%20balancer) page.
 
-## Next steps
+## Related content
 
-> [!div class="nextstepaction"]
-> [Create a public standard load balancer](quickstart-load-balancer-standard-public-portal.md)
-> [Azure Load Balancer components](./components.md)
+- [Create a public load balancer](quickstart-load-balancer-standard-public-portal.md)
+- [Azure Load Balancer components](./components.md)