- A major Microsoft 365 cloud services outage began around 18:00 UTC on November 12 and has extended beyond 15 hours.
- The incident is attributed to a core process on affected servers becoming “overwhelmed,” leading to failed health checks and capacity loss.
- Key services impacted include Exchange Online, Teams, Copilot 365, Defender for Office 365, Intune, and various administrative tools.
Microsoft 365 Outage: An Ongoing Challenge
A significant outage affecting Microsoft 365 cloud services, which commenced around 18:00 UTC on November 12, continues to severely disrupt operations for users globally. The incident, dubbed the “Microsoft long weekend” in Australia, has rendered core services such as Exchange Online, Teams, Copilot 365, and Defender for Office 365 unavailable. Furthermore, administrators are unable to access critical management tools like Intune and the Microsoft 365 Apps Admin Center, complicating recovery efforts.
Microsoft initially attributed the problem to a “problem that’s causing servers to fail automated health checks and become unavailable.” Subsequent investigations have indicated that “a core process on the affected servers is becoming overwhelmed, which causes the servers to stop responding and contributes to the capacity loss.”
Chronology of Events and Mitigation Attempts
Microsoft’s efforts to restore services have not yet yielded the anticipated relief. While the company initially reported validating an alternative service health check method that allowed a “subset of affected servers to successfully return to service,” subsequent updates highlight ongoing difficulties:
- Applying infrastructure capacity improvements in affected regions.
- Monitoring changes that are “not taking as expected.”
- Reviewing traffic flows and infrastructure to optimize routing.
- Identifying alternate workstreams to increase capacity.
- Observing partial recovery in some regions, but without sustained stability.
- Encountering issues with virtual machines getting “stuck in a bad state” during scaling efforts.
As of the latest updates, Microsoft has not provided a definitive timeline for full service restoration. The company is “continuing to pursue multiple workstreams to pinpoint the underlying cause of the traffic influx and advance the recoverability of the backend servers.”
No Evidence of Malicious Activity
Early in the incident, Microsoft clarified its stance on a potential cyberattack. Initially stating “no indication this is the result of malicious activity,” the company later updated to “As of now, we are not aware of any malicious activity that is causing this incident” at 05:46 UTC. This suggests that Microsoft has ruled out a cyberattack as the cause, focusing instead on internal technical infrastructure issues. PROSTO24 has previously covered similar service disruptions impacting Microsoft.
Affected Services and Global Impact
The outage impacts a wide array of Microsoft 365 services that rely on Exchange Online and email functionalities. Key affected services include:
| Service | Description |
|---|---|
| Exchange Online | Primary email service |
| Teams | Collaboration platform |
| Copilot 365 | AI assistant |
| Defender for Office 365 | Threat protection |
| Intune | Endpoint management |
| Microsoft 365 Apps Admin Center | Admin console |
| SharePoint Online | Collaboration service |
| Windows 365 | Cloud PCs |
| Fabric, Graph, Planner, Power Apps, Purview, To Do, Universal Print | Other cloud services |
Reports indicate significant disruption to daily operations across various countries, including parts of the UK government and the National Health Service (NHS), which experienced problems sending and receiving emails and accessing online patient consultations.
The prolonged Microsoft 365 outage underscores the inherent risks of centralizing critical business functions within a single cloud ecosystem. For organizations and governments, this incident highlights the imperative for robust disaster recovery plans and potentially diversified solutions to ensure operational continuity, especially for essential communications like email. The lack of a clear timeline for full restoration also points to the complexity of the underlying issues Microsoft is facing, suggesting that more resilient and distributed strategies might be necessary to mitigate the impact of such large-scale incidents in the future.
The prolonged Microsoft 365 outage, attributed to an overwhelmed core process, highlights critical architectural vulnerabilities in large-scale distributed systems. The inability to quickly stabilize capacity and the observed ‘stuck’ VM states during scaling indicate deeper issues beyond transient traffic influx, potentially related to resource orchestration or state management within their hypervisor layer. This incident will undoubtedly prompt enterprises to re-evaluate their cloud redundancy strategies and multi-cloud commitments, given the substantial operational impact across core business functions like Exchange Online and Teams.