What Happened on November 12?
On Thursday, November 12, 2026, users of Microsoft 365 services, including Outlook, Teams, Copilot, and SharePoint Online, began experiencing widespread connectivity issues. The problems started in the Americas and quickly spread globally, impacting businesses,
government agencies, schools, and even healthcare providers who rely on Microsoft's cloud infrastructure. Reports showed users were unable to access their email, join meetings, or use various cloud-based applications, grinding productivity to a halt for hours and extending into the next day. Microsoft quickly acknowledged the issue, assigning it incident numbers EX1550543 and MO1550821, and began an urgent investigation.
A 'Domino Effect' of Failing Servers
Initially, Microsoft reported that its infrastructure was experiencing an 'elevated load'. However, the company soon clarified that the problem wasn't a surge in user traffic. Instead, a large number of their servers had become 'unexpectedly unavailable'. This created a domino effect: as servers went offline, the remaining active servers were overwhelmed by the redirected traffic, causing them to fail or become unresponsive. This cascading failure explains why the outage was so widespread and difficult to contain. Microsoft's engineers noted that even when they brought some servers back online, they would often become unresponsive again once they started receiving traffic.
The Likely Culprit: A Faulty Health Check
The technical root of the problem appears to be a failure in Microsoft's automated 'health check' system. In a massive cloud network, automated systems constantly monitor servers to ensure they are working correctly. If a server fails a health check, it is automatically taken out of service to prevent further issues. Microsoft reported that it was testing a configuration change to address a problem causing servers to fail these automated checks and become unavailable. It appears a flawed update or misconfiguration may have caused healthy servers to be incorrectly flagged as faulty, leading to them being unnecessarily removed from the network and triggering the overload on the rest of the system.
Not A Cyberattack, But A Configuration Issue
Microsoft has been clear in its communications that it has found no evidence of malicious activity or a cyberattack being responsible for the outage. The evidence points toward an internal configuration error, a type of issue that has caused major internet disruptions in the past. Experts have noted that a single faulty software update or configuration change can cascade across a global network, leading to widespread service disruptions. Microsoft’s engineers began rolling back a recent network configuration change that was suspected of contributing to the problem while working to stabilize the network.
The Slow Road to Recovery
Fixing a problem of this scale is not as simple as flipping a switch. Engineers had to carefully restart affected servers while managing traffic flow to prevent them from being overwhelmed again. The company reported 'encouraging recovery progress' on Friday, November 13, but noted that service health remained variable and had not returned to normal levels. The incident highlights the immense complexity of modern cloud infrastructure and the profound impact that even small errors can have. It also underscores the global economy's deep reliance on a handful of major technology providers for critical day-to-day operations.
















