Merge pull request #54082 from staleycyn/patch-3

Content drift updates for the Design ExpressRoute module

Author: JamesJBarnett

learn-pr/wwl-azure/design-implement-azure-expressroute/includes/10-troubleshoot-expressroute-connection-issues.md

@@ -23,7 +23,7 @@ For an ExpressRoute circuit to be operational, the Microsoft **Circuit status**
 
 ### Verify the peering 
 
-Each ExpressRoute circuit can have: an Azure private peering, an Azure public peering, and/or a Microsoft peering. For success, the peering status should be **provisioned**. 
+Each ExpressRoute circuit can have one or both peerings: Azure private peering and Microsoft peering. For success, the peering status should be **provisioned**. 
 
 :::image type="content" source="../media/peering-status.png" alt-text="Screenshot of the peering status. ":::
 
@@ -36,4 +36,4 @@ The Azure portal has information on configuring and troubleshooting ExpressRoute
 When you need assistance from Microsoft or from an ExpressRoute partner, you must provide the ExpressRoute Service Key. The Service Key uniquely identifies your circuit.
 
 > [!TIP]
-> Learn more about ExpressRoute troubleshooting in the [Troubleshoot virtual network connectivity in Microsoft Azure](/training/modules/cloud-hybrid-connectivity/) module.
+> Learn more about ExpressRoute troubleshooting in the [Troubleshoot cloud and hybrid connectivity in Microsoft Azure](/training/modules/cloud-hybrid-connectivity/) module.

learn-pr/wwl-azure/design-implement-azure-expressroute/includes/3-design-expressroute-deployment.md

@@ -14,10 +14,15 @@ This table highlights the key differences between ExpressRoute Direct and the Se
 | Feature/Aspect | ExpressRoute using a Service Provider |   ExpressRoute Direct   |
 | --- | --- | --- |
 | Usage cases | Small to medium sized business looking for a simple setup with managed services | Large enterprises with mission-critical applications requiring high-performance connectivity |
-| Connectivity | Connection via a service provider's infrastructure | Direct connection to Microsoft's network through dual 10-Gbps or 100-Gbps ports |
-| Circuit SKUs |                             Ranges from 50 Mbps to 10 Gbps                             | 10-Gbps: 1, 2, 5, 10 Gbps; 100-Gbps: 5, 10, 40, 100 Gbps |
+| Connectivity | Connection via a service provider's infrastructure | Direct connection to Microsoft's network through dual 10-Gbps, 100-Gbps,or 400-Gbps ports |
+| Circuit SKUs | Ranges from 50 Mbps to 10 Gbps | 10-Gbps: 1, 2, 5, 10 Gbps; 100-Gbps: 5, 10, 40, 100 Gbps; 400-Gbps: 5, 10, 40, 100, 200, 400 Gbps |
 | Optimization | Optimized for single tenant | Optimized for a single tenant with multiple business units |
 
+
+> [!NOTE]
+> 400-Gbps ExpressRoute Direct is available in limited peering locations and requires enrollment. 
+
+
 Azure ExpressRoute offers different [SKUs](/azure/expressroute/expressroute-faqs#expressroute-premium) to cater to various connectivity needs and performance requirements. Each SKU has different pricing and features, such as varying limits on the number of virtual networks you can connect to and the bandwidth options available. When choosing a SKU, consider your organization's geographic footprint, latency requirements, and budget constraints.
 
 :::image type="content" source="../media/sku-scope.png" alt-text="Diagram of the ExpressRoute SKU coverage.":::

learn-pr/wwl-azure/design-implement-azure-expressroute/includes/6-configure-peering-for-expressroute-deployment.md

@@ -18,11 +18,11 @@ This comparison table compares Private peering with Microsoft peering.
 
 | Feature                     | ExpressRoute Private Peering                  | ExpressRoute Microsoft Peering                |
 |-----------------------------|-----------------------------------------------|-----------------------------------------------|
-| **Purpose**                 | Connects directly to Azure virtual networks   | Connects to Microsoft services like Office 365, Dynamics 365, and Azure PaaS services |
+| **Purpose**                 | Connects directly to Azure virtual networks   | Connects to Microsoft services like Microsoft 365, Dynamics 365, and Azure PaaS services |
 | **Traffic Type**            | Private IP traffic                            | Public IP traffic                             |
 | **Access**                  | Direct access to Azure VMs and services within virtual networks | Access to Microsoft SaaS services and Azure PaaS services |
 | **Security**                | Traffic stays on private network, not exposed to the internet | Traffic is routed over public IPs but through a private connection |
-| **Use Cases**               | Enterprise applications, databases, and other workloads requiring secure, high-performance connectivity | Access to Microsoft services like Office 365, Dynamics 365, and Azure PaaS services |
+| **Use Cases**               | Enterprise applications, databases, and other workloads requiring secure, high-performance connectivity | Access to Microsoft services like Microsoft 365, Dynamics 365, and Azure PaaS services |
 | **Network Isolation**       | Provides network isolation from the public internet | Doesn't provide network isolation from the public internet, but ensures traffic doesn't traverse the public internet |
 | **Bandwidth Options**       | Offers scalable bandwidth options             | Offers scalable bandwidth options             |
 
@@ -43,4 +43,4 @@ ExpressRoute locations, also known as peering locations or meet-me locations, ar
 
 - **Compliance and regulatory requirements**: If your organization has specific compliance or regulatory requirements, ensure that the peering location meets these standards. Compliance requirements might include data residency or industry-specific regulations.
 
-- **Future growth and scalability**: Consider your future growth plans and ensure that the peering location can accommodate increased bandwidth and other connections as your needs evolve.
+- **Future growth and scalability**: Consider your future growth plans and ensure that the peering location can accommodate increased bandwidth and other connections as your needs evolve.

learn-pr/wwl-azure/design-implement-azure-expressroute/includes/9-improve-data-path-performance-between-networks-expressroute-fastpath.md

@@ -1,7 +1,10 @@
-
-
 ExpressRoute virtual network gateway facilitates the exchange of network routes and directs network traffic. [ExpressRoute FastPath](/azure/expressroute/about-fastpath) enhances data path performance between your on-premises network and your virtual networks. When enabled, ExpressRoute FastPath routes network traffic directly to virtual machines, bypassing the ExpressRoute virtual network gateway. 
 
+To use FastPath, your ExpressRoute virtual network gateway must be one of the following SKUs. A gateway is still required to exchange route information. FastPath bypasses the gateway only for data traffic.
+- Ultra Performance
+- ErGw3AZ
+- ErGwScale (minimum 10 scale units)
+
 FastPath is available on all ExpressRoute circuits. ExpressRoute FastPath is useful for enterprises that need consistent and high-performance connectivity to Azure for mission-critical applications. 
 
 :::image type="content" source="../media/fastpath-vnet-peering.png" alt-text="Diagram of the FastPath layout.":::
@@ -18,4 +21,11 @@ FastPath is available on all ExpressRoute circuits. ExpressRoute FastPath is use
 
 - **Reliability**. With a more direct connection, there's less chance of network congestion or packet loss, improving the reliability of data transfers.
 
-- **Security**. FastPath ensures that data travels through fewer intermediary points, potentially reducing exposure to security risks.
+- **Security**. FastPath ensures that data travels through fewer intermediary points, potentially reducing exposure to security risks.
+
+### Advanced FastPath features (ExpressRoute Direct only)
+
+When using FastPath with an ExpressRoute Direct circuit, three additional capabilities are available:
+-	**Virtual network peering**: FastPath sends traffic directly to VMs in spoke virtual networks connected via VNet peering. Hub and spoke virtual networks must be in the same region.
+-	**User-Defined Routes (UDRs)**: FastPath honors UDRs configured on the gateway subnet while maintaining the performance bypass.
+-	**Private Link and private endpoints**: FastPath sends traffic directly to private endpoints in spoke virtual networks. This feature is in limited general availability and requires enrollment.

learn-pr/wwl-azure/design-implement-azure-expressroute/index.yml

@@ -5,7 +5,7 @@ metadata:
   prefetch-feature-rollout: true
   title: Design and Implement Azure ExpressRoute
   description: "You learn how to design and implement Azure ExpressRoute, ExpressRoute Global Reach, ExpressRoute FastPath."
-  ms.date: 01/26/2026
+  ms.date: 03/23/2026
   author: wwlpublish
   ms.author: cynthist
   ms.topic: module