On October 29, 2025, starting around 16:00 UTC, users and services utilizing Microsoft’s Azure Front Door (AFD) may have encountered delays, timeouts, and errors. The root cause of these disruptions was identified as an unintended configuration modification.

The range of Azure services potentially impacted by this issue included, but was not limited to, App Service, Azure Active Directory B2C, Azure Communication Services, Azure Databricks, Azure Healthcare APIs, Azure Maps, Azure Portal, Azure SQL Database, Azure Virtual Desktop, Container Registry, Media Services, Microsoft Defender External Attack Surface Management, Microsoft Entra ID (covering Mobility Management Policy Service, Identity & Access Management, and User Management UX), Microsoft Purview, Microsoft Sentinel (Threat Intelligence), and Video Indexer.

Currently, the AFD service is functioning with over 98% availability. Most customers and services have either recovered or are seeing significant improvements across the affected areas. Efforts continue to address the remaining issues for the last set of impacted customers and services. Our revised timeline aims for complete resolution by 00:40 UTC on October 30, 2025, and we will provide updates if this goal is achieved ahead of schedule.

The AFD service is now operating above 98% availability. While the majority of customers and services are mitigated or seeing strong improvement across affected regions, we are continuing to work on tail-end recovery for remaining impacted customers and services. We have revised our mitigation time and are currently tracking toward full mitigation by 00:40 UTC on 30 October 2025, though we will communicate if mitigation is achieved sooner.