Azure Front Door outage: a valid customer change exposes a latent bug at the edge

A customer configuration change produced metadata that crashed Azure Front Door's edge servers, causing timeouts and DNS failures for Azure, Microsoft 365 and many customer sites for about eight hours.

ResolvedEnded Oct 30, 2025
Security:
No determination
Started
Oct 29, 2025, 15:41 UTC
Impact mitigated
Oct 30, 2025, 00:05 UTC
Duration
8 h 24 min
Full recovery
Complete
Geographic scope
Global
Last verified
2 sources

What happened

Systems and services affected
Azure Front DoorAzure CDNAzure PortalAzure App ServiceAzure SQL DatabaseMicrosoft Entra IDMicrosoft 365Dynamics 365Power Platform
Kind of failure
Software defect
Sector
Cloud infrastructure
Provider report
Published
Provider incident IDs
YKYN-BWZ
Status and recovery
Resolved. Microsoft confirmed impact mitigated at 00:05 UTC on October 30, after restoring a cleaned configuration to all edge sites and rebalancing traffic.[1]

What caused it?

Root cause: Confirmed

A valid customer configuration change produced incompatible metadata that "exposed a latent bug in the data plane" during asynchronous processing. Edge servers crashed, which also affected Front Door's internal DNS service. Microsoft also cites a gap in pre-production validation.[1]

Provider report: Published. Microsoft published a post-incident review under tracking ID YKYN-BWZ, with repair items running into 2026.[1]

Was it malicious?

No determination

Microsoft attributes the incident to a latent software defect triggered by a valid customer configuration. Its review does not describe malicious activity.[1]

How the failure happened

  1. 1TriggerValid customer configuration change
  2. 2FailureIncompatible metadata hit a latent bug
  3. 3SpreadEdge servers crashed
  4. Affected9 services and systems

Evidence for each step

  1. 1
    Valid customer configuration change[1]
    Starting point.
  2. 2
    Incompatible metadata hit a latent bug. In the data plane, during asynchronous processing[1]
    Led from step 1: Stated in a provider report or official record.
  3. 3
    Edge servers crashed. Front Door's internal DNS service was also affected[1]
    Led from step 2: Stated in a provider report or official record.

Only steps the sources state are drawn. Affected services are listed under What happened.

Explanation

Both versions summarize the sourced claims on this page. Our own interpretation appears only under Independent analysis.

Plain language: what happened and why people were affected.

On October 29, 2025, many websites and Microsoft services that sit behind Azure Front Door, Microsoft's global system for routing web traffic, timed out or could not be found for about eight hours.

A customer made an ordinary settings change. The way Front Door processed it set off a hidden bug in its edge servers around the world, and they crashed.

Microsoft stopped all customer changes from going out, removed the problem settings from its last known-good configuration, pushed that to every edge site, and rebalanced traffic.

Confirmed and unknown

Confirmed

  • Confirmed
    A valid customer configuration change produced metadata that exposed a latent bug in the data plane, crashing edge servers.[1]
    Said by: Microsoft · Evidence: Official
  • Confirmed
    The crash happened after the metadata passed protection safeguards; safeguards were not bypassed in this incident.[1]
    Said by: Microsoft · Evidence: Official
  • Confirmed
    Impact ran from 15:41 UTC on October 29 to 00:05 UTC on October 30.[1]
    Said by: Microsoft · Evidence: Official
  • Confirmed
    Microsoft 365, Dynamics 365, Power Platform and Entra ID were affected, as was customers' ability to open support cases.[1]
    Said by: Microsoft · Evidence: Official

Still unknown

No open questions: the provider has published a full account.

Timeline

Times in UTC. Dates without a time mean the sources give no time. Only events a source documents are listed.

  1. First observedOct 29, 2025, 15:41 UTC
  2. AcknowledgedOct 29, 2025, 17:30 UTC
  3. MitigationOct 29, 2025, 17:40 UTC
  4. RecoveryOct 29, 2025, 18:30 UTC
  5. ResolvedOct 30, 2025, 00:05 UTC
  6. Incident reportPublished, date not shown
Oct 29, 2025, 15:41 UTCOct 30, 2025, 00:05 UTC
  1. First observed
    Edge servers begin crashing; timeouts and DNS failures start.[1]
  2. Acknowledged
    Microsoft blocks all customer configuration propagation.[1]
  3. Mitigation
    Deployment of a cleaned known-good configuration begins.[1]
  4. Recovery
    AFD DNS servers recover; traffic manually rebalanced to healthy edge sites.[1]
  5. Automatic traffic management resumes.[1]
  6. Resolved
    Impact confirmed mitigated.[1]
  7. Start to: Impact mitigated8 h 24 min

Related incidents

Links stated by providers or officials carry their evidence label. “Similar failure” is a comparison of documented causes, not a causal link.

Evidence and sources

Grouped by type of evidence. Numbers match the citations above.

Primary: provider and official sources

Published by the provider or agency itself: incident reports, status records, advisories, statements.

  1. 1.
    Post Incident Review (PIR): Azure Front Door, Connectivity issues across multiple regions (YKYN-BWZ) (opens in a new tab)
    Microsoft Azure · Provider report · Published · Accessed
    Listed as 10/29/2025; the text describes actions through November 5, 2025.
  2. 2.
    Cloudflare outage on November 18, 2025 (opens in a new tab)
    Cloudflare · Provider report · Published · Accessed

Last verified against these sources on Nov 14, 2026.