Merge pull request #54099 from staleycyn/patch-3

Content drift fixes for the Load Balance HTTPS traffic module

Author: JamesJBarnett

learn-pr/wwl-azure/load-balancing-https-traffic-azure/includes/2-design-azure-application-gateway.md

@@ -1,15 +1,23 @@
 
 
 
-The [Azure Application Gateway](/azure/application-gateway/overview) processes network traffic to web apps hosted on a pool of web servers. The processing performed by Azure Application Gateway includes load balancing HTTP traffic and inspecting traffic using a web application firewall. This type of routing is known as application layer (OSI layer 7) load balancing. Azure Application Gateway includes the following features:
+The [Azure Application Gateway](/azure/application-gateway/overview) processes network traffic to web apps hosted on a pool of web servers. The processing performed by Azure Application Gateway includes load balancing HTTP traffic and inspecting traffic using a web application firewall. This type of routing is known as application layer (OSI layer 7) load balancing. A
+
+Azure Application Gateway v2 includes the following features.  
 
 - Support for the HTTP, HTTPS, HTTP/2, and WebSocket protocols.
 - A web application firewall (WAF) to protect against web application vulnerabilities.
-- End-to-end request encryption.
+- SSL/TLS termination at the gateway, offloading encryption overhead from backend servers.
+- End-to-end TLS encryption for compliance scenarios requiring encryption to the backend.
 - Autoscaling to dynamically adjust capacity as your web traffic load change.
 - Connection draining allowing graceful removal of backend pool members during planned service updates.
 - Session stickiness to ensure client requests in the same session are routed to the same backend server. 
-- Path and URL based routing. 
+- Path and URL based routing.
+- Zone redundancy, Azure key vault integration, and HTTP header rewrite.
+
+> [!Note]
+> Support for Application Gateway V1 ends on April 28, 2026.
+
 
 ## How Azure Application Gateway works
 
@@ -24,4 +32,4 @@ Let's review the [Azure Application Gateway components](/azure/application-gatew
 - **Health probes**. Health probes determine which servers are available for load-balancing in a backend pool. Servers are automatically added and removed from the backend pool based on their availability. 
 
 > [!TIP]
-> Learn more about Azure Application Gateway check out the [Introduction to Azure Application Gateway](/training/modules/intro-to-azure-application-gateway/) module.
+> Learn more about Azure Application Gateway check out the [Introduction to Azure Application Gateway](/training/modules/intro-to-azure-application-gateway/) module.

learn-pr/wwl-azure/load-balancing-https-traffic-azure/includes/5-design-configure-azure-front-door.md

@@ -1,26 +1,26 @@
-
-
-
-
 [Azure Front Door](/azure/frontdoor/front-door-overview) is Microsoft’s modern cloud Content Delivery Network (CDN) that provides fast, reliable, and secure access between your users and your applications. Azure Front Door delivers your content using the Microsoft’s global edge network with hundreds of global and local POPs distributed around the world close to both your enterprise and consumer end users.
 
+
 ## Azure Front Door tiers
 
-Azure Front Door provides both content delivery and security features. **Azure Front Door Standard** is content-delivery optimized.
+> [!Note]
+> Azure Front Door has three tiers: Standard, Premium, and Classic. This module focuses on Standard and Premium. New resources will not be supported on Azure Front Door Classic after August 2025. 
+
+**Azure Front Door Standard** provides both content delivery and security features. 
 
 - Provide for both static and dynamic content acceleration.
 - Support global load balancing.
 - Implement SSL offload.
 - Implement domain and certificate management.
 - Benefit from enhanced traffic analytics.
-- Benefit from basic security capabilities.
+- Custom WAF rules for basic protection against known attack patterns.
 
-**Azure Front Door Premium** is security optimized.
+**Azure Front Door Premium** is security optimized and provides other features. 
 
-- Extensive security capabilities across Web Application Firewall.
 - BOT protection.
 - Private Link support.
 - Integration with Microsoft Threat Intelligence and security analytics.
+- Microsoft-managed WAF rule sets that autoupdate against OWASP top-10 and emerging threats.
 
 ## Azure Front Door usage cases
 
@@ -37,9 +37,6 @@ This diagram shows a user request processed by Azure Front Door.
 
 ## Other things to know
 
-- **Routing algorithm**. The Azure Front Door routing algorithm first matches based on HTTP protocol, then frontend host, then the Path.
-    -  HTTP Protocols (HTTP/HTTPS)
-    -  Hosts (for example, www.foo.com, \*.bar.com)
-    -  Paths (for example, /*, /users/*, /file.gif)
+- **Routing algorithm**. The Azure Front Door routing algorithm first matches based on HTTP protocol, then frontend host, and then Path. The Standard and Premium tiers also support a Rules Engine that uses regular expressions and server variables for complex routing conditions.
 - **Response codes**. Azure Front Door response codes help clients understand the purpose of the redirect. You can set the protocol used for redirection. The most common use case of the redirect feature is to set HTTP to HTTPS redirection.
 - **Health probes**. Front Door periodically sends a synthetic HTTP/HTTPS request to each of your configured backends. Front Door then uses these responses from the probe to determine the "best" backend resources to route your client requests.

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

@@ -5,7 +5,7 @@ metadata:
   prefetch-feature-rollout: true
   title: Load balance HTTP(S) traffic in Azure
   description: "You learn how to design load balancer solutions for HTTP(S) traffic and how to implement Azure Application gateway and Azure Front Door."
-  ms.date: 02/19/2026
+  ms.date: 03/23/2026
   author: wwlpublish
   ms.author: cynthist
   ms.topic: module