Merge pull request #293943 from duongau/erfreshness3

ExpressRoute - Freshness review (Batch 3 - Jan 2025)

Author: JamesJBarnett

articles/expressroute/expressroute-connectivity-models.md

@@ -5,7 +5,7 @@ services: expressroute
 author: duongau
 ms.service: azure-expressroute
 ms.topic: concept-article
-ms.date: 12/28/2023
+ms.date: 01/31/2025
 ms.author: duau
 ---
 
@@ -26,7 +26,7 @@ You can connect your on-premises datacenters or offices to the Microsoft cloud t
 
 ## <a name="IPVPN"></a>Any-to-any (IPVPN) networks
 
-You can integrate your WAN with the Microsoft cloud. IPVPN providers (typically MPLS VPN) offer any-to-any connectivity between your branch offices and datacenters. The Microsoft cloud can be interconnected to your WAN to make it appear like any other branch office. WAN providers typically offer managed Layer 3 connectivity. ExpressRoute capabilities and features are all identical across all of the above connectivity models.
+You can integrate your WAN with the Microsoft cloud. IPVPN providers (typically MPLS VPN) offer any-to-any connectivity between your branch offices and datacenters. The Microsoft cloud can be interconnected to your WAN to make it appear like any other branch office. WAN providers typically offer managed Layer 3 connectivity. ExpressRoute capabilities and features are all identical across all of the connectivity models listed previously.
 
 ## <a name="Direct"></a>Direct from ExpressRoute sites
 

articles/expressroute/expressroute-erdirect-about.md

@@ -7,15 +7,15 @@ ms.service: azure-expressroute
 ms.custom:
   - ignite-2023
 ms.topic: concept-article
-ms.date: 03/28/2024
+ms.date: 01/31/2025
 ms.author: duau
 ---
 
 # About ExpressRoute Direct
 
-ExpressRoute Direct gives you the ability to connect directly into the Microsoft global network at peering locations strategically distributed around the world. ExpressRoute Direct provides dual 100-Gbps or 10-Gbps connectivity, that supports Active/Active connectivity at scale. You can work with any service provider to set up ExpressRoute Direct.
+ExpressRoute Direct gives you the ability to connect directly into the Microsoft global network at peering locations strategically distributed around the world. ExpressRoute Direct provides dual 100-Gbps or 10-Gbps connectivity that supports active-active connectivity at scale. You can work with any service provider to set up ExpressRoute Direct.
 
-Key features that ExpressRoute Direct provides include, but not limited to:
+Key features include, but not limited to:
 
 * Large data ingestion into services like Azure Storage and Azure Cosmos DB.
 * Physical isolation for industries that regulates and require dedicated or isolated connectivity such as banks, government, and retail companies.
@@ -45,16 +45,16 @@ Once enrolled, verify that **Microsoft.Network** resource provider is registered
 
 1. In your subscription, for **Resource Providers**, verify **Microsoft.Network** provider shows a **Registered** status. If the Microsoft.Network resource provider isn't present in the list of registered providers, add it.
 
-When you start using ExpressRoute Direct and notice that there aren't any available ports for your chosen peering location, submit a support request to request for more inventory.
+If you start using ExpressRoute Direct and find that ports at your selected peering location are unavailable, submit a support ticket to request more inventories.
 
 ## ExpressRoute using a service provider and ExpressRoute Direct
 
 | ExpressRoute using a service provider | ExpressRoute Direct | 
 | --- | --- |
-| Uses a service provider to enable fast onboarding and connectivity into existing infrastructure | Requires 100-Gbps or 10-Gbps infrastructure and full management of all layers |
-| Integrates with hundreds of providers including Ethernet and MPLS | Direct and Dedicated capacity for regulated industries and large data ingestion |
-| Circuits SKUs ranging from 50 Mbps to 10 Gbps | Customer may select a combination of the following circuit SKUs on 100-Gbps ExpressRoute Direct: <ul><li>5 Gbps</li><li>10 Gbps</li><li>40 Gbps</li><li>100 Gbps</li></ul> Customer may select a combination of the following circuit SKUs on 10-Gbps ExpressRoute Direct:<ul><li>1 Gbps</li><li>2 Gbps</li><li>5 Gbps</li><li>10 Gbps</li></ul>
-| Optimized for a single tenant | Optimized for single tenant with multiple business units and multiple work environments
+| Uses a service provider to enable fast onboarding and connectivity into existing infrastructure | Requires 100-Gbps or 10-Gbps infrastructure and full management of all layers. |
+| Integrates with hundreds of providers including Ethernet and MPLS | Direct and Dedicated capacity for regulated industries and large data ingestion. |
+| Circuits SKUs ranging from 50 Mbps to 10 Gbps | You can select a combination of the following circuit SKUs on 100-Gbps ExpressRoute Direct: <ul><li>5 Gbps</li><li>10 Gbps</li><li>40 Gbps</li><li>100 Gbps</li></ul> You can select a combination of the following circuit SKUs on 10-Gbps ExpressRoute Direct:<ul><li>1 Gbps</li><li>2 Gbps</li><li>5 Gbps</li><li>10 Gbps</li></ul> |
+| Optimized for a single tenant | Optimized for single tenant with multiple business units and multiple work environments. |
 
 ## ExpressRoute Direct circuits
 
@@ -78,33 +78,33 @@ ExpressRoute Direct supports large data ingestion scenarios into services such a
 | <ul><li>5 Gbps</li><li>10 Gbps</li><li>40 Gbps</li><li>100 Gbps</li></ul> | <ul><li>1 Gbps</li><li>2 Gbps</li><li>5 Gbps</li><li>10 Gbps</li></ul>
 
 > [!NOTE]
-> You can provision logical ExpressRoute circuits on top of your selected ExpressRoute Direct resource of 10-Gbps or 100-Gbps up to the subscribed Bandwidth of 20Gbps or 200Gbps. For example,you can provision two 10 Gbps ExpressRoute circuits within a single 10 Gbps ExpressRoute Direct resource (port pair).
+> You can create logical ExpressRoute circuits on top of your selected ExpressRoute Direct resource of 10-Gbps or 100-Gbps up to the subscribed Bandwidth of 20 Gbps or 200 Gbps. For example, you can create two 10-Gbps ExpressRoute circuits within a single 10-Gbps ExpressRoute Direct resource (port pair).
 
 ## Technical Requirements
 
 * Microsoft Enterprise Edge Router (MSEE) Interfaces:
     * Dual 10 Gigabit or 100-Gigabit Ethernet ports only across router pair
     * Single Mode LR Fiber connectivity
-      * MSEE supports QSFP-100G-LR-4 for 100Gbps (Use compatible optics on your devices) 
+      * MSEE supports QSFP-100G-LR-4 for 100 Gbps (Use compatible optics on your devices) 
     * IPv4 and IPv6
-    * IP MTU 1500 bytes
+    * IP MTU 1,500 bytes
 
 * Switch/Router Layer 2/Layer three Connectivity:
     * Must support 1 802.1Q (Dot1Q) tag or two Tag 802.1Q (QinQ) tag encapsulation
     * Ethertype = 0x8100
     * Must add the outer VLAN tag (STAG) based on the VLAN ID specified by Microsoft - *applicable only on QinQ*
     * Must support multiple BGP sessions (VLANs) per port and device
-    * IPv4 and IPv6 connectivity. *For IPv6 no extra subinterface will be created. IPv6 address will be added to existing subinterface*. 
+    * IPv4 and IPv6 connectivity. *IPv6 address is added to existing subinterface*. 
     * Optional: [Bidirectional Forwarding Detection (BFD)](./expressroute-bfd.md) support, which is configured by default on all Private Peerings on ExpressRoute circuits
  
 > [!NOTE]
-> ExpressRoute Direct does not support Link Aggregation Control Protocol (LACP) or Multi-Chassis Link Aggregation (MLAG)
+> ExpressRoute Direct doesn't support Link Aggregation Control Protocol (LACP) or Multi-Chassis Link Aggregation (MLAG)
 
 ## VLAN Tagging
 
 ExpressRoute Direct supports both QinQ and Dot1Q VLAN tagging.
 
-* **QinQ VLAN Tagging** allows for isolated routing domains on a per ExpressRoute circuit basis. Azure dynamically gives an S-Tag at circuit creation and can't be changed. Each peering on the circuit (Private and Microsoft) will use a unique C-Tag as the VLAN. The C-Tag isn't required to be unique across circuits on the ExpressRoute Direct ports.
+* **QinQ VLAN Tagging** allows for isolated routing domains on a per ExpressRoute circuit basis. Azure dynamically gives an S-Tag at circuit creation that can't be changed. Each peering on the circuit (Private and Microsoft) uses a unique C-Tag as the VLAN. The C-Tag isn't required to be unique across circuits on the ExpressRoute Direct ports.
 
 * **Dot1Q VLAN Tagging** allows for a single tagged VLAN on a per ExpressRoute Direct port pair basis. A C-Tag used on a peering must be unique across all circuits and peerings on the ExpressRoute Direct port pair.
 

articles/expressroute/expressroute-global-reach.md

@@ -5,55 +5,55 @@ services: expressroute
 author: duongau
 ms.service: azure-expressroute
 ms.topic: concept-article
-ms.date: 06/29/2023
+ms.date: 01/31/2025
 ms.author: duau
 ms.custom: references_regions
 ---
 
 # About ExpressRoute Global Reach
 
-ExpressRoute is a private and resilient way to connect your on-premises networks to the Microsoft Cloud. You can access many Microsoft cloud services such as Azure and Microsoft 365 from your private data center or your corporate network. For example, you may have a branch office in San Francisco with an ExpressRoute circuit in Silicon Valley. You have a second branch office in London with an ExpressRoute circuit also in the same city. Both branch offices have high-speed connectivity to Azure resources in US West and UK South. However, the branch offices can't connect and send data directly with one another. In other words, 10.0.1.0/24 can send data to 10.0.3.0/24 and 10.0.4.0/24 network, but NOT to 10.0.2.0/24 network.
+ExpressRoute provides a private and resilient connection between your on-premises networks and the Microsoft Cloud, allowing access to services like Azure and Microsoft 365 from your data center or corporate network. For instance, you might have a branch office in San Francisco with an ExpressRoute circuit in Silicon Valley, and another branch office in London with an ExpressRoute circuit there. Both offices can connect to Azure resources in US West and UK South, but they can't directly communicate with each other. For example, the 10.0.1.0/24 network can send data to the 10.0.3.0/24 and 10.0.4.0/24 networks, but not to the 10.0.2.0/24 network.
 
-:::image type="content" source="./media/expressroute-global-reach/dual-circuit.png" alt-text="Diagram that shows circuits not linked together with ExpressRoute Global Reach.":::
+:::image type="content" source="./media/expressroute-global-reach/dual-circuit.png" alt-text="Diagram showing circuits not linked together with ExpressRoute Global Reach.":::
 
-With **ExpressRoute Global Reach**, you can link ExpressRoute circuits together to make a private network between your on-premises networks. In the above example, with the addition of ExpressRoute Global Reach, your San Francisco office (10.0.1.0/24) can directly exchange data with your London office (10.0.2.0/24) through the existing ExpressRoute circuits and via Microsoft's global network. 
+With **ExpressRoute Global Reach**, you can link ExpressRoute circuits to create a private network between your on-premises networks. In the previous example, with ExpressRoute Global Reach, your San Francisco office (10.0.1.0/24) can directly exchange data with your London office (10.0.2.0/24) through the existing ExpressRoute circuits and Microsoft's global network.
 
-:::image type="content" source="./media/expressroute-global-reach/global-reach.png" alt-text="Diagram that shows circuits linked together with ExpressRoute Global Reach.":::
+:::image type="content" source="./media/expressroute-global-reach/global-reach.png" alt-text="Diagram showing circuits linked together with ExpressRoute Global Reach.":::
 
 ## Use case
 
-ExpressRoute Global Reach is designed to complement your service provider’s WAN implementation and connect your branch offices across the world. For example, if your service provider primarily operates in the United States and has linked all of your branches in the U.S., but the service provider doesn’t operate in Japan and Hong Kong Special Administrative Region, with ExpressRoute Global Reach you can work with a local service provider and Microsoft to connect your branches there to the ones in the U.S. using ExpressRoute and our global network.
+ExpressRoute Global Reach complements your service provider’s WAN implementation by connecting your branch offices worldwide. For example, if your service provider operates primarily in the United States and connects all your U.S. branches, but doesn't operate in Japan and Hong Kong SAR, you can use ExpressRoute Global Reach to work with a local service provider and Microsoft to connect your branches in Japan and Hong Kong SAR to branches in the U.S. using ExpressRoute and Microsoft's global network.
 
 :::image type="content" source="./media/expressroute-global-reach/global-reach-infrastructure.png" alt-text="Diagram that shows a use case for Express Route Global Reach.":::
 
 ## Availability
 
-ExpressRoute Global Reach is supported in the following places. 
+ExpressRoute Global Reach is available in the following locations:
 
-> [!NOTE] 
+> [!NOTE]
 > To enable ExpressRoute Global Reach between [different geopolitical regions](expressroute-locations-providers.md#locations), your circuits must be **Premium SKU**.
 
-* Australia
-* Canada
-* Denmark
-* France
-* Germany
-* Hong Kong SAR
-* India
-* Ireland
-* Japan
-* Korea
-* Netherlands
-* New Zealand
-* Norway
-* Poland
-* Singapore
-* South Africa (Johannesburg only)
-* Sweden
-* Switzerland
-* Taiwan
-* United Kingdom
-* United States
+- Australia
+- Canada
+- Denmark
+- France
+- Germany
+- Hong Kong SAR
+- India
+- Ireland
+- Japan
+- Korea
+- Netherlands
+- New Zealand
+- Norway
+- Poland
+- Singapore
+- South Africa (Johannesburg only)
+- Sweden
+- Switzerland
+- Taiwan
+- United Kingdom
+- United States
 
 ## Next steps
 

articles/expressroute/expressroute-howto-circuit-arm.md

@@ -210,7 +210,7 @@ Peerings                         : []
 
 ### Send the service key to your connectivity provider for provisioning
 
-*ServiceProviderProvisioningState* provides you with information about the current state of provisioning on the service-provider side. *CircuitProvisioningState* provides you with the status on the Microsoft side. For more information about circuit provisioning states, see [Workflows](expressroute-workflows.md#expressroute-circuit-provisioning-states).
+*ServiceProviderProvisioningState* provides you with information about the current state of provisioning on the service-provider side. *CircuitProvisioningState* provides you with the status on the Microsoft side. For more information about circuit provisioning states, see [Workflows](expressroute-workflows.md#expressroute-partner-circuit-provisioning-states).
 
 When you create a new ExpressRoute circuit, the circuit is in the following state:
 

articles/expressroute/expressroute-howto-circuit-portal-resource-manager.md

@@ -115,7 +115,7 @@ You can view the properties of the circuit by selecting it. On the Overview page
 
 ### Send the service key to your connectivity provider for provisioning
 
-On this page, **Provider status** gives you the current state of provisioning on the service-provider side. **Circuit status** provides you with the state on the Microsoft side. For more information about circuit provisioning states, see the [Workflows](expressroute-workflows.md#expressroute-circuit-provisioning-states) article.
+On this page, **Provider status** gives you the current state of provisioning on the service-provider side. **Circuit status** provides you with the state on the Microsoft side. For more information about circuit provisioning states, see the [Workflows](expressroute-workflows.md#expressroute-partner-circuit-provisioning-states) article.
 
 When you create a new ExpressRoute circuit, the circuit is in the following state: