Microsoft has attributed last week's global outage of Outlook and other Microsoft 365 services to a software defect introduced in July, revealing that more than 80 per cent of servers supporting its networking gateway became unresponsive at the peak of the disruption.

Charles Lamanna, Microsoft's Executive Vice President of Copilot, Agents and Platform, said three factors combined to trigger the failure, including the latent software defect, a shift in Microsoft Teams traffic to the primary gateway and reduced server capacity.

The outage ran from 4:20 PM UTC on Thursday, November 12, until 4:10 PM UTC on Friday, November 13, according to Microsoft's preliminary post-incident report dated November 15. The incident is recorded as EX1550543/MO1550821.

The hidden defect from July

The first factor was a hidden software defect that caused servers to become overwhelmed and unresponsive under certain load conditions. The defect originated in a fix developed specifically for Microsoft 365 networking gateway servers and does not affect broader Windows deployments, Lamanna said.

The initial change began rolling out in July and remained in place worldwide for more than three months without causing any disruption.

The defect went unnoticed because Microsoft's load testing used weaker hardware with fewer processor cores and different traffic patterns from the real-world systems, so the problem never showed up in tests.

Two more factors lined up

The second factor emerged about 15 hours before the outage, when Microsoft Teams shifted from an alternative gateway to the primary gateway, which also supports Exchange Online, the company's email platform. That increased the load on the gateway and changed its traffic patterns.

The third factor was that nearly 14 per cent of the gateway's server capacity was already out of service due to an unrelated issue from the previous day.

The combination of increased traffic and reduced capacity triggered the latent software defect. In under two hours, more than 80 per cent of the servers had stopped responding, as automatic systems moved traffic to healthy servers that then locked up too.

What was affected and what happens next

The outage disrupted Teams, OneDrive, SharePoint and Office applications, with Exchange Online suffering the greatest impact. The disruption hit Indian airlines, financial services firms and other businesses.

The fix and the final report

Engineers eventually found the faulty code and developed an update that restored normal functioning. Microsoft said the fix returned Windows connection handling to its earlier working state.

A final post-incident report with more details and corrective steps is due by November 20, 2026. Microsoft said no action is needed on users' own PCs or devices, as the bug was in its cloud infrastructure, not in customer Windows systems.