How a months-old bug plunged Microsoft’s services into darkness
Microsoft reveals what caused last week’s global Outlook and Office 365 outage: a months-old bug, faulty connections and reduced server capacity.
-
A computer screen shows the Microsoft support page in London, Nov. 13, 2026. (AP)
Microsoft has traced last week's worldwide outage, which knocked out Outlook, Exchange and a range of other essential office tools, to a combination of three problems, according to an early report released Monday.
The faults were an old software defect, internal connections that failed to work properly, and a shortfall in server capacity. Microsoft leaders said any one of these could probably have been fixed without much trouble, but together they made the breakdown, which lasted about 24 hours, far harder to contain.
How the disruption unfolded
The trouble started Thursday, when US customers found they could not reach their Outlook mailboxes. By the following day, millions of people around the world had lost access to email entirely, along with other Office 365 services.
The knock-on effects were serious: jails were unable to release inmates, hospitals fell back on paper records, schools could not reach parents, and police departments were unable to take crime reports.
Microsoft apologized and said service had returned by Saturday. It did not link the outage to a security breach.
A hidden flaw from July
Writing on X on Monday, Charles Lamanna, Microsoft's executive vice-president of Copilot, Agents, and Platform, said a hidden flaw dating back to July had caused the company's servers to "become overwhelmed and unresponsive".
He explained that Microsoft normally runs two networking gateways, which act as the entry and exit points that let separate systems exchange data.
One of these was not functioning for Microsoft Teams, which put the main gateway under heavy strain. On top of that, more than 14% of the company's server capacity was offline because of a separate problem that had begun the day before.
"Taken together, the increased load and the reduced server capacity, caused the network gateway to encounter the latent bug from July," Lamanna wrote. "This caused requests to build up until servers ultimately stopped responding. This occurred during the peak window of traffic in the United States."
Why recovery took so long
The age of the flaw also complicated the response, Lamanna said, because the company could not simply reverse a recent update to remove it.
"Recovery took longer than usual because as servers returned to service, they were immediately overwhelmed by waiting traffic and became unresponsive again," he wrote. "Our normally automated recovery processes were not designed to restore service from this broad unresponsive state.
Additionally, since the main code defect was a latent bug from several months previous, our normal rollback, flighting, and feature flags were unable to quickly revert the change."
Microsoft intends to release a final report with further details, he added.
Calls for greater resilience
Industry analysts argue the incident should prompt organizations to think harder about their dependence on one operating system.
Matt Hull, vice-president of cyber intelligence and response at NCC Group, said the outage shows why organizations need to build resilience into their business operations as well as their cybersecurity.
"Reports that hospitals, schools and other essential services are affected demonstrate the wide impact that a system outage can have, regardless of the cause," Hull noted.
Read next: Microsoft's role in world’s first AI-driven genocide, in Gaza, exposed