3 Sources
[1]
Microsoft reveals that an old bug caused the massive outage that took its services offline
It was one of three root causes for the outage that affected business, hospitals, governments and other organizations worldwide. Microsoft has revealed more details about the outage that took services like Outlook, Teams and Copilot 365 offline, affecting businesses, hospitals, law enforcement and
[2]
Microsoft Reveals Root Cause Of Massive Microsoft 365 Outage, As Months-Old Windows Bug Crippled Over 80% Of Servers
Microsoft has finally resolved the massive Microsoft 365 outage that disrupted Outlook, Teams, Copilot, and numerous other cloud services worldwide on November 12-13. The company has also published a preliminary post-incident report revealing that a months-old Windows server defect, combined with
[3]
Microsoft says latent July bug triggered global Microsoft 365 outage By Investing.com
Investing.com -- Microsoft Corporation (NASDAQ:MSFT) disclosed that a latent software defect lurking in its data centers since July triggered last week's widespread outage across Outlook, Teams, and its Copilot AI assistant. The disruption, which halted workflows for corporate and government
Share
Copy Link
A bug that had been sitting inside Microsoft's systems since July took Outlook, Teams, Copilot and other Microsoft 365 services offline around the world for nearly 24 hours this week, and the company now says it took three separate problems arriving at once to set it off
2
3
.
Source: Wccftech
Per Microsoft's preliminary Post-Incident Report, dated November 15, the outage ran from 4:20 PM UTC on November 12 until 4:10 PM UTC the following day
2
1
. It names three contributing factors.One was a latent defect introduced by a July Windows update on the servers that handle network traffic for Microsoft 365. Under certain workloads, it caused lock contention that exhausted CPU and memory. Another was routine: Teams traffic was automatically rerouted onto the primary gateway shared with Exchange Online about 15 hours before the outage began
2
3
. Microsoft typically runs two such gateway systems, and one was already not working for Teams1
. The remaining factor was bad luck: nearly 14% of the gateway's capacity was already offline from an unrelated problem the day before2
3
.More than 80% of the gateway's servers had stopped responding within two hours, and automated traffic redirection overwhelmed the remaining ones in turn, per Microsoft's own executive vice president
2
3
1
. Regional containment safeguards failed to stop the spread2
3
.The bug escaped testing for more than three months, Microsoft says, because its labs ran on lower-core-count hardware, where the lock contention was less likely to appear
2
3
.Exchange Online suffered the greatest disruption, per the preliminary report, with many users unable to reach mailboxes or send and receive email
2
3
. Teams, Copilot, SharePoint and OneDrive had trouble with features that depend on Exchange Online2
3
. Outlook and Exchange stayed tied to the failing gateway through peak US business hours while other apps shifted away2
3
.
Source: Engadget
Recovery was slow for a structural reason: the bug was months old, so the standard rollback tools and feature flags engineers would normally use were useless
2
3
1
. Servers crashed again after restarts under accumulated traffic2
1
. Reverting the code meant pulling over half the infrastructure in a region offline at once2
3
1
. Investing.com reports it took roughly 15 hours to find the root cause and another 15 to begin rolling out the fix3
.The affected connection-handling code has been fixed, and webmail availability was back to normal worldwide as of 2:17 PM UTC on November 13
2
. The outage hit businesses, hospitals, law enforcement and governments3
1
. Investing.com says institutional clients and market observers are likely to scrutinize Microsoft's load testing and failover safeguards3
. It frames the episode as a reminder of the concentration risk in relying on a single cloud vendor3
.The report also says there is no sign of malicious activity or of AI agents playing a part
2
. The defect, it adds, is specific to Microsoft's own gateway infrastructure rather than Windows more broadly2
. Charles Lamanna, Microsoft's executive vice president for Copilot and AI agents, apologized on X: "We are deeply sorry for the impact to all our customers and recognize the impact that this has on their normal business & operations"1
.Microsoft has since added traffic-distribution safeguards, expanded monitoring and increased capacity
2
1
. The queued email that backed up during the incident was later confirmed processed2
. The company plans to publish its final report on the outage by November 20, with additional corrective measures to come in it2
1
.Related Stories
Summarized by
Navi
[1]
13 Nov 2026•Technology

14 Nov 2026•Business and Economy

13 Nov 2026•Technology
