Merge pull request #54117 from MicrosoftDocs/main

learn-build-service-prod[bot] · web-flow · commit b26239472a81 · 2026-04-03T23:08:48.000Z
Auto Publish – main to live - 2026-04-03 23:00 UTC
diff --git a/learn-pr/advocates/improve-reliability-scaling/includes/5-applications.md b/learn-pr/advocates/improve-reliability-scaling/includes/5-applications.md
@@ -63,7 +63,7 @@ Another way to improve the performance of your application is to implement an in
 
 Now you know that performance doesn't equal scalability exactly, but by improving the performance of your application, you can reduce the load on other resources. This improvement means you may not have to scale as soon.
 
-Azure Cache for Redis is a managed Redis offering. Redis can be used for many patterns and use cases. For your product service in this scenario, you would likely implement the cache-aside pattern. In this pattern, you load items from the database into the cache as needed, making your application more performant, and reducing the load on the database.
+Azure Managed Redis is a managed Redis offering. Redis can be used for many patterns and use cases. For your product service in this scenario, you would likely implement the cache-aside pattern. In this pattern, you load items from the database into the cache as needed, making your application more performant, and reducing the load on the database.
 
 Redis can also be used as a messaging queue for caching web content or for user session caching. This type of caching may be more suitable for other services in the system such as the shopping cart service, where you could store shopping cart data per session in Redis instead of using a cookie.
 
@@ -111,4 +111,4 @@ Sharding is a technique to distribute large amounts of identically structured da
 
 Your application adds the relevant data to the relevant shard, and thus make your system scalable beyond the constraints of the individual database.
 
-Azure SQL offers the Azure Elastic Database tools. These tools help you create, maintain, and query sharded SQL databases in Azure from your application logic.
+Azure SQL offers the Azure Elastic Database tools. These tools help you create, maintain, and query sharded SQL databases in Azure from your application logic.
diff --git a/learn-pr/advocates/improve-reliability-scaling/includes/6-global.md b/learn-pr/advocates/improve-reliability-scaling/includes/6-global.md
@@ -1,4 +1,4 @@
-In the previous unit, we described scaling compute, and making it more available in the process. We also suggested adding an Azure Cache for Redis to improve performance, and scaling out Azure SQL databases via sharding.
+In the previous unit, we described scaling compute, and making it more available in the process. We also suggested adding Azure Managed Redis to improve performance, and scaling out Azure SQL databases via sharding.
 
 The next step, as your business grows, might be to go global. However, there are some things you need to think about before trying to implement a fully global architecture.
 
diff --git a/learn-pr/paths/understand-data-concepts/index.yml b/learn-pr/paths/understand-data-concepts/index.yml
@@ -5,7 +5,7 @@ metadata:
   description: Data is key to most business operations and services and an understanding of data is essential in many roles. This learning path covers data concepts, data analytics, and data roles, services, and products.
   ms.date: 02/18/2025
   author: wwlpublish
-  ms.author: rcaper
+  ms.author: weslbo
   ms.topic: learning-path
 title: Understand data concepts
 prerequisites: |
diff --git a/learn-pr/wwl-azure/load-balancing-non-https-traffic-azure/includes/3-design-implement-azure-load-balancer-using-azure-portal.md b/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.
diff --git a/learn-pr/wwl-azure/load-balancing-non-https-traffic-azure/includes/5-explore-azure-traffic-manager.md b/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. 
diff --git a/learn-pr/wwl-azure/load-balancing-non-https-traffic-azure/includes/7-summary.md b/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
 
diff --git a/learn-pr/wwl-azure/load-balancing-non-https-traffic-azure/index.yml b/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: |
diff --git a/learn-pr/wwl-data-ai/get-started-data-analytics/index.yml b/learn-pr/wwl-data-ai/get-started-data-analytics/index.yml
@@ -5,7 +5,7 @@ metadata:
   description: "This content is a part of Get started with data analytics."
   ms.date: 02/14/2025
   author: wwlpublish
-  ms.author: rcaper
+  ms.author: weslbo
   ms.topic: module
   ms.collection: N/A
   ms.custom:
diff --git a/learn-pr/wwl-data-ai/get-started-data-concepts/index.yml b/learn-pr/wwl-data-ai/get-started-data-concepts/index.yml
@@ -5,7 +5,7 @@ metadata:
   description: "Businesses rely on data. Understanding data is key to many business operations. This module covers what data is, when to sort and filter data and when to calculate derived values from data."
   ms.date: 02/14/2025
   author: wwlpublish
-  ms.author: rcaper
+  ms.author: weslbo
   ms.topic: module
   ms.collection: N/A
   ms.custom:

Original file line number	Diff line number	Diff line change
`@@ -1,4 +1,4 @@`
`1`		`-In the previous unit, we described scaling compute, and making it more available in the process. We also suggested adding an Azure Cache for Redis to improve performance, and scaling out Azure SQL databases via sharding.`
	`1`	`+In the previous unit, we described scaling compute, and making it more available in the process. We also suggested adding Azure Managed Redis to improve performance, and scaling out Azure SQL databases via sharding.`
`2`	`2`
`3`	`3`	`The next step, as your business grows, might be to go global. However, there are some things you need to think about before trying to implement a fully global architecture.`
`4`	`4`