Microsoft on Monday, November 16 released the preliminary post-incident report into last week's global Microsoft 365 outage, saying more than 80 per cent of the servers behind its networking gateway were unresponsive at the peak of the failure, and blaming a hidden software defect introduced in July, The Hindu BusinessLine reported.

Source: The Hindu BusinessLine

This is the root-cause follow-up to the outage itself, which began on Thursday, November 12, knocked out Outlook and other Microsoft 365 services worldwide, and was fully restored by Saturday, November 14. Read the original outage report

Charles Lamanna, Microsoft's Executive Vice President of Copilot, Agents and Platform, set out three factors that converged, in a post on X on Monday. The full preliminary report was made available to business customers in the Microsoft 365 admin centre under the incident codes MO1550821 and EX1550543, and a final review is due later this week, Expert Insights reported.

Source: Expert Insights

Three factors, one cascade

First, a latent defect in a fix prepared specifically for Microsoft 365 networking gateway servers. The change began rolling out in July and was in place worldwide for more than three months with no impact, Lamanna said; under certain load conditions it left a core process overwhelmed — a lock-contention problem — so servers stopped responding. Microsoft says the defect does not apply to broader Windows deployments.

Second, about 15 hours before the outage, Microsoft Teams shifted from an alternative gateway to the primary gateway that also supports Exchange Online, the company's email platform — concentrating traffic on the very servers carrying the defect.

Third, nearly 14 per cent of the gateway's server capacity was already out of service at the time because of an unrelated issue from the previous day. As servers failed, automatic rerouting pushed traffic onto the remaining healthy endpoints, spreading the load across fewer and fewer machines until, in under two hours, the failure had cascaded across the fleet.

80%+of gateway servers unresponsive at the lowest point
74countries and territories reporting problems within the first hour
15 hrsbefore the outage, Teams had failed over onto the primary gateway
14%of gateway capacity already out of service for an unrelated reason

What the outage hit

The outage began late on Thursday, November 12 and hit Indian airlines, financial services firms and businesses, along with governments, courts, healthcare services and banks in other countries. Outlook email was hit hardest; Teams, OneDrive, SharePoint, Office apps and the Copilot AI assistant were also disrupted, though Teams chats and meetings kept working for much of the outage. More than 430 million people use the affected Microsoft 365 apps.

Microsoft has said from the start that this was a technical issue, not a cyberattack. During the outage the company paused all deployments, and on November 13 it extended its email timeout window to 48 hours so delayed mail would keep retrying instead of bouncing back. Service was restored to the remaining customers and regions early on Saturday, November 14.

One estimate, by the US research firm Anderson Economic Group, puts the cost of the outage at as much as $7 billion in lost productivity — yaani roughly seven billion dollars of work time lost — though that is an outside estimate, not a Microsoft figure, and the company's shares barely moved.

What happens next

Microsoft's final post-incident review is due later this week. The questions it still has to answer: why a defect deployed in July survived three months of worldwide use undetected, why so much gateway capacity was already offline, and what changes will stop a single gateway failure from cascading across Outlook, Teams and Copilot at once.