Microsoft 365 Outage

Between 15:45 UTC on 29 October and 00:05 UTC on 30 October 2025, customers and Microsoft services leveraging Azure Front Door (AFD) may have experienced latencies, timeouts, and errors.

Affected Azure services include, but are 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 Copilot for Security, Microsoft Defender External Attack Surface Management, Microsoft Entra ID (Mobility Management Policy Service, Identity & Access Management, and User Management UX), Microsoft Purview, Microsoft Sentinel (Threat Intelligence), and Video Indexer.

Customer configuration changes to AFD remain temporarily blocked. We will notify customers once this block has been lifted. While error rates and latency are back to pre-incident levels, a small number of customers may still be seeing issues and we are still working to mitigate this long tail. Updates will be provided directly via Azure Service Health.

What went wrong and why?

An inadvertent tenant configuration change within Azure Front Door (AFD) triggered a widespread service disruption affecting both Microsoft services and customer applications dependent on AFD for global content delivery. The change introduced an invalid or inconsistent configuration state that caused a significant number of AFD nodes to fail to load properly, leading to increased latencies, timeouts, and connection errors for downstream services.

As unhealthy nodes dropped out of the global pool, traffic distribution across healthy nodes became imbalanced, amplifying the impact and causing intermittent availability even for regions that were partially healthy. We immediately blocked all further configuration changes to prevent additional propagation of the faulty state and began deploying a ‘last known good’ configuration across the global fleet. Recovery required reloading configurations across a large number of nodes and rebalancing traffic gradually to avoid overload conditions as nodes returned to service. This deliberate, phased recovery was necessary to stabilize the system while restoring scale and ensuring no recurrence of the issue.

The trigger was traced to a faulty tenant configuration deployment process. Our protection mechanisms, to validate and block any erroneous deployments, failed due to a software defect which allowed the deployment to bypass safety validations. Safeguards have since been reviewed and additional validation and rollback controls have been immediately implemented to prevent similar issues in the future.

Microsoft Update:

User impact: Users may see issues accessing some Microsoft 365 services and portals.

More info: We've edited the Title, User impact, and More info sections of this communication to align with our current understanding of the affected scenarios.

Impacted scenarios include, but may not be limited to the following:

• Access to some Microsoft Entra, Microsoft Purview, Microsoft Defender, Microsoft Power Apps and Microsoft Intune functions. For example, Microsoft Defender for Cloud Apps policies may not be applying as expected.
• Access to security.microsoft.com, learn.microsoft.com, and other portals accessed through microsoft.com.
• Issues with add-ins and network connectivity in Outlook.
• Degraded functionality to some workflows within Microsoft Teams, including impact to location data in support of emergency calls.

Current status: We're deploying a previous healthy configuration to the affected portions of infrastructure to resolve this issue. This is being done in tandem with efforts to rebalance traffic across healthy infrastructure to achieve recovery as quickly as possible.

Scope of impact: Any users attempting to access Microsoft 365 services, such as those detailed in the more info section above, may be impacted. This information may be updated as our investigation continues.

Start time: Wednesday, October 29, 2025, 3:49 PM UTC

Preliminary root cause: A problematic configuration change was applied to a portion of Azure infrastructure.

https://status.cloud.microsoft/

Current update from Microsoft

We've identified a recent configuration change to a portion of Azure infrastructure which we believe is causing the impact. We're pursuing multiple remediation strategies, including moving traffic away from the impacted infrastructure and blocking the offending change. We'll provide an estimated recovery time as soon as possible.

Scope of impact: Any users attempting to access Microsoft 365 services, such as those detailed in the more info section above, may be impacted. This information may be updated as our investigation continues.

https://status.cloud.microsoft/

Microsoft is currently investigating an ongoing incident that is preventing some customers from accessing Microsoft 365 applications. This widespread Microsoft outage is impacting our ability to deliver certain support functions, including email, Teams, SharePoint, OneDrive, and other Microsoft 365 services.

We are actively monitoring Microsoft’s service health, and will update accordingly.

https://status.cloud.microsoft/

We appreciate your patience