Added updates for retirement and fixed links

Author: mbender-ms

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

@@ -6,7 +6,7 @@ services: load-balancer
 author: mbender-ms
 ms.service: azure-load-balancer
 ms.topic: overview
-ms.date: 06/18/2024
+ms.date: 02/19/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.
@@ -27,10 +27,10 @@ Alternatively, an [internal (or private) load balancer](./components.md#frontend
 
 :::image type="content" source="media/load-balancer-overview/load-balancer.png" alt-text="Diagram that depicts a load balancer directing traffic.":::
 
-Azure Load Balancer has three stock-keeping units (SKUs) - Basic, Standard, and Gateway. Each SKU is catered towards a specific scenario and has differences in scale, features, and pricing.
-
 For more information on the service's individual components, see [Azure Load Balancer components](./components.md).
 
+Azure Load Balancer has three stock-keeping units (SKUs) - Basic, Standard, and Gateway. Each SKU is catered towards a specific scenario and has differences in scale, features, and pricing. For more information, see [Azure Load Balancer SKUs](skus.md).
+
 ## Why use Azure Load Balancer?
 
 With Azure Load Balancer, you can scale your applications and create highly available services.
@@ -67,21 +67,21 @@ Key scenarios that you can accomplish by using Azure Standard Load Balancer incl
 
 ### <a name="securebydefault"></a>Security by default
 
-- [Standard Load Balancer](https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/skus.md) is built on the Zero Trust network security model.
+- Standard Load Balancer is built on the Zero Trust network security model.
 
-- [Standard Load Balancer](https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/skus.md) is part of your virtual network, which is private and isolated for security.
+- 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 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](https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/skus.md) is open to the internet by default.
+- Basic Load Balancer is open to the internet by default.
 
 - Azure Load Balancer doesn't store customer data.
 
 ## Pricing and SLA
 
 For [Standard Load Balancer](https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/skus.md) 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.
+Basic Load Balancer is offered at no charge and has no SLA. Also, it will be retired on September 30, 2025.
 
 ## What's new?