What Exactly Happened?
The problems began around midday on the US East Coast, which was late evening in Europe and the start of the business day in parts of Asia. Users suddenly found they couldn't access their email on Outlook, join meetings on Teams, or use a host of other
connected Microsoft 365 services. Outage trackers like Downdetector saw a massive spike in reports, with over 130,000 complaints about Outlook alone, though this figure likely understated the full scope of the issue. The disruption was global, affecting businesses, schools, and government agencies in at least 74 countries.
Which Services Were Affected?
The outage was centred on Exchange Online, Microsoft's cloud-based service that powers email, calendars, and contacts. Because so many other Microsoft 365 applications are integrated with it, the failure had a cascading effect. The list of impacted services included Outlook, Microsoft Teams, SharePoint Online, OneDrive, and even the AI assistant Copilot. The disruption was so severe that it affected everything from court proceedings and hospital communications to airline customer service and corporate earnings calls. Some organisations reportedly reverted to using fax machines to communicate.
The Technical Root Cause
Microsoft quickly ruled out any malicious or cyberattack activity. The preliminary investigation pointed to an internal failure. In its status updates, the company explained that the issue was not caused by a surge in user traffic but by a large number of its own servers becoming 'unexpectedly unavailable'. This placed an extreme load on the remaining infrastructure, causing a core process responsible for establishing secure connections to become overwhelmed. In simple terms, think of it as a significant portion of a call centre's staff suddenly vanishing, forcing the few remaining operators to handle an impossible number of calls, leading to the entire system freezing up. The initial fixes did not provide the expected relief, prolonging the outage as engineers scrambled to find a stable solution.
A Ripple Effect on Global Business
The outage served as a stark reminder of the global economy's deep dependence on cloud infrastructure. For more than 18 hours, productivity for millions of workers plummeted. Businesses couldn't send emails, trading firms faced communication delays, and remote workforces were left unable to collaborate. The financial impact is hard to calculate but grows with every minute of downtime, encompassing lost productivity, interrupted transactions, and delayed decisions. In one clear example, US electric truck maker Workhorse Group had to postpone its quarterly earnings call due to the disruption. The event has also sparked broader conversations about the risks of single-vendor cloud concentration.
Microsoft's Response and The Path to Recovery
Microsoft's engineers worked through the night to resolve the issue, providing regular updates via their social media channels as their own service status page was initially impacted. The recovery was a gradual and delicate process. At first, attempts to bring servers back online failed as they were immediately swamped with traffic and became unresponsive again. Engineers had to reroute traffic and apply a patch to a component that handles sign-ins and routing. By the morning of November 13, Microsoft reported seeing 'encouraging recovery progress' across North America, Europe, and Asia, though intermittent issues and email backlogs persisted as the system slowly returned to normal. The company promised a full post-incident report to explain the root cause in detail once services were fully restored.
