What Exactly Happened?
On the evening of Thursday, November 12, 2026, users across the world began reporting issues with Microsoft 365 services. The problems started in the Americas and quickly spread globally, with the disruption lasting for nearly 24 hours for many. The core
of the issue was traced to Exchange Online, the service that powers Outlook email. This initial failure created a domino effect, taking down or degrading a host of connected applications. Microsoft acknowledged the issue and confirmed it was not the result of any malicious activity or cyberattack. By the morning of Saturday, November 14, the company announced that all services had been fully restored.
Which Services Were Hit?
While Outlook was the most visibly affected service, the outage had a cascading impact across the Microsoft 365 ecosystem. Users experienced significant problems with Microsoft Teams, including scheduling and features linked to Exchange calendars. The disruption also affected SharePoint Online, OneDrive, and the AI assistant Copilot, which relies on access to Microsoft 365 data to function. The failure was so extensive because many of these applications are deeply integrated, meaning a problem with a foundational service like Exchange Online can cripple features across the entire suite.
The 'Perfect Storm' Behind the Crash
In a preliminary report, Microsoft explained the outage was caused by a 'perfect storm' of three separate issues occurring at once. The first was a latent software bug introduced in a July 2026 update. This bug, which went undetected in testing, could cause servers to become unresponsive under very specific, heavy load conditions. The second factor was a traffic surge that created those exact conditions. About 15 hours before the outage, Microsoft Teams experienced a minor, unrelated issue and automatically shifted its network traffic to the same primary gateway used by Exchange Online. This failover, normally a routine resiliency measure, dramatically increased the load. Finally, about 14% of the network gateway's server capacity was already offline for routine maintenance from the previous day. The combination of the hidden bug, the sudden traffic surge from Teams, and the reduced server capacity triggered a cascading failure that took down over 80% of the gateway servers at its peak.
Why the Outage Hit India Hard
The timing of the outage was particularly damaging for Indian businesses. The worst of the disruption occurred during the entire workday on Friday, November 13, a critical period for wrapping up the week and coordinating with global clients. India's massive IT services industry, which relies heavily on Microsoft's collaboration tools, was severely affected. According to an estimate by market intelligence firm EIIRTrend, the sector may have lost around $200 million from lost billable hours, project delays, and the extra costs of catching up. Beyond the IT sector, several Indian airlines, including IndiGo and Akasa Air, reported that their email-based customer support channels were down, forcing them to redirect customers to other support platforms. The event served as a stark reminder of the Indian economy's deep integration with and dependence on global cloud infrastructure.
The Long Road to Recovery
Fixing an outage of this magnitude proved unusually complex. Microsoft engineers couldn't simply roll back the faulty update because the bug had been in the system since July. Furthermore, their automated recovery processes struggled because as soon as servers were brought back online, they were immediately overwhelmed by the massive backlog of queued emails and data requests, causing them to fail again. Engineers had to develop and deploy a specific fix for the bug across the global infrastructure while managing the immense volume of backed-up traffic. Services that could be rerouted to alternative infrastructure, like some Teams functions, recovered faster, but Exchange Online, due to its scale, could not be easily switched, prolonging the email blackout.
















