Skip to content

Commit 630e183

Browse files
Merge pull request #279062 from duongau/patch-2
ExpressRoute - Evaluate circuit resiliency (update section name to reflect section)
2 parents c612366 + f7ee48b commit 630e183

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/expressroute/evaluate-circuit-resiliency.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ services: expressroute
55
author: duongau
66
ms.service: expressroute
77
ms.topic: how-to
8-
ms.date: 03/22/2024
8+
ms.date: 06/24/2024
99
ms.author: duau
1010
ms.custom: ai-usage
1111
---
@@ -30,7 +30,7 @@ Circuits configured for maximum resiliency provide both site (peering location)
3030

3131
:::image type="content" source=".\media\evaluate-circuit-resiliency\route-table.png" alt-text="Screenshot of the route table for an ExpressRoute private peering.":::
3232

33-
## Initiate a manual failover for an ExpressRoute circuit
33+
## Initiate ExpressRoute circuit manual failover
3434

3535
> [!NOTE]
3636
> The following procedure outlined will result in the disconnection of both redundant connections of the ExpressRoute circuit. Therefore, it's important that you do this test during scheduled maintenance windows or during off-peak hours. You should also ensure that a redundant circuit is available to provide connectivity to your on-premises network.

0 commit comments

Comments
 (0)