Key facts
- Microsoft said a latent bug from July caused its servers to become overwhelmed and unresponsive.
- Charles Lamanna said one of two networking gateways was not working for Microsoft Teams, overloading the primary gateway.
- Lamanna said more than 14% of Microsoft's server capacity was not working because of an unrelated issue from the previous day.
- Lamanna said normal rollback and automated recovery processes could not restore service from the unresponsive state.
- Microsoft said it did not attribute the blackout to a cybersecurity breach.
- Microsoft plans to publish a final report with more information, Lamanna said.
Microsoft said on November 16, 2026 that a latent bug dating from July caused the 24-hour outage of Outlook, Exchange and other Office 365 services that began on November 12. In an initial report issued that Monday, the company said the months-old defect malfunctioning connections between internal systems was a factor in the disruption, and that each factor might have been resolved alone but together produced an outage that was harder to mitigate.
The disruption began on November 12 with US users reporting interrupted access to their Outlook email accounts. As it continued into the next day, millions of people worldwide said they could not access their email or other Office 365 services. Jails could not release prisoners, hospitals turned to paper records, schools lost contact with parents, and police departments could not receive crime reports, according to the report. Microsoft said it had resolved the issue and restored service by November 14, and issued an apology. The company did not attribute the blackout to a cybersecurity breach.
In a post on X on November 16, Charles Lamanna, the executive vice-president of Copilot, Agents, and Platform at Microsoft, said the latent bug from July caused Microsoft's servers to "become overwhelmed and unresponsive". Lamanna wrote that Microsoft typically has two networking gateways, the entry and exit points that connect separate systems and allow data to pass between them, but one was not working for Microsoft Teams, which overwhelmed the primary gateway. More than 14% of the company's server capacity was also not working because of an unrelated issue from the previous day, he wrote.
"Taken together, the increased load and the reduced server capacity, caused the network gateway to encounter the latent bug from July," Lamanna wrote. He said requests built up until servers stopped responding, during the peak window of traffic in the United States. Recovery took longer than usual because returning servers were immediately overwhelmed by waiting traffic, and the company's normally automated recovery processes were not designed to restore service from that state, he wrote. Because the main code defect was months old, normal rollback, flighting and feature flags could not quickly revert it, he said. Lamanna said Microsoft plans to publish a final report with more information.
Matt Hull, vice-president of cyber intelligence and response at NCC Group, said the outage showed the need for companies to examine their reliance on a single operating system. "This is a prime example of the importance of not only cyber resilience, but business resilience," Hull said, adding that reports of hospitals, schools and other essential services being affected demonstrated the wide impact a system outage can have regardless of its cause.