Merge pull request #313104 from duongau/expressroute-freshness-review-560387-batch3

Expressroute freshness review - batch 3

Author: prmerger-automator[bot]

articles/expressroute/expressroute-bfd.md

@@ -1,11 +1,10 @@
 ---
 title: 'Azure ExpressRoute: Configure BFD'
 description: This article provides instructions on how to configure BFD (Bidirectional Forwarding Detection) over private-peering of an ExpressRoute circuit.
-services: expressroute
 author: duongau
 ms.service: azure-expressroute
 ms.topic: concept-article
-ms.date: 06/03/2024
+ms.date: 03/12/2026
 ms.author: duau
 ---
 
@@ -16,7 +15,7 @@ ExpressRoute supports Bidirectional Forwarding Detection (BFD) both over private
 ## Need for BFD
 
 The following diagram shows the benefit of enabling BFD over ExpressRoute circuit:
-[![1]][1]
+:::image type="content" source="./media/expressroute-bfd/bfd-need.png" alt-text="Diagram showing how BFD expedites link failure detection time.":::
 
 You can enable ExpressRoute circuit either by Layer 2 connections or managed Layer 3 connections. In both cases, if there are more than one Layer-2 devices in the ExpressRoute connection path, the responsibility of detecting any link failures in the path lies with the overlying BGP session.
 
@@ -56,7 +55,7 @@ router bgp 65020
 ```
 
 >[!NOTE]
->To enable BFD under an already existing private or Microsoft peering, you'll need to reset the peering. For IPv4 peering, this will need to be done on Circuits configured with private peering before August 2018 and Microsoft peering before January 2020. For IPv6 peering, this will need to be done on Circuits configured before November 2025. Peerings configured after these dates will have BFD enabled by default. See [Reset ExpressRoute peerings][ResetPeering]. While configuring BFD on your primary and secondary devices is optional, the BFD configuration on the Azure devices for new peerings is not optional and cannot be removed.
+>To enable BFD under an already existing private or Microsoft peering, you'll need to reset the peering. For IPv4 peering, this will need to be done on Circuits configured with private peering before August 2018 and Microsoft peering before January 2020. For IPv6 peering, this will need to be done on Circuits configured before November 2025. Peerings configured after these dates will have BFD enabled by default. See [Reset ExpressRoute peerings](./expressroute-howto-reset-peering.md). While configuring BFD on your primary and secondary devices is optional, the BFD configuration on the Azure devices for new peerings is not optional and cannot be removed.
 >
 
 ## BFD Timer Negotiation
@@ -71,13 +70,6 @@ Between BFD peers, the slower of the two peers determine the transmission rate.
 
 For more information or help, check out the following links:
 
-- [Create and modify an ExpressRoute circuit][CreateCircuit]
-- [Create and modify routing for an ExpressRoute circuit][CreatePeering]
+- [Create and modify an ExpressRoute circuit](./expressroute-howto-circuit-portal-resource-manager.md)
+- [Create and modify routing for an ExpressRoute circuit](./expressroute-howto-routing-portal-resource-manager.md)
 
-<!--Image References-->
-[1]: ./media/expressroute-bfd/bfd-need.png "BFD expedites link failure deduction time"
-
-<!--Link References-->
-[CreateCircuit]: ./expressroute-howto-circuit-portal-resource-manager.md
-[CreatePeering]: ./expressroute-howto-routing-portal-resource-manager.md
-[ResetPeering]: ./expressroute-howto-reset-peering.md

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

@@ -1,11 +1,10 @@
 ---
 title: 'Configure peering for ExpressRoute circuit - Azure PowerShell'
 description: This article shows you how to create and manage routing configuration for an ExpressRoute circuit in the Resource Manager deployment model using PowerShell.
-services: expressroute
 author: duongau
 ms.service: azure-expressroute
 ms.topic: how-to
-ms.date: 04/22/2024
+ms.date: 03/12/2026
 ms.author: duau 
 ms.custom: devx-track-azurepowershell
 
@@ -18,7 +17,7 @@ This article helps you create and manage routing configuration for an ExpressRou
 > * [Azure portal](expressroute-howto-routing-portal-resource-manager.md)
 > * [PowerShell](expressroute-howto-routing-arm.md)
 > * [Azure CLI](howto-routing-cli.md)
-> * [PowerShell (classic)](expressroute-howto-routing-classic.md)
+> * [PowerShell (classic)](/previous-versions/azure/expressroute/expressroute-howto-routing-classic)
 > 
 
 These instructions only apply to circuits created with service providers offering Layer 2 connectivity services. If you're using a service provider that offers managed Layer 3 services, typically an IPVPN, like MPLS, your connectivity provider configures and manages network routing for you.
@@ -51,7 +50,7 @@ In this tutorial, you learn how to:
 This section helps you create, get, update, and delete the Microsoft peering configuration for an ExpressRoute circuit.
 
 > [!IMPORTANT]
-> Microsoft peering of ExpressRoute circuits that were configured prior to August 1, 2017 will have all service prefixes advertised through the Microsoft peering, even if route filters are not defined. Microsoft peering of ExpressRoute circuits that are configured on or after August 1, 2017 will not have any prefixes advertised until a route filter is attached to the circuit. For more information, see [Configure a route filter for Microsoft peering](how-to-routefilter-powershell.md).
+> Microsoft peering of ExpressRoute circuits that were configured prior to August 1, 2017 will have all service prefixes advertised through the Microsoft peering, even if route filters are not defined. Microsoft peering of ExpressRoute circuits that are configured on or after August 1, 2017 will not have any prefixes advertised until a route filter is attached to the circuit. For more information, see [Configure a route filter for Microsoft peering](how-to-routefilter-portal.md).
 > 
 
 ### To create Microsoft peering
@@ -164,29 +163,11 @@ This section helps you create, get, update, and delete the Azure private peering
 
 ### To create Azure private peering
 
-1. Import the PowerShell module for ExpressRoute.
-
-   Install the latest PowerShell installer from [PowerShell Gallery](https://www.powershellgallery.com/). Then import the Azure Resource Manager modules into the PowerShell session in order to start using the ExpressRoute cmdlets. You need to run PowerShell as an Administrator.
-
-   ```azurepowershell-interactive
-   Install-Module Az
-   ```
-
-   Import all of the Az.\* modules within the known semantic version range.
-
-   ```azurepowershell-interactive
-   Import-Module Az
-   ```
-
-   You can also just import a select module within the known semantic version range.
-
-   ```azurepowershell-interactive
-   Import-Module Az.Network 
-   ```
+1. Sign in and select your subscription.
 
-   Sign in to your account.
+   If you installed PowerShell locally, sign in. If you're using Azure Cloud Shell, you can skip this step.
 
-   ```azurepowershell-interactive
+   ```azurepowershell
    Connect-AzAccount
    ```
 

articles/expressroute/expressroute-nat.md

@@ -5,7 +5,7 @@ services: expressroute
 author: duongau
 ms.service: azure-expressroute
 ms.topic: concept-article
-ms.date: 06/14/2024
+ms.date: 03/12/2026
 ms.author: duau
 ---
 
@@ -17,9 +17,9 @@ Review the [ExpressRoute circuits and routing domains](expressroute-circuit-peer
 
 ## NAT requirements for Microsoft peering
 
-The Microsoft peering path lets you connect to Microsoft cloud services. The list of services includes Microsoft 365 services, such as Exchange Online, SharePoint Online, and Skype for Business. Microsoft expects to support bi-directional connectivity on the Microsoft peering. Traffic destined to Microsoft cloud services must be SNATed to valid public IPv4 addresses before they enter the Microsoft network. Traffic destined to your network from Microsoft cloud services must be SNATed at your Internet edge to prevent [asymmetric routing](expressroute-asymmetric-routing.md). The following figure provides a high-level picture of how the NAT should be set up for Microsoft peering.
+The Microsoft peering path lets you connect to Microsoft cloud services. The list of services includes Microsoft 365 services, such as Exchange Online, SharePoint Online, and Microsoft Teams. Microsoft expects to support bi-directional connectivity on the Microsoft peering. Traffic destined to Microsoft cloud services must be SNATed to valid public IPv4 addresses before they enter the Microsoft network. Traffic destined to your network from Microsoft cloud services must be SNATed at your Internet edge to prevent [asymmetric routing](expressroute-asymmetric-routing.md). The following figure provides a high-level picture of how the NAT should be set up for Microsoft peering.
 
-![High-level diagram of how the NAT should be set up for Microsoft peering.](./media/expressroute-nat/expressroute-nat-microsoft.png) 
+:::image type="content" source="./media/expressroute-nat/expressroute-nat-microsoft.png" alt-text="High-level diagram of how the NAT should be set up for Microsoft peering.":::
 
 ### Traffic originating from your network destined to Microsoft
 
@@ -35,7 +35,7 @@ The Microsoft peering path lets you connect to Microsoft cloud services. The lis
 * Certain scenarios require Microsoft to initiate connectivity to service endpoints hosted within your network. A typical example of the scenario would be connectivity to ADFS servers hosted in your network from Microsoft 365. In such cases, you must leak appropriate prefixes from your network into the Microsoft peering. 
 * You must SNAT Microsoft traffic at the Internet edge for service endpoints within your network to prevent [asymmetric routing](expressroute-asymmetric-routing.md). Requests **and replies** with a destination IP that match a route received from ExpressRoute always go through ExpressRoute. Asymmetric routing exists if the request is received via the Internet with the reply sent via ExpressRoute. SNATing the incoming Microsoft traffic at the Internet edge forces reply traffic back to the Internet edge, resolving the problem.
 
-![Asymmetric routing with ExpressRoute](./media/expressroute-asymmetric-routing/AsymmetricRouting2.png)
+:::image type="content" source="./media/expressroute-asymmetric-routing/AsymmetricRouting2.png" alt-text="Diagram showing asymmetric routing with ExpressRoute.":::
 
 ### NAT IP pool and route advertisements
 

articles/expressroute/how-to-configure-traffic-collector.md

@@ -2,14 +2,13 @@
 title: Configure Traffic Collector for ExpressRoute
 titleSuffix: Azure ExpressRoute
 description: This article shows you how to create an ExpressRoute Traffic Collector resource and import logs into a Log Analytics workspace.
-services: expressroute
 author: duongau
 ms.service: azure-expressroute
 ms.topic: how-to
-ms.date: 06/19/2024
+ms.date: 03/12/2026
 ms.author: duau
 ms.custom: sfi-image-nochange
-#Customer intent: As a network engineer, I want to configure ExpressRoute Traffic Collector to import flow logs into a Log Analytics workspace.
+
 # Customer intent: As a network engineer, I want to configure an ExpressRoute Traffic Collector to import flow logs into a Log Analytics workspace, so that I can effectively monitor and analyze network traffic.
 ---
 
@@ -43,7 +42,7 @@ This article helps you deploy an ExpressRoute Traffic Collector using the Azure
 
 - Minimum of **contributor** access is required in both subscriptions to associate an ExpressRoute Traffic Collector with an ExpressRoute circuit in a different subscription.
 
-For more information, see [Identity and access management](../active-directory/fundamentals/active-directory-ops-guide-iam.md).
+For more information, see [Identity and access management](/entra/architecture/ops-guide-iam).
 
 ## Deploy ExpressRoute Traffic Collector
 

articles/expressroute/howto-routing-cli.md

@@ -1,11 +1,10 @@
 ---
 title: 'Configure peering for Expressroute circuit - Azure CLI'
 description: This article shows you how to create and provision the private, public, and Microsoft peering of an ExpressRoute circuit. This article also shows you how to check the status, update, or delete peerings for your circuit.
-services: expressroute
 author: duongau
 ms.service: azure-expressroute
 ms.topic: how-to
-ms.date: 04/22/2024
+ms.date: 03/12/2026
 ms.author: duau
 ms.custom: devx-track-azurecli
 # Customer intent: As a network engineer, I want to configure private and Microsoft peerings for an ExpressRoute circuit using CLI, so that I can manage high-performance connections between on-premises infrastructure and the cloud.
@@ -19,7 +18,7 @@ This article shows you how to create and manage routing configuration/peering fo
 > * [Azure portal](expressroute-howto-routing-portal-resource-manager.md)
 > * [PowerShell](expressroute-howto-routing-arm.md)
 > * [Azure CLI](howto-routing-cli.md)
-> * [PowerShell (classic)](expressroute-howto-routing-classic.md)
+> * [PowerShell (classic)](/previous-versions/azure/expressroute/expressroute-howto-routing-classic)
 > 
 
 :::image type="content" source="./media/expressroute-howto-routing-portal-resource-manager/expressroute-network.png" alt-text="Diagram showing an on-premises network connected to the Microsoft cloud through an ExpressRoute circuit." lightbox="./media/expressroute-howto-routing-portal-resource-manager/expressroute-network.png":::
@@ -39,7 +38,7 @@ You can configure private peering and Microsoft peering for an ExpressRoute circ
 This section helps you create, get, update, and delete the Microsoft peering configuration for an ExpressRoute circuit.
 
 > [!IMPORTANT]
-> Microsoft peering of ExpressRoute circuits that were configured prior to August 1, 2017 will have all service prefixes advertised through the Microsoft peering, even if route filters are not defined. Microsoft peering of ExpressRoute circuits that are configured on or after August 1, 2017 will not have any prefixes advertised until a route filter is attached to the circuit. For more information, see [Configure a route filter for Microsoft peering](how-to-routefilter-powershell.md).
+> Microsoft peering of ExpressRoute circuits that were configured prior to August 1, 2017 will have all service prefixes advertised through the Microsoft peering, even if route filters are not defined. Microsoft peering of ExpressRoute circuits that are configured on or after August 1, 2017 will not have any prefixes advertised until a route filter is attached to the circuit. For more information, see [Configure a route filter for Microsoft peering](how-to-routefilter-portal.md).
 
 ### To create Microsoft peering
 
@@ -69,15 +68,15 @@ This section helps you create, get, update, and delete the Microsoft peering con
    "allowClassicOperations": false,
    "authorizations": [],
    "circuitProvisioningState": "Enabled",
-   "etag": "W/\"1262c492-ffef-4a63-95a8-a6002736b8c4\"",
+   "etag": "W/\"aaaa0000-bb11-2222-33cc-444444dddddd\"",
    "gatewayManagerEtag": null,
    "id": "/subscriptions/aaaa0a0a-bb1b-cc2c-dd3d-eeeeee4e4e4e/resourceGroups/ExpressRouteResourceGroup/providers/Microsoft.Network/expressRouteCircuits/MyCircuit",
    "location": "westus",
    "name": "MyCircuit",
    "peerings": [],
    "provisioningState": "Succeeded",
    "resourceGroup": "ExpressRouteResourceGroup",
-   "serviceKey": "1d05cf70-1db5-419f-ad86-1ca62c3c125b",
+   "serviceKey": "aaaaaaaa-0b0b-1c1c-2d2d-333333333333",
    "serviceProviderNotes": null,
    "serviceProviderProperties": {
     "bandwidthInMbps": 200,
@@ -91,7 +90,7 @@ This section helps you create, get, update, and delete the Microsoft peering con
     "tier": "Standard"
    },
    "tags": null,
-   "type": "Microsoft.Network/expressRouteCircuits]
+   "type": "Microsoft.Network/expressRouteCircuits"
    ```
 
 4. Configure Microsoft peering for the circuit. Make sure that you have the following information before you continue.
@@ -135,7 +134,7 @@ The output is similar to the following example:
 ```output
 {
   "azureAsn": 12076,
-  "etag": "W/\"2e97be83-a684-4f29-bf3c-96191e270666\"",
+  "etag": "W/\"bbbb1111-cc22-3333-44dd-555555eeeeee\"",
   "gatewayManagerEtag": "18",
   "id": "/subscriptions/bbbb1b1b-cc2c-dd3d-ee4e-ffffff5f5f5f/resourceGroups/ExpressRouteResourceGroup/providers/Microsoft.Network/expressRouteCircuits/MyCircuit/peerings/AzureMicrosoftPeering",
   "lastModifiedBy": "Customer",
@@ -209,15 +208,15 @@ This section helps you create, get, update, and delete the Azure private peering
    "allowClassicOperations": false,
    "authorizations": [],
    "circuitProvisioningState": "Enabled",
-   "etag": "W/\"1262c492-ffef-4a63-95a8-a6002736b8c4\"",
+   "etag": "W/\"aaaa0000-bb11-2222-33cc-444444dddddd\"",
    "gatewayManagerEtag": null,
    "id": "/subscriptions/aaaa0a0a-bb1b-cc2c-dd3d-eeeeee4e4e4e/resourceGroups/ExpressRouteResourceGroup/providers/Microsoft.Network/expressRouteCircuits/MyCircuit",
    "location": "westus",
    "name": "MyCircuit",
    "peerings": [],
    "provisioningState": "Succeeded",
    "resourceGroup": "ExpressRouteResourceGroup",
-   "serviceKey": "1d05cf70-1db5-419f-ad86-1ca62c3c125b",
+   "serviceKey": "aaaaaaaa-0b0b-1c1c-2d2d-333333333333",
    "serviceProviderNotes": null,
    "serviceProviderProperties": {
    "bandwidthInMbps": 200,
@@ -231,7 +230,7 @@ This section helps you create, get, update, and delete the Azure private peering
     "tier": "Standard"
    },
    "tags": null,
-   "type": "Microsoft.Network/expressRouteCircuits]
+   "type": "Microsoft.Network/expressRouteCircuits"
    ```
 
 1. Configure Azure private peering for the circuit. Make sure that you have the following items before you continue with the next steps:

articles/expressroute/provider-rate-limit.md

@@ -2,11 +2,10 @@
 title: About rate limiting for ExpressRoute circuits over service provider ports
 titleSuffix: Azure ExpressRoute
 description: This document discusses how rate limiting works for ExpressRoute circuits over service provider ports. You'll also learn how to monitor the throughput and traffic drop due to rate limiting.
-services: expressroute
 author: duongau
 ms.service: azure-expressroute
 ms.topic: concept-article
-ms.date: 03/01/2024
+ms.date: 03/12/2026
 ms.author: duau
 # Customer intent: As a network administrator, I want to monitor the throughput and traffic drop for my ExpressRoute circuits, so that I can manage rate limiting effectively and ensure optimal performance of the network connection.
 ---

articles/expressroute/rate-limit.md

@@ -2,12 +2,11 @@
 title: Rate limiting for ExpressRoute Direct circuits
 titleSuffix: Azure ExpressRoute
 description: This document provides guidance on how to enable or disable rate limiting for an ExpressRoute Direct circuit.
-services: expressroute
 author: duongau
 ms.service: azure-expressroute
 ms.custom: ignite-2023, ai-usage
 ms.topic: how-to
-ms.date: 03/21/2024
+ms.date: 03/12/2026
 ms.author: duau
 # Customer intent: As a network engineer, I want to enable or disable rate limiting for my ExpressRoute Direct circuits, so that I can manage traffic loads and ensure optimal network performance and stability between my on-premises network and Azure.
 ---
@@ -60,7 +59,7 @@ To enable rate limiting for an existing ExpressRoute Direct circuit, complete th
 
 To disable rate limiting for an existing ExpressRoute Direct circuit, complete the following steps:
 
-1. Sign-in to the Azure portal using this [Azure portal](https://portal.azure.com/?feature.erdirectportratelimit=true) link, then go to the ExpressRoute Direct circuit that you want to configure rate limiting for.
+1. Sign-in to the [Azure portal](https://portal.azure.com/), then go to the ExpressRoute Direct circuit that you want to configure rate limiting for.
 
 1. Select **Configuration** under *Settings* on the left side pane.
 
@@ -130,4 +129,4 @@ To disable rate limiting for an existing ExpressRoute Direct circuit, complete t
 ## Next steps
 
 - For more information regarding ExpressRoute Direct, see [About ExpressRoute Direct](expressroute-erdirect-about.md).
-- For information about setting up ExpressRoute Direct, see [How to configure ExpressRoute Direct](expressroute-howto-erdirect.md).
+- For information about setting up ExpressRoute Direct, see [How to configure ExpressRoute Direct](how-to-expressroute-direct-portal.md).