Merge pull request #278565 from mbender-ms/lb-image-updates-265739

load balancer - updated images and acrolinx

Author: rmca14

articles/load-balancer/components.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/18/2024
 ms.author: mbender
 ms.custom: template-concept, engagement-fy23
 ---
@@ -81,9 +81,7 @@ The load-balancing decision is made per flow. This action is based on the follow
 
 The HA ports load-balancing rules help you with critical scenarios, such as high availability and scale for network virtual appliances (NVAs) inside virtual networks. The feature can help when a large number of ports must be load-balanced.
 
-<p align="center">
-  <img src="./media/load-balancer-components/harules.svg" alt="Figure depicts how Azure Load Balancer directs all frontend ports to three instances of all backend ports" width="512" title="HA Ports rules">
-</p>
+:::image type="content" source="media/load-balancer-components/harules.png" alt-text="Diagram of Azure Load Balancer directing all frontend ports to three instances of all backend ports":::
 
 *Figure: HA Ports rules*
 
@@ -121,16 +119,7 @@ Basic load balancer doesn't support outbound rules.
 - Forwarding IP fragments isn't supported on load-balancing rules. IP fragmentation of UDP and TCP packets isn't supported on load-balancing rules. 
 - You can only have one Public Load Balancer (NIC based) and one internal Load Balancer (NIC based) per availability set. However, this constraint doesn't apply to IP-based load balancers.  
 
-## Next steps
-
-- See [Create a public Standard load balancer](quickstart-load-balancer-standard-public-portal.md) to get started with using a Load Balancer.
-- Learn more about [Azure Load Balancer](load-balancer-overview.md).
-- Learn about [Public IP Address](../virtual-network/ip-services/virtual-network-public-ip-address.md)
-- Learn about [Private IP Address](../virtual-network/ip-services/private-ip-addresses.md)
-- Learn about using [Standard load balancer and Availability Zones](load-balancer-standard-availability-zones.md).
-- Learn about [Standard load balancer Diagnostics](load-balancer-standard-diagnostics.md).
-- Learn about [TCP Reset on Idle](load-balancer-tcp-reset.md).
-- Learn about [Standard load balancer with HA Ports load balancing rules](load-balancer-ha-ports-overview.md).
-- Learn more about [Network Security Groups](../virtual-network/network-security-groups-overview.md).
-- Learn more about [Load balancer limits](../azure-resource-manager/management/azure-subscription-service-limits.md#load-balancer).
-- Learn about using [Port forwarding](./tutorial-load-balancer-port-forwarding-portal.md).
+## Next step
+
+> [!div class="nextstepaction"]
+> [Create a public Standard load balancer](quickstart-load-balancer-standard-public-portal.md)

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

@@ -6,7 +6,7 @@ services: load-balancer
 author: mbender-ms
 ms.service: load-balancer
 ms.topic: overview
-ms.date: 09/15/2023
+ms.date: 06/18/2024
 ms.author: mbender
 ms.custom: template-overview, engagement-fy23
 # Customer intent: As an IT administrator, I want to learn more about the Azure Load Balancer service and what I can use it for.
@@ -20,7 +20,7 @@ Azure Load Balancer operates at layer 4 of the Open Systems Interconnection (OSI
 
 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.
 
-An **[internal (or private) load balancer](./components.md#frontend-ip-configurations)** is used 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.
+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.
 
 :::image type="content" source="media/load-balancer-overview/load-balancer.png" alt-text="Diagram depicts public and internal load balancers directing traffic to web and business tiers.":::
 
@@ -36,7 +36,7 @@ Key scenarios that you can accomplish using Azure Standard Load Balancer include
 
 - Load balance **[internal](./quickstart-load-balancer-standard-internal-portal.md)** and **[external](./quickstart-load-balancer-standard-public-portal.md)** traffic to Azure virtual machines.
 
-- Pass-through load balancing which results in ultra-low latency. 
+- Pass-through load balancing, which results in ultra-low latency. 
 
 - Increase availability by distributing resources **[within](./tutorial-load-balancer-standard-public-zonal-portal.md)** and **[across](./quickstart-load-balancer-standard-public-portal.md)** zones.
 
@@ -48,7 +48,7 @@ Key scenarios that you can accomplish using Azure Standard Load Balancer include
 
 - 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)**.
 
-- Standard load balancer provides multi-dimensional metrics through [Azure Monitor](../azure-monitor/overview.md).  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.
+- Standard load balancer provides multi-dimensional metrics through [Azure Monitor](../azure-monitor/overview.md). 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.
 
 - Load balance services on **[multiple ports, multiple IP addresses, or both](./load-balancer-multivip-overview.md)**.
 
@@ -62,9 +62,9 @@ Key scenarios that you can accomplish using Azure Standard Load Balancer include
 
 * 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 secure by default and part of your virtual network. The virtual network is a private and isolated network. 
 
-* 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 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).
 
 * Basic load balancer is open to the internet by default. 
 
@@ -78,12 +78,10 @@ See [SLA for load balancer](https://aka.ms/lbsla). Basic load balancer has no SL
 
 ## What's new?
 
-Subscribe to the RSS feed and view the latest Azure Load Balancer feature updates on the [Azure Updates](https://azure.microsoft.com/updates/?category=networking&query=load%20balancer) page.
+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
 
-* See [Create a public standard load balancer](quickstart-load-balancer-standard-public-portal.md) to get started with using a load balancer.
-
-* For more information on Azure Load Balancer limitations and components, see [Azure Load Balancer components](./components.md) and [Azure Load Balancer concepts](./concepts.md)
-
-* [Learn module: Introduction to Azure Load Balancer](/training/paths/intro-to-azure-application-delivery-services).
+> [!div class="nextstepaction"]
+> [Create a public standard load balancer](quickstart-load-balancer-standard-public-portal.md)
+> [Azure Load Balancer components](./components.md)