Azure Proactive Resiliency Library v2
Tools Glossary GitHub GitHub Issues Toggle Dark/Light/Auto mode Toggle Dark/Light/Auto mode Toggle Dark/Light/Auto mode Back to homepage

expressRouteCircuits

Summary

RecommendationImpactCategoryAutomation AvailableIn Azure Advisor
Connect on-prem networks to Azure critical workloads via multiple ExpressRoutesHighHigh AvailabilityNoNo
Ensure ExpressRoute's physical links connect to distinct network edge devicesHighHigh AvailabilityNoNo
Ensure both connections of an ExpressRoute circuit are configured in active-active modeHighHigh AvailabilityNoNo
Activate Bidirectional Forwarding Detection on edge devices for faster failoverHighHigh AvailabilityNoNo
Configure monitoring and alerting for ExpressRoute circuitsHighMonitoring and AlertingNoNo
Configure service health to receive ExpressRoute circuit maintenance notificationHighMonitoring and AlertingNoNo
Implement rate-limiting across ExpressRoute Direct Circuits to optimize network flowMediumScalabilityYesNo

Details


Connect on-prem networks to Azure critical workloads via multiple ExpressRoutes

Impact:  High Category:  High Availability

APRL GUID:  4d703025-dafc-f840-a183-5dc440456134

Description:

Connecting each ExpressRoute Gateway to a minimum of two circuits in different peering locations enhances redundancy and reliability by ensuring alternate pathways for data in case one circuit fails.

Potential Benefits:

Enhanced reliability and redundancy
Learn More:
Designing for disaster recovery with ExpressRoute private peering

ARG Query:

Click the Azure Resource Graph tab to view the query

// cannot-be-validated-with-arg