Microsoft says a software bug from a July update caused the November 12, 2026 Microsoft 365 outage, which left more than 80% of its networking gateway servers unresponsive.
What happened
The outage began at 11:20 AM ET on Thursday, November 12, 2026, and lasted nearly 24 hours. Microsoft confirmed full restoration at 11:10 AM ET on Friday, November 13, 2026. The disruption hit Microsoft 365 services worldwide, including Outlook, Exchange Online, Teams, and Copilot. Users could not access their email, and message delivery slowed.
In a preliminary post-incident report in the Microsoft 365 Admin Center, Microsoft blamed three problems: a previously undetected software bug, increased traffic after a Microsoft Teams failover, and reduced server capacity. Microsoft engineers developed a fix and deployed it across the affected servers, and services stabilized throughout Friday.
The backstory
Microsoft introduced the bug in July 2026 through an update to its Microsoft 365 networking gateway servers. The update ran for more than three months without issues. Microsoft’s testing did not catch the flaw because its labs used less powerful hardware than its production servers.
Going deeper
- The bug: Under certain traffic conditions, the flaw overwhelmed servers and made them stop responding.
- The trigger: Microsoft Teams automatically switched to the networking infrastructure that Exchange Online uses about 15 hours before the outage, which increased traffic on those servers.
- The capacity gap: An unrelated issue had already taken nearly 14% of the gateway’s server capacity offline. The infrastructure could handle that reduction alone, but the added traffic triggered the bug.
- The cascade: As servers failed, Microsoft’s systems redirected users to other servers, which the extra traffic then overwhelmed. Safeguards meant to stop problems from spreading between regions failed to contain the failures, so the disruption spread worldwide.
- The recovery: Restarting affected servers did not work at first, because backed-up traffic quickly overwhelmed them again.
- The Teams outage: Teams also had a separate outage earlier on November 12. Microsoft has not said whether the two incidents are related.
What was said
Microsoft explained in its preliminary report why testing missed the bug, “The contention issue is worsened on machines with more cores and newer hardware; whereas our load testing tended to focus on weaker hardware with fewer cores.”
Microsoft also described how quickly the failure spread, “In less than two hours, the previously unknown defect was encountered across our fleet and rendered them unresponsive. At its lowest, more than 80% of servers were unresponsive.”
Microsoft said it has since increased capacity, improved monitoring, and added safeguards to stop traffic redirection from triggering similar cascading failures. Its investigation continues, and it expects to publish a final post-incident report during the week of November 16, 2026.
By the numbers
- Nearly 24 hours: the length of the outage (11:20 AM ET on November 12 to 11:10 AM ET on November 13, 2026)
- More than 3 months: how long the buggy update ran without issues before the outage
- About 15 hours: how long before the outage Teams switched to Exchange Online’s networking infrastructure
- Nearly 14%: the share of gateway server capacity already offline
- Less than 2 hours: how long the defect took to spread across Microsoft’s server fleet
- More than 80%: the share of servers unresponsive at the lowest point
Why it matters
This outage shows how a flaw can sit unnoticed for months and then cause a global failure. The July update ran for more than three months before a Teams failover and a capacity shortfall triggered the bug. Microsoft’s lab testing used weaker hardware than its production servers, so it never exposed the problem.
Email suffered the most. Teams, OneDrive, and SharePoint could switch to alternative infrastructure and recover earlier, but Exchange Online could not. Users were locked out of their mailboxes for nearly a full day. For organizations that depend on Microsoft 365 for email, the incident shows how one provider’s infrastructure problem can cut off a communication channel with no backup.
The bottom line
Microsoft has added capacity, monitoring, and new safeguards, and a final report is due the week of November 16, 2026. Organizations that rely on Microsoft 365 should read that report and ask whether their email provider tests updates on hardware that matches production.
Related: HIPAA Compliant Email: The Definitive Guide
FAQs
What is Exchange Online?
Exchange Online is Microsoft’s cloud-based email and calendar service for organizations.
Why do email outages matter for healthcare organizations?
Healthcare teams rely on email to coordinate care and share information, so an outage can delay communication.
How can organizations prepare for a cloud service outage?
Organizations can prepare by keeping a backup communication method and a documented plan for staff to follow during downtime.
