Microsoft Blames July Software Bug for Global Microsoft 365 Outage
Microsoft has identified the cause of the global Microsoft 365 outage that left millions of people unable to reach their email and workplace tools on 12 and 13 November: a software defect introduced in a July update to its network gateway servers, which sat undetected for more than three months before a surge in traffic triggered it.
The company set out the findings in a preliminary post-incident report published on Sunday 15 November, with Microsoft executive Charles Lamanna also posting an abridged version of the report. The outage knocked out Outlook, Teams, SharePoint and Copilot for much of the working day, and Microsoft now says it knows why.
A bug that hid for more than three months
The faulty change was written specifically for the Microsoft 365 networking gateway servers, the systems that receive user connections before passing them on to services such as Exchange Online, the email system behind Outlook.
Under certain workloads, the defect caused lock contention inside an internal Windows process, exhausting the server’s processor and memory resources until the machine stopped responding. The change went through Microsoft’s staged deployment process from July and, in the company’s own words, ran worldwide for more than three months “without impact”.
It escaped detection because Microsoft’s load testing did not reproduce the conditions that trigger it. The defect is worse on newer machines with more processor cores, while the company’s testing “tended to focus on weaker hardware with fewer cores”, The Register reported, quoting the report.
Microsoft stressed that the defect is specific to its Microsoft 365 gateway infrastructure and does not affect broader Windows deployments, so there is nothing for ordinary Windows users to install or fix.
Three problems collided on 12 November
Microsoft cites three factors behind the failure, and none of them alone would have caused an outage on this scale.
The first was the hidden July bug. The second was an automated failover in Microsoft Teams: at 01:07 UTC on Thursday 12 November, Microsoft’s systems automatically moved Teams traffic from a second, independent gateway onto the one that also carries Exchange Online.
The third was reduced capacity. At the time, almost 14 percent of the networking gateway’s server capacity was already out of service. The extra Teams traffic hit a gateway that was both short of capacity and carrying the dormant defect — and the defect woke up.
Within about two hours, more than 80 percent of the gateway servers had stopped responding, and users across the world found they could not reach their inboxes.
How the outage unfolded
The disruption began at 16:20 UTC on Thursday 12 November, or 11:20 a.m. Eastern time, TechCentral reported, and the worst-hit service was Exchange Online. The first support case arrived at 16:33 UTC. By 00:30 UTC on Friday 13 November, engineers had identified connection negotiation as the main culprit, concluding that competing processes were preventing connections from being handled.
At first, engineers tried to patch the faulty code rather than roll it back. But at 07:20 UTC on Friday, they applied an update that reverted the defective change. By 16:10 UTC, Microsoft confirmed that services were healthy again, and it issued its final customer update at 04:15 on Saturday 14 November.
The preliminary report puts the disruption at almost 24 hours, shorter than the roughly 36-hour figure cited when the service was declared fully restored on Saturday, which counted from Microsoft’s first public acknowledgement of the problem on Thursday.
What Microsoft says happens next
Microsoft says it has already restored stable connection-handling code, cleared the backlog of delayed emails, expanded server capacity and introduced safeguards intended to stop a similar cascading failure.
A final post-incident report is due by 20 November, with a full list of repairs. The company also reiterated that the outage was a technical failure, with no indication of malicious activity and no involvement of AI agents.
For businesses that depend on Microsoft 365, the episode is a reminder of how much everyday work now runs through a single cloud gateway.
Frequently asked questions
What caused the Microsoft 365 outage?
Microsoft says a software defect introduced in a July 2026 update to its Microsoft 365 networking gateway servers caused lock contention that exhausted server resources. The defect was triggered on 12 November when Teams traffic was automatically moved onto the same gateway while about 14 percent of its capacity was already offline.
Which services were affected?
Outlook and Exchange Online were hit hardest, with Teams, SharePoint and Copilot also disrupted. At the worst point, more than 80 percent of the networking gateway servers had stopped responding.
When will Microsoft publish its final report?
Microsoft says a final post-incident report, with a full list of repairs, is due by 20 November 2026.