Merge pull request #54113 from staleycyn/patch-3

Content drift fixes on the non-HTTPS load balancing module

Author: v-dirichards

learn-pr/wwl-azure/load-balancing-non-https-traffic-azure/includes/3-design-implement-azure-load-balancer-using-azure-portal.md

@@ -1,6 +1,6 @@
 
 
-**Azure Load Balancer** operates at layer 4 of the Open Systems Interconnection (OSI) model. It's the single point of contact for clients. Azure 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**](/azure/load-balancer/load-balancer-overview) operates at layer 4 of the Open Systems Interconnection (OSI) model. It's the single point of contact for clients. Azure 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.
 
 This video reviews how to select a load balancer type.  
 
@@ -43,22 +43,20 @@ Load Balancers can also use a "no-zone" frontend. In these scenarios, a public l
 
 ## Selecting an Azure load balancer SKU
 
-There are several [load balancer SKUs](/azure/load-balancer/skus): Basic, Standard, and Gateway. These SKUs differ in terms of their scenario scope and scale, features, and cost. The [Gateway Load Balancer SKU](/azure/load-balancer/gateway-overview) is for high performance and high availability scenarios with Network Virtual Appliances (NVAs). This table compares the Standard and Basic Load Balancer.
+There are two [load balancer SKUs](/azure/load-balancer/skus): Standard, and Gateway. These SKUs differ in terms of their scenario scope and scale, features, and cost. 
 
 > [!IMPORTANT]
-> On September 30, 2025, Basic Load Balancer will be retired. 
+> On September 30, 2025, the Basic Load Balancer was retired. The Basic Load Balancer is no longer available for new deployments. Existing Basic Load Balancer resources should be [upgraded to Standard Load Balancer](/azure/load-balancer/load-balancer-basic-upgrade-guidance). 
 
-| **Features** | **Standard Load Balancer** | **Basic Load Balancer** |
+| **Features** | **Standard Load Balancer** | **Gateway Load Balancer** |
 | --- | ---  | ---|
-| Backend pool size | Supports up to 1,000 instances. | Supports up to 300 instances. |
-|  Backend pool endpoints |Any virtual machines or virtual machine scale sets in a single virtual network. | Virtual machines in a single availability set or virtual machine scale set. |
-| Health probes | TCP, HTTP, HTTPS | TCP, HTTP |
-| Health probe down behavior | TCP connections stay alive on an instance probe down and on all probes down. | TCP connections stay alive on an instance probe down. All TCP connections end when all probes are down. |
-| Availability Zones | Zone-redundant and zonal frontends for inbound and outbound traffic. | Not available. |
-| Diagnostics | Azure Monitor multi-dimensional metrics. | [Azure Monitor logs](/azure/load-balancer/load-balancer-monitor-log) |
-| Secure by default | Closed to inbound flows unless allowed by a network security group. Internal traffic from the virtual network to the internal load balancer is allowed.  | Open by default. Network security group optional. |
-| Multiple front ends | Inbound and outbound | Inbound only |
+| Primary use case | General-purpose load balancing for web applications and services | High performance and high availability scenarios with Network Virtual Appliances (NVAs) |
+| Backend pool size | Supports up to 1,000 instances | Supports up to 1,000 instances |
+| Backend pool endpoints | Any virtual machines or virtual machine scale sets in a single virtual network. | Network Virtual Appliances (NVAs) in a single virtual network  |
+| Traffic inspection | No built-in traffic inspection | Enables transparent traffic inspection and filtering through NVAs |
+| Cross-region connectivity | Regional load balancing | Regional load balancing with NVA integration |
+
 
 
 > [!TIP]
-> Learn more about the Load Balancer check out the [Introduction to Azure Load Balancer](/training/modules/intro-to-azure-load-balancer/) module.
+> Learn more about the Load Balancer check out the [Introduction to Azure Load Balancer](/training/modules/intro-to-azure-load-balancer/) module.

learn-pr/wwl-azure/load-balancing-non-https-traffic-azure/includes/5-explore-azure-traffic-manager.md

@@ -1,5 +1,5 @@
 
-[Azure Traffic Manager](/azure/traffic-manager/traffic-manager-overview) is a DNS-based traffic load balancer. This service allows you to distribute traffic to your public facing applications across the global Azure regions. Traffic Manager also provides your public endpoints with high availability and quick responsiveness. The most important point to understand is that Traffic Manager works at the DNS level which is at the Application layer (Layer-7).
+[Azure Traffic Manager](/azure/traffic-manager/traffic-manager-overview) is a DNS-based traffic load balancer. This service allows you to distribute traffic to your public facing applications across the global Azure regions. Traffic Manager also provides your public endpoints with high availability and quick responsiveness. The most important point to understand is that Traffic Manager works at the DNS level, which is at the Application layer (Layer-7).
 
 This video reviews Traffic Manager features and how the service works. 
 
@@ -51,3 +51,6 @@ Use the [**Performance** routing method](/azure/traffic-manager/traffic-manager-
 Use the [**Geographic** routing method](/azure/traffic-manager/traffic-manager-routing-methods#geographic-traffic-routing-method) to direct users to specific endpoints based on where their DNS queries originate from geographically. Good choice for regional compliance requirements. 
 
 :::image type="content" source="../media/routing-method-geographic-c04c1141.png" alt-text="Diagram that shows the 'Geographic' routing method.":::
+
+> [!Note]
+> The are two other routing methods: Multivalue and Subnet. Use the [**Multivalue** routing method](/azure/traffic-manager/traffic-manager-routing-methods#multivalue-traffic-routing-method) when you want to return multiple healthy endpoints in a single DNS query response. Use the [**Subnet** routing method](/azure/traffic-manager/traffic-manager-routing-methods#subnet-traffic-routing-method) when you want to map user IP address ranges to specific endpoints. 

learn-pr/wwl-azure/load-balancing-non-https-traffic-azure/includes/7-summary.md

@@ -5,9 +5,9 @@ In this module, you learned about the Azure Load Balancer and Azure Traffic Mana
 - Azure offers two non-HTTP(S) load balancing solutions: Azure Load Balancer and Azure Traffic Manager.
 - Azure Load Balancers can distribute workloads globally or regionally.
 - Azure Load Balancers can be public (external) or internal (private).
-- Azure Load Balancer has two SKUs: Basic and Standard.
+- Azure Load Balancer has two SKUs: Standard and Gateway.
 - Azure Traffic Manager is a DNS-based network traffic load balancer.
-- Azure Traffic Manager supports different traffic-routing methods. These methods include performance, weighted, priority, and geographic. 
+- Azure Traffic Manager supports different traffic-routing methods. These methods include performance, weighted, priority, geographic, multivalue, and subnet. 
 
 ### Learn more with Copilot
 

learn-pr/wwl-azure/load-balancing-non-https-traffic-azure/index.yml

@@ -5,15 +5,15 @@ metadata:
   prefetch-feature-rollout: true
   title: Load balance non-HTTP(S) traffic in Azure
   description: "You learn the different load balancer options in Azure and how to choose and implement the right Azure solution for non-HTTP(S) traffic."
-  ms.date: 02/19/2026
+  ms.date: 03/23/2026
   author: wwlpublish
   ms.author: cynthist
   ms.topic: module
   ms.collection: N/A
   ms.custom:
   - references_regions
   ms.service: azure-load-balancer
-  ai-usage: human-only
+  ai-usage: ai-assisted
 title: Load balance non-HTTP(S) traffic in Azure
 summary: You learn the different load balancer options in Azure and how to choose and implement the right Azure solution for non-HTTP(S) traffic.
 abstract: |