# Check provider Metro support when Standard ExpressRoute resiliency is unavailable

> The selected provider and location can constrain which resiliency option is offered.

- Canonical URL: https://update.dsesecurity.com/updates/dse-20260917-108-check-provider-metro-support-when-standard-expressroute-resiliency-is-unavailable/
- Publisher: Detection Systems & Engineering (DSE Security)
- Author: DSE Security Editorial Team
- Published: 2026-09-17T16:33:12+00:00
- Modified: 2026-09-17T16:42:35+00:00
- Last reviewed by DSE: 2026-09-17
- Resource type: Guide
- DSE priority: Information
- Topics: Cybersecurity, Networks & Infrastructure
- Reading time: 1 minutes

## What you need to know

The selected provider and location can constrain which resiliency option is offered.

## Potentially affected

Apply this check when preparing a new circuit order and the expected Standard option is unavailable. Record the selected provider, peering location and business requirement before diagnosing the selection as a deployment failure.

## DSE recommendation

DSE recommends asking the provider to confirm the supported resiliency offering for that location before changing permissions or retrying an unchanged order.

## Article

## Source facts

Microsoft states that new Standard-resiliency ExpressRoute circuits cannot be deployed in some locations when the chosen provider supports High resiliency, also called ExpressRoute Metro. Metro divides a single circuit’s connections between two sites in the same metropolitan area. Maximum resiliency instead uses a pair of circuits across distinct locations. [Microsoft Learn](https://learn.microsoft.com/en-us/azure/expressroute/design-architecture-for-resiliency).

## Applicability

Apply this check when preparing a new circuit order and the expected Standard option is unavailable. Record the selected provider, peering location and business requirement before diagnosing the selection as a deployment failure.

## DSE recommendation

DSE recommends asking the provider to confirm the supported resiliency offering for that location before changing permissions or retrying an unchanged order. Match the offered circuit structure with the approved design, and update the procurement and implementation records together. If the requirement calls for Maximum resiliency, resolve the second circuit and location explicitly rather than treating the Metro label as sufficient.

## Verification

Compare the provider’s current offering and the saved deployment parameters with the intended resiliency design. Confirm the circuit count and named locations in the approved order. Record unresolved availability questions before scheduling installation, and check the provisioned circuit identities against the order at handoff.

## Official references

[Microsoft Learn: Design and architect Azure ExpressRoute for resiliency](https://learn.microsoft.com/en-us/azure/expressroute/design-architecture-for-resiliency).

## Primary reference

- Name: Design and architect Azure ExpressRoute for resiliency | Microsoft Learn
- Authority: Microsoft Learn
- URL: https://learn.microsoft.com/en-us/azure/expressroute/design-architecture-for-resiliency
- Source publication date: Not stated by the source

## Citation and use

Preferred citation: “Check provider Metro support when Standard ExpressRoute resiliency is unavailable,” DSE Security, https://update.dsesecurity.com/updates/dse-20260917-108-check-provider-metro-support-when-standard-expressroute-resiliency-is-unavailable/
Publishing principles: https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/
Usage and citation policy: https://update.dsesecurity.com/usage/
Copyright © 2026 Detection Systems & Engineering. All rights reserved.