{
    "api_version": "1",
    "kind": "dse_post",
    "self": "https://update.dsesecurity.com/api/v1/posts/dse-20260917-108-check-provider-metro-support-when-standard-expressroute-resiliency-is-unavailable/",
    "item": {
        "id": "https://update.dsesecurity.com/updates/dse-20260917-108-check-provider-metro-support-when-standard-expressroute-resiliency-is-unavailable/",
        "slug": "dse-20260917-108-check-provider-metro-support-when-standard-expressroute-resiliency-is-unavailable",
        "url": "https://update.dsesecurity.com/updates/dse-20260917-108-check-provider-metro-support-when-standard-expressroute-resiliency-is-unavailable/",
        "alternate_urls": {
            "markdown": "https://update.dsesecurity.com/updates/dse-20260917-108-check-provider-metro-support-when-standard-expressroute-resiliency-is-unavailable.md",
            "json": "https://update.dsesecurity.com/api/v1/posts/dse-20260917-108-check-provider-metro-support-when-standard-expressroute-resiliency-is-unavailable/"
        },
        "title": "Check provider Metro support when Standard ExpressRoute resiliency is unavailable",
        "summary": "The selected provider and location can constrain which resiliency option is offered.",
        "format": {
            "slug": "guide",
            "name": "Guide"
        },
        "priority": {
            "slug": "info",
            "name": "Information"
        },
        "featured": false,
        "image": {
            "theme": "network-infrastructure",
            "label": "Networks & infrastructure",
            "alt": "Resilient network core with engineered blue and gold data paths.",
            "card_url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-card.webp?v=1.8.20",
            "hero_url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-hero.webp?v=1.8.20",
            "social_url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-social-v2.jpg?v=1.8.20",
            "width": 2400,
            "height": 1350
        },
        "topics": [
            {
                "slug": "cybersecurity",
                "name": "Cybersecurity",
                "url": "https://update.dsesecurity.com/topic/cybersecurity/"
            },
            {
                "slug": "networks-infrastructure",
                "name": "Networks & Infrastructure",
                "url": "https://update.dsesecurity.com/topic/networks-infrastructure/"
            }
        ],
        "author": {
            "name": "DSE Security Editorial Team",
            "url": "https://update.dsesecurity.com/#editorial-team",
            "type": "Organization"
        },
        "publisher": {
            "name": "Detection Systems & Engineering",
            "url": "https://dsesecurity.com/"
        },
        "published_at": "2026-09-17T16:33:12+00:00",
        "modified_at": "2026-09-17T16:42:35+00:00",
        "reviewed_on": "2026-09-17",
        "reading_minutes": 1,
        "word_count": 206,
        "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.",
        "primary_source": {
            "name": "Design and architect Azure ExpressRoute for resiliency | Microsoft Learn",
            "url": "https://learn.microsoft.com/en-us/azure/expressroute/design-architecture-for-resiliency",
            "published_on": null,
            "authority": "Microsoft Learn"
        },
        "publishing_principles": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/",
        "usage_info": "https://update.dsesecurity.com/usage/",
        "copyright_notice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.",
        "content_html": "<h2>Source facts</h2>\n<p>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&#8217;s connections between two sites in the same metropolitan area. Maximum resiliency instead uses a pair of circuits across distinct locations. <a href=\"https://learn.microsoft.com/en-us/azure/expressroute/design-architecture-for-resiliency\" target=\"_blank\" rel=\"noopener noreferrer\">Microsoft Learn</a>.</p>\n<h2>Applicability</h2>\n<p>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.</p>\n<h2>DSE recommendation</h2>\n<p>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.</p>\n<h2>Verification</h2>\n<p>Compare the provider&#8217;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.</p>\n<h2>Official references</h2>\n<p><a href=\"https://learn.microsoft.com/en-us/azure/expressroute/design-architecture-for-resiliency\" target=\"_blank\" rel=\"noopener noreferrer\">Microsoft Learn: Design and architect Azure ExpressRoute for resiliency</a>.</p>",
        "content_text": "Source facts\nMicrosoft 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.\nApplicability\nApply 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.\nDSE recommendation\nDSE 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.\nVerification\nCompare 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.\nOfficial references\nMicrosoft Learn: Design and architect Azure ExpressRoute for resiliency.",
        "content_markdown": "## Source facts\n\nMicrosoft 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).\n\n## Applicability\n\nApply 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.\n\n## DSE recommendation\n\nDSE 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.\n\n## Verification\n\nCompare 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.\n\n## Official references\n\n[Microsoft Learn: Design and architect Azure ExpressRoute for resiliency](https://learn.microsoft.com/en-us/azure/expressroute/design-architecture-for-resiliency)."
    },
    "json_ld": {
        "@context": "https://schema.org",
        "@graph": [
            {
                "@type": "Organization",
                "@id": "https://dsesecurity.com/#organization",
                "name": "Detection Systems & Engineering",
                "alternateName": "DSE Security",
                "url": "https://dsesecurity.com/",
                "logo": {
                    "@type": "ImageObject",
                    "url": "https://update.dsesecurity.com/assets/dse-logo-20260812.png?v=1.8.20"
                }
            },
            {
                "@type": "Organization",
                "@id": "https://update.dsesecurity.com/#editorial-team",
                "name": "DSE Security Editorial Team",
                "url": "https://update.dsesecurity.com/",
                "parentOrganization": {
                    "@id": "https://dsesecurity.com/#organization"
                }
            },
            {
                "@type": "WebSite",
                "@id": "https://update.dsesecurity.com/#website",
                "name": "DSE Updates",
                "alternateName": "DSE Security Knowledge Hub",
                "url": "https://update.dsesecurity.com/",
                "inLanguage": "en-US",
                "publisher": {
                    "@id": "https://dsesecurity.com/#organization"
                },
                "potentialAction": {
                    "@type": "SearchAction",
                    "target": {
                        "@type": "EntryPoint",
                        "urlTemplate": "https://update.dsesecurity.com/?q={search_term_string}"
                    },
                    "query-input": "required name=search_term_string"
                }
            },
            {
                "@type": "WebPage",
                "@id": "https://update.dsesecurity.com/updates/dse-20260917-108-check-provider-metro-support-when-standard-expressroute-resiliency-is-unavailable/",
                "url": "https://update.dsesecurity.com/updates/dse-20260917-108-check-provider-metro-support-when-standard-expressroute-resiliency-is-unavailable/",
                "isPartOf": {
                    "@id": "https://update.dsesecurity.com/#website"
                },
                "lastReviewed": "2026-09-17"
            },
            {
                "@type": "BreadcrumbList",
                "@id": "https://update.dsesecurity.com/updates/dse-20260917-108-check-provider-metro-support-when-standard-expressroute-resiliency-is-unavailable/#breadcrumbs",
                "itemListElement": [
                    {
                        "@type": "ListItem",
                        "position": 1,
                        "name": "DSE Updates",
                        "item": "https://update.dsesecurity.com/"
                    },
                    {
                        "@type": "ListItem",
                        "position": 2,
                        "name": "Check provider Metro support when Standard ExpressRoute resiliency is unavailable",
                        "item": "https://update.dsesecurity.com/updates/dse-20260917-108-check-provider-metro-support-when-standard-expressroute-resiliency-is-unavailable/"
                    }
                ]
            },
            {
                "@type": [
                    "Article",
                    "TechArticle"
                ],
                "@id": "https://update.dsesecurity.com/updates/dse-20260917-108-check-provider-metro-support-when-standard-expressroute-resiliency-is-unavailable/#article",
                "identifier": "https://update.dsesecurity.com/updates/dse-20260917-108-check-provider-metro-support-when-standard-expressroute-resiliency-is-unavailable/",
                "url": "https://update.dsesecurity.com/updates/dse-20260917-108-check-provider-metro-support-when-standard-expressroute-resiliency-is-unavailable/",
                "headline": "Check provider Metro support when Standard ExpressRoute resiliency is unavailable",
                "description": "The selected provider and location can constrain which resiliency option is offered.",
                "abstract": "The selected provider and location can constrain which resiliency option is offered.",
                "articleBody": "Source facts\nMicrosoft 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.\nApplicability\nApply 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.\nDSE recommendation\nDSE 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.\nVerification\nCompare 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.\nOfficial references\nMicrosoft Learn: Design and architect Azure ExpressRoute for resiliency.",
                "datePublished": "2026-09-17T16:33:12+00:00",
                "dateModified": "2026-09-17T16:42:35+00:00",
                "mainEntityOfPage": {
                    "@id": "https://update.dsesecurity.com/updates/dse-20260917-108-check-provider-metro-support-when-standard-expressroute-resiliency-is-unavailable/"
                },
                "inLanguage": "en-US",
                "isAccessibleForFree": true,
                "author": {
                    "@type": "Organization",
                    "name": "DSE Security Editorial Team",
                    "url": "https://update.dsesecurity.com/#editorial-team"
                },
                "publisher": {
                    "@id": "https://dsesecurity.com/#organization"
                },
                "image": {
                    "@type": "ImageObject",
                    "@id": "https://update.dsesecurity.com/updates/dse-20260917-108-check-provider-metro-support-when-standard-expressroute-resiliency-is-unavailable/#primaryimage",
                    "url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-social-v2.jpg?v=1.8.20",
                    "contentUrl": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-social-v2.jpg?v=1.8.20",
                    "width": 1200,
                    "height": 630,
                    "caption": "Check provider Metro support when Standard ExpressRoute resiliency is unavailable"
                },
                "articleSection": [
                    "Cybersecurity",
                    "Networks & Infrastructure"
                ],
                "keywords": [
                    "Cybersecurity",
                    "Networks & Infrastructure",
                    "Guide",
                    "Information priority"
                ],
                "genre": "Guide",
                "about": [
                    {
                        "@type": "Thing",
                        "name": "Cybersecurity",
                        "url": "https://update.dsesecurity.com/topic/cybersecurity/"
                    },
                    {
                        "@type": "Thing",
                        "name": "Networks & Infrastructure",
                        "url": "https://update.dsesecurity.com/topic/networks-infrastructure/"
                    }
                ],
                "wordCount": 206,
                "timeRequired": "PT1M",
                "publishingPrinciples": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/",
                "usageInfo": "https://update.dsesecurity.com/usage/",
                "copyrightHolder": {
                    "@id": "https://dsesecurity.com/#organization"
                },
                "copyrightNotice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.",
                "citation": {
                    "@type": "CreativeWork",
                    "name": "Design and architect Azure ExpressRoute for resiliency | Microsoft Learn",
                    "url": "https://learn.microsoft.com/en-us/azure/expressroute/design-architecture-for-resiliency"
                }
            }
        ]
    }
}