A major global outage in Microsoft 365 services on 12–13 November 2026 left millions unable to access Outlook email, Teams meetings, and Copilot AI tools. The disruption, lasting more than 24 hours, impacted government agencies, healthcare providers, financial institutions, and tech companies across at least 74 countries. Microsoft confirmed the incident stemmed from a technical fault during a network capacity upgrade, not a cyberattack, and has since restored most services.
What failed and when
The outage began around noon ET on 12 November, initially affecting users in the Americas before spreading globally. According to Microsoft, a network change following a capacity upgrade caused a cascading failure, rendering a large number of servers unexpectedly unavailable due to elevated load. Services impacted included Exchange Online (Outlook), Teams, Microsoft Copilot, Defender security features, Intune management dashboards, and cloud-hosted Windows environments. Some users could not send or receive emails, join scheduled meetings, or access shared documents. OpenAI reported issues with Microsoft connectors affecting ChatGPT, while Anthropic users saw disruptions to Claude AI.
Scale and economic impact
Downdetector recorded outage reports across 74 countries within an hour. UK police forces including Merseyside, Greater Manchester, Bedfordshire, Thames Valley, and Cumbria advised the public to report crimes via telephone due to disabled online forms. In the US, city governments in Jacksonville, Austin, and Dallas reported email disruptions, while Arapahoe County’s sheriff’s office cited delays in processing bail payments. Japanese civil servants reverted to printing physical documents, and Australian schools, courts, and government services faced operational delays. The Anderson Economic Group estimated lost productivity could reach $7 billion, with 26 million users affected on the first day and 51 million on the second. Microsoft may face up to $800 million in daily subscription refunds, though not all customers will claim them.
Technical cause and recovery
Microsoft stated the root cause was a technical issue unrelated to cybersecurity or AI systems. The company acknowledged that early mitigation attempts failed to produce expected results, prolonging the outage. Engineers observed uneven recovery: North America rebounded faster, while Europe and Asia saw slower progress. By the morning of 13 November, Microsoft reported that email queues were significantly reduced and service stability was improving. A full post-incident report is expected, detailing the failure chain and preventive measures. This marks the second major Microsoft cloud disruption in 2026, following a September outage tied to authentication configuration errors.
What it means
For businesses relying on Microsoft 365, this outage underscores systemic risk in single-vendor cloud dependency. Even with high uptime SLAs, cascading infrastructure failures can halt operations globally. Organisations in the UK, UAE, US, and Kazakhstan should assess multi-vendor strategies or offline contingency plans, particularly for mission-critical functions like emergency response or financial processing. While cybersecurity insurance may cover some costs, it transfers rather than eliminates risk. The repeated nature of such outages suggests Microsoft’s resilience mechanisms need deeper scrutiny.
The incident highlights the fragility of modern digital infrastructure, where a routine network upgrade can trigger worldwide disruption. For IT leaders, the priority is no longer just adoption speed but resilience design — including data control, service redundancy, and clear exit strategies from dominant providers.