Skip to content

Commit f29f12f

Browse files
authored
Merge pull request #313028 from duongau/expressroute-freshness-review-560387-batch2
Expressroute freshness review — batch 2 (8 articles)
2 parents c1b4705 + e8a47ff commit f29f12f

8 files changed

Lines changed: 89 additions & 130 deletions

articles/expressroute/expressroute-config-samples-nat.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,11 +1,10 @@
11
---
22
title: 'Azure ExpressRoute: Router configuration samples - NAT'
33
description: This page provides router configuration samples for Cisco and Juniper routers.
4-
services: expressroute
54
author: duongau
65
ms.service: azure-expressroute
76
ms.topic: concept-article
8-
ms.date: 12/28/2023
7+
ms.date: 03/11/2026
98
ms.author: duau
109
---
1110

articles/expressroute/expressroute-howto-linkvnet-cli.md

Lines changed: 3 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,11 +1,10 @@
11
---
22
title: 'Link a VNet to an ExpressRoute circuit - Azure CLI'
33
description: This article shows you how to link virtual networks (VNets) to ExpressRoute circuits by using the Resource Manager deployment model and Azure CLI.
4-
services: expressroute
54
author: duongau
65
ms.service: azure-expressroute
76
ms.topic: how-to
8-
ms.date: 09/15/2023
7+
ms.date: 03/11/2026
98
ms.author: duau
109
ms.custom: template-tutorial, devx-track-azurecli
1110
---
@@ -17,7 +16,7 @@ This article shows you how to link virtual networks (VNets) to Azure ExpressRout
1716
> * [Azure portal](expressroute-howto-linkvnet-portal-resource-manager.md)
1817
> * [PowerShell](expressroute-howto-linkvnet-arm.md)
1918
> * [Azure CLI](expressroute-howto-linkvnet-cli.md)
20-
> * [PowerShell (classic)](expressroute-howto-linkvnet-classic.md)
19+
> * [PowerShell (classic)](/previous-versions/azure/expressroute/expressroute-howto-linkvnet-classic)
2120
>
2221
2322
:::image type="content" source="./media/expressroute-howto-linkvnet-portal-resource-manager/gateway-circuit.png" alt-text="Diagram showing a virtual network linked to an ExpressRoute circuit." lightbox="./media/expressroute-howto-linkvnet-portal-resource-manager/gateway-circuit.png":::
@@ -61,7 +60,7 @@ Each of the smaller clouds within the large cloud is used to represent subscript
6160
>
6261
>
6362
64-
![Cross-subscription connectivity](./media/expressroute-howto-linkvnet-classic/cross-subscription.png)
63+
:::image type="content" source="./media/expressroute-howto-linkvnet-classic/cross-subscription.png" alt-text="Diagram showing cross-subscription connectivity for ExpressRoute circuits.":::
6564

6665
### Administration - Circuit Owners and Circuit Users
6766

articles/expressroute/expressroute-howto-reset-peering.md

Lines changed: 10 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -1,12 +1,11 @@
11
---
22
title: 'Azure ExpressRoute: Reset circuit peering using Azure PowerShell'
33
description: Learn how to enable and disable peerings for an Azure ExpressRoute circuit using Azure PowerShell.
4-
services: expressroute
54
author: duongau
65
ms.service: azure-expressroute
76
ms.custom: devx-track-azurepowershell
87
ms.topic: how-to
9-
ms.date: 12/28/2023
8+
ms.date: 03/11/2026
109
ms.author: duau
1110
---
1211

@@ -52,8 +51,8 @@ There are a two scenarios where you can find it helpful to reset your ExpressRou
5251
Name : ExpressRouteARMCircuit
5352
ResourceGroupName : ExpressRouteResourceGroup
5453
Location : westus
55-
Id : /subscriptions/########-####-####-####-############/resourceGroups/ExpressRouteResourceGroup/providers/Microsoft.Network/expressRouteCircuits/ExpressRouteARMCircuit
56-
Etag : W/"cd011bef-dc79-49eb-b4c6-81fb6ea5d178"
54+
Id : /subscriptions/aaaa0a0a-bb1b-cc2c-dd3d-eeeeee4e4e4e/resourceGroups/ExpressRouteResourceGroup/providers/Microsoft.Network/expressRouteCircuits/ExpressRouteARMCircuit
55+
Etag : W/"aaaa0000-bb11-2222-33cc-444444dddddd"
5756
ProvisioningState : Succeeded
5857
Sku : {
5958
"Name": "Standard_MeteredData",
@@ -68,12 +67,12 @@ There are a two scenarios where you can find it helpful to reset your ExpressRou
6867
"PeeringLocation": "Los Angeles",
6968
"BandwidthInMbps": 50
7069
}
71-
ServiceKey : ########-####-####-####-############
70+
ServiceKey : aaaa0a0a-bb1b-cc2c-dd3d-eeeeee4e4e4e
7271
Peerings : [
7372
{
7473
"Name": "AzurePrivatePeering",
75-
"Etag": "W/\"cd011bef-dc79-49eb-b4c6-81fb6ea5d178\"",
76-
"Id": "/subscriptions/########-####-####-####-############/resourceGroups/ExpressRouteResourceGroup/providers/Microsoft.Network/expressRouteCircuits/ExpressRouteARMCircuit/peerings/AzurePrivatePeering",
74+
"Etag": "W/\"aaaa0000-bb11-2222-33cc-444444dddddd\"",
75+
"Id": "/subscriptions/aaaa0a0a-bb1b-cc2c-dd3d-eeeeee4e4e4e/resourceGroups/ExpressRouteResourceGroup/providers/Microsoft.Network/expressRouteCircuits/ExpressRouteARMCircuit/peerings/AzurePrivatePeering",
7776
"PeeringType": "AzurePrivatePeering",
7877
"State": "Enabled",
7978
"AzureASN": 12076,
@@ -98,8 +97,8 @@ There are a two scenarios where you can find it helpful to reset your ExpressRou
9897
},
9998
{
10099
"Name": "MicrosoftPeering",
101-
"Etag": "W/\"cd011bef-dc79-49eb-b4c6-81fb6ea5d178\"",
102-
"Id": "/subscriptions/########-####-####-####-############/resourceGroups/ExpressRouteResourceGroup/providers/Microsoft.Network/expressRouteCircuits/ExpressRouteARMCircuit/peerings/MicrosoftPeering",
100+
"Etag": "W/\"aaaa0000-bb11-2222-33cc-444444dddddd\"",
101+
"Id": "/subscriptions/aaaa0a0a-bb1b-cc2c-dd3d-eeeeee4e4e4e/resourceGroups/ExpressRouteResourceGroup/providers/Microsoft.Network/expressRouteCircuits/ExpressRouteARMCircuit/peerings/MicrosoftPeering",
103102
"PeeringType": "MicrosoftPeering",
104103
"State": "Enabled",
105104
"AzureASN": 12076,
@@ -147,5 +146,5 @@ There are a two scenarios where you can find it helpful to reset your ExpressRou
147146

148147
## Next steps
149148
If you need help with troubleshooting an ExpressRoute problem, see the following articles:
150-
* [Verifying ExpressRoute connectivity](expressroute-troubleshooting-expressroute-overview.md)
151-
* [Troubleshooting network performance](expressroute-troubleshooting-network-performance.md)
149+
* [Verifying ExpressRoute connectivity](/troubleshoot/azure/expressroute/expressroute-troubleshooting-expressroute-overview)
150+
* [Troubleshooting network performance](/troubleshoot/azure/expressroute/expressroute-troubleshooting-network-performance)

articles/expressroute/expressroute-qos.md

Lines changed: 5 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,19 +1,18 @@
11
---
22
title: 'Azure ExpressRoute: QoS requirements'
33
description: This page provides detailed requirements for configuring and managing QoS. Skype for Business/voice services are discussed.
4-
services: expressroute
54
author: duongau
65
ms.service: azure-expressroute
76
ms.topic: concept-article
8-
ms.date: 06/30/2023
7+
ms.date: 03/11/2026
98
ms.author: duau
109
---
1110

1211
# ExpressRoute QoS requirements
1312

1413
Skype for Business has various workloads that require differentiated QoS treatment. If you plan to consume voice services through ExpressRoute, you should adhere to the requirements described in this article.
1514

16-
![Diagram that shows the voice services going through ExpressRoute.](./media/expressroute-qos/expressroute-qos.png)
15+
:::image type="content" source="./media/expressroute-qos/expressroute-qos.png" alt-text="Diagram that shows the voice services going through ExpressRoute.":::
1716

1817
> [!NOTE]
1918
> QoS requirements apply to the Microsoft peering only. The DSCP values in your network traffic received on Azure private peering will be kept as is, but they won't be used to prioritize the traffic on Microsoft's network.
@@ -38,6 +37,6 @@ The following table provides a list of DSCP markings used by Microsoft Teams and
3837
* Refer to the requirements for [Routing](expressroute-routing.md) and [NAT](expressroute-nat.md).
3938
* See the following links to configure your ExpressRoute connection.
4039

41-
* [Create an ExpressRoute circuit](expressroute-howto-circuit-classic.md)
42-
* [Configure routing](expressroute-howto-routing-classic.md)
43-
* [Link a VNet to an ExpressRoute circuit](expressroute-howto-linkvnet-classic.md)
40+
* [Create an ExpressRoute circuit](expressroute-howto-circuit-portal-resource-manager.md)
41+
* [Configure routing](expressroute-howto-routing-arm.md)
42+
* [Link a VNet to an ExpressRoute circuit](expressroute-howto-linkvnet-portal-resource-manager.md)

articles/expressroute/how-to-configure-custom-bgp-communities.md

Lines changed: 3 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,12 +1,11 @@
11
---
22
title: 'Configure custom BGP communities for Azure ExpressRoute private peering'
33
description: Learn how to apply or update BGP community value for a new or an existing virtual network.
4-
services: expressroute
54
author: duongau
65
ms.service: azure-expressroute
76
ms.custom: devx-track-azurepowershell
87
ms.topic: how-to
9-
ms.date: 09/05/2023
8+
ms.date: 03/11/2026
109
ms.author: duau
1110
# Customer intent: As a network administrator, I want to configure custom BGP community values for virtual networks, so that I can better manage routing decisions for traffic between my on-premises infrastructure and Azure through ExpressRoute.
1211
---
@@ -112,5 +111,5 @@ BGP communities are groupings of IP prefixes tagged with a community value. This
112111
113112
## Next steps
114113
115-
- [Verify ExpressRoute connectivity](expressroute-troubleshooting-expressroute-overview.md).
116-
- [Troubleshoot your network performance](expressroute-troubleshooting-network-performance.md)
114+
- [Verify ExpressRoute connectivity](/troubleshoot/azure/expressroute/expressroute-troubleshooting-expressroute-overview).
115+
- [Troubleshoot your network performance](/troubleshoot/azure/expressroute/expressroute-troubleshooting-network-performance)

0 commit comments

Comments
 (0)