Merge pull request #49199 from wwlpublish/227f6f11a4aea31305b6ba9b9824eaf69d95bd127f770e94c0c3fcadee243655-live

 Modules/M04-load-balancing-non-https-traffic-azure

Author: JamesJBarnett

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

@@ -6,12 +6,12 @@ metadata:
   prefetch-feature-rollout: true
   title: Introduction
   description: "Introduction"
-  ms.date: 10/07/2024
+  ms.date: 02/13/2025
   author: wwlpublish
-  ms.author: jileary
+  ms.author: cynthist
   ms.topic: unit
   ms.custom:
   - references_regions
 durationInMinutes: 2
 content: |
-  [!include[](includes/1-introduction.md)]
+  [!include[](includes/1-introduction.md)]

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

@@ -6,37 +6,12 @@ metadata:
   prefetch-feature-rollout: true
   title: Explore load balancing
   description: "Explore load balancing"
-  ms.date: 10/07/2024
+  ms.date: 02/13/2025
   author: wwlpublish
-  ms.author: jileary
+  ms.author: cynthist
   ms.topic: unit
   ms.custom:
   - references_regions
 durationInMinutes: 6
 content: |
-  [!include[](includes/2-explore.md)]
-quiz:
-  title: "Check your knowledge"
-  questions:
-  - content: "An engineer has a secure web application that experiences high traffic, and they want to use a load balancer to distribute the workload. Which load balancers support this type of traffic?"
-    choices:
-    - content: "Azure Application Gateway and Azure Front Door."
-      isCorrect: true
-      explanation: "Correct. Secure web applications use HTTPS traffic. Azure Application Gateway and Azure Front Door support HTTPS traffic."
-    - content: "Azure Load Balancer and Traffic Manager."
-      isCorrect: false
-      explanation: "Incorrect. Secure web applications use HTTPS traffic. Azure Load Balancer and Traffic Manager support non-HTTPS traffic."
-    - content: "Azure Application Gateway only."
-      isCorrect: false
-      explanation: "Incorrect. Secure web applications use HTTPS traffic. Azure Application Gateway does support HTTPS traffic, but it's not the only load balancer that does."
-  - content: "Which type of load balancing services distribute traffic across global backends for web applications?"
-    choices:
-    - content: "Azure Application Gateway."
-      isCorrect: false
-      explanation: "Incorrect. Azure Application Gateway does not distribute traffic across global backends."
-    - content: "Azure Front Door."
-      isCorrect: true
-      explanation: "Correct. Azure Front Door distributes traffic across global backends for web applications."
-    - content: "Azure Load Balancer."
-      isCorrect: false
-      explanation: "Incorrect. Azure Load Balancer does not distribute traffic across global backends for web applications."
+  [!include[](includes/2-explore.md)]

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

@@ -6,9 +6,9 @@ metadata:
   prefetch-feature-rollout: true
   title: Design and implement Azure load balancer using the Azure portal
   description: "Design and implement Azure load balancer using the Azure portal"
-  ms.date: 10/07/2024
+  ms.date: 02/13/2025
   author: wwlpublish
-  ms.author: jileary
+  ms.author: cynthist
   ms.topic: unit
   ms.custom:
   - references_regions
@@ -39,4 +39,4 @@ quiz:
       explanation: "Incorrect. Basic SKU doesn't support outbound rules."
     - content: "Either Standard or Basic"
       isCorrect: false
-      explanation: "Incorrect. Basic SKU doesn't support outbound rules."
+      explanation: "Incorrect. Basic SKU doesn't support outbound rules."

learn-pr/wwl-azure/load-balancing-non-https-traffic-azure/4-exercise-create-configure-azure-load-balancer.yml

@@ -6,12 +6,12 @@ metadata:
   prefetch-feature-rollout: true
   title: 'Exercise: create and configure an Azure load balancer'
   description: "Exercise: create and configure an Azure load balancer"
-  ms.date: 10/07/2024
+  ms.date: 02/13/2025
   author: wwlpublish
-  ms.author: jileary
+  ms.author: cynthist
   ms.topic: unit
   ms.custom:
   - references_regions
 durationInMinutes: 15
 content: |
-  [!include[](includes/4-exercise-create-configure-azure-load-balancer.md)]
+  [!include[](includes/4-exercise-create-configure-azure-load-balancer.md)]

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

@@ -6,9 +6,9 @@ metadata:
   prefetch-feature-rollout: true
   title: Explore Azure Traffic Manager
   description: "Explore Azure Traffic Manager"
-  ms.date: 10/07/2024
+  ms.date: 02/13/2025
   author: wwlpublish
-  ms.author: jileary
+  ms.author: cynthist
   ms.topic: unit
   ms.custom:
   - references_regions
@@ -39,4 +39,4 @@ quiz:
       explanation: "Incorrect. Select this routing method to direct users to specific endpoints (Azure, External, or Nested) based on where their DNS queries originate from geographically."
     - content: "Priority"
       isCorrect: false
-      explanation: "Incorrect. Select this routing method for one primary service endpoint for all traffic. You can provide multiple backup endpoints in case the primary or one of the backup endpoints is unavailable."
+      explanation: "Incorrect. Select this routing method for one primary service endpoint for all traffic. You can provide multiple backup endpoints in case the primary or one of the backup endpoints is unavailable."

learn-pr/wwl-azure/load-balancing-non-https-traffic-azure/6-exercise-create-traffic-manager-profile-using-azure-portal.yml

@@ -6,12 +6,12 @@ metadata:
   prefetch-feature-rollout: true
   title: 'Exercise: create a Traffic Manager profile using the Azure portal'
   description: "Exercise: create a Traffic Manager profile using the Azure portal"
-  ms.date: 10/07/2024
+  ms.date: 02/13/2025
   author: wwlpublish
-  ms.author: jileary
+  ms.author: cynthist
   ms.topic: unit
   ms.custom:
   - references_regions
 durationInMinutes: 7
 content: |
-  [!include[](includes/6-exercise-create-traffic-manager-profile-using-azure-portal.md)]
+  [!include[](includes/6-exercise-create-traffic-manager-profile-using-azure-portal.md)]

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

@@ -6,12 +6,12 @@ metadata:
   prefetch-feature-rollout: true
   title: Summary
   description: "Summary"
-  ms.date: 10/07/2024
+  ms.date: 02/13/2025
   author: wwlpublish
-  ms.author: jileary
+  ms.author: cynthist
   ms.topic: unit
   ms.custom:
   - references_regions
 durationInMinutes: 1
 content: |
-  [!include[](includes/7-summary.md)]
+  [!include[](includes/7-summary.md)]

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

@@ -73,4 +73,4 @@ You can use the **Azure Load Balancing** page in the Azure portal to help you gu
 
  -  Optionally, you can also click the **Service comparison** or **Tutorial** tabs for more information and training on the different load balancing services.
 
-Now let's look at each of the main Azure load balancing services in more detail.
+Now let's look at each of the main Azure load balancing services in more detail.

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

@@ -1,3 +1,4 @@
+
 **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.
 
 ## Choosing a load balancer type
@@ -358,8 +359,8 @@ You need to enter the following information on the **Add load balancing rule** p
  -  **Backend port**: You can choose to route traffic to the virtual machine in the backend pool using a different port than the one that clients use by default to communicate with the load balancer (port 80)
  -  **Backend pool**: Select an existing backend pool. The virtual machines in this backend pool are the target for the load balanced traffic.
  -  **Health probe**: Select an existing health probe or create a new one. The load balancing rule uses the health probe to determine which virtual machines in the backend pool are healthy and therefore can receive load balanced traffic.
- -  **Session persistence**: You can choose **None**, or **Client IP**, or **Client IP and protocol**. Session persistence specifies that traffic is processed by the same virtual machine in the session. **None** specifies that successive requests from the same client may be handled by any virtual machine. **Client IP** specifies how successive requests from the same client IP address are processed. **Client IP and protocol** specifies that successive requests from the same client IP address and protocol combination are processed by the same virtual machine.
- -  **Idle timeout (minutes)**: Specify the time to keep a TCP or HTTP connection open without relying on clients to send *keep-alive* messages. The default idle timeout is **4** minutes, which is also the minimum setting. The maximum setting is 30 minutes.
+ -  **Session persistence**: You can choose **None**, or **Client IP**, or **Client IP and protocol**. Session persistence specifies that the same virtual machine processes the session. **None** specifies that successive requests from the same client may be handled by any virtual machine. **Client IP** specifies how successive requests from the same client IP address are processed. **Client IP and protocol** specifies that successive requests from the same client IP address and protocol combination are processed by the same virtual machine.
+ -  **Idle time out (minutes)**: Specify the time to keep a TCP or HTTP connection open without relying on clients to send *keep-alive* messages. The default idle time out is **4** minutes, which is also the minimum setting. The maximum setting is 30 minutes.
  -  **Floating IP**: Choose between **Disabled** or **Enabled**. With Floating IP set to **Disabled**, Azure exposes a traditional load balancing IP address mapping scheme for ease of use (the VM instances' IP). With Floating IP set to **Enabled**, it changes the IP address mapping to the Frontend IP of the load balancer to allow for more flexibility.
 
 You then click **Add** to add the load balancing rule.

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

@@ -1,3 +1,4 @@
+
 Azure Traffic Manager 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.
 
 Traffic Manager uses DNS to direct the client requests to the appropriate service endpoint based on a traffic-routing method. Traffic manager also provides health monitoring for every endpoint. The endpoint can be any Internet-facing service hosted inside or outside of Azure. Traffic Manager provides a range of traffic-routing methods and endpoint monitoring options to suit different application needs and automatic failover models. Traffic Manager is resilient to failure, including the failure of an entire Azure region.
@@ -511,10 +512,10 @@ Then, under the **Endpoint monitor settings** section, you specify the following
 :::row-end:::
 :::row:::
   :::column:::
-    Probe timeout
+    Probe time out
   :::column-end:::
   :::column:::
-    This property specifies the amount of time the Traffic Manager probing agent should wait before considering a health probe check to an endpoint a failure. If the Probing Interval is set to 30 seconds, then you can set the Timeout value between 5 and 10 seconds. If no value is specified, it uses a default value of 10 seconds. If the Probing Interval is set to 10 seconds, then you can set the Timeout value between 5 and 9 seconds. If no Timeout value is specified, it uses a default value of 9 seconds.
+    This property specifies the amount of time the Traffic Manager probing agent should wait before considering a health probe check to an endpoint a failure. If the Probing Interval is set to 30 seconds, then you can set the time out value between 5 and 10 seconds. If no value is specified, it uses a default value of 10 seconds. If the Probing Interval is set to 10 seconds, then you can set the time out value between 5 and 9 seconds. If no time out value is specified, it uses a default value of 9 seconds.
   :::column-end:::
 :::row-end:::
 
@@ -526,9 +527,9 @@ Click **Save**.
 
 ### How endpoint monitoring works
 
-When the monitoring protocol is set as HTTP or HTTPS, the Traffic Manager probing agent makes a GET request to the endpoint using the protocol, port, and relative path given. An endpoint is considered healthy if probing agent receives a 200-OK response, or any of the responses configured in the Expected status code \*ranges. If the response is a different value or no response get received within the timeout period, the Traffic Manager probing agent reattempts according to the Tolerated Number of Failures setting. No reattempts are done if this setting is 0. The endpoint is marked unhealthy if the number of consecutive failures is higher than the Tolerated Number of Failures setting.
+When the monitoring protocol is set as HTTP or HTTPS, the Traffic Manager probing agent makes a GET request to the endpoint using the protocol, port, and relative path given. An endpoint is considered healthy if probing agent receives a 200-OK response, or any of the responses configured in the Expected status code \*ranges. If the response is a different value or no response get received within the time out period, the Traffic Manager probing agent reattempts according to the Tolerated Number of Failures setting. No reattempts are done if this setting is 0. The endpoint is marked unhealthy if the number of consecutive failures is higher than the Tolerated Number of Failures setting.
 
-When the monitoring protocol is TCP, the Traffic Manager probing agent creates a TCP connection request using the port specified. If the endpoint responds to the request with a response to establish the connection, that health check is marked as a success. The Traffic Manager probing agent resets the TCP connection. In cases where the response is a different value or no response get received within the timeout period, the Traffic Manager probing agent reattempts according to the Tolerated Number of Failures setting. No reattempts are made if this setting is 0. If the number of consecutive failures is higher than the Tolerated Number of Failures setting, then that endpoint is marked unhealthy.
+When the monitoring protocol is TCP, the Traffic Manager probing agent creates a TCP connection request using the port specified. If the endpoint responds to the request with a response to establish the connection, that health check is marked as a success. The Traffic Manager probing agent resets the TCP connection. In cases where the response is a different value or no response get received within the time out period, the Traffic Manager probing agent reattempts according to the Tolerated Number of Failures setting. No reattempts are made if this setting is 0. If the number of consecutive failures is higher than the Tolerated Number of Failures setting, then that endpoint is marked unhealthy.
 
 In all cases, Traffic Manager probes from multiple locations. The consecutive failure determines what happen within each region. Endpoints are receiving health probes from Traffic Manager with a higher frequency than the setting used for Probing Interval.