Microsoft Outlook outage cause: July bug, Teams failover downed 80% of gateways

Representative image: Tho-Ge / Pixabay
Microsoft said on 16 November 2026 that a hidden bug from a July update, extra Teams traffic and lost capacity caused the 12 November Outlook outage.
What Happened
Microsoft has explained what caused the global outage of Outlook email and other Microsoft 365 services on Thursday, 12 November 2026. In a post on Monday, 16 November, Charles Lamanna, Microsoft's executive vice president for Copilot, Agents and Platform, said three factors came together: a hidden software defect introduced by an update that began rolling out in July, a surge of traffic after Microsoft Teams switched onto the main network gateway about 15 hours earlier, and nearly 14% of gateway capacity being out of service because of an unrelated problem the day before. At the worst point, more than 80% of the gateway servers stopped responding. Lamanna apologised to customers.
Microsoft Outlook Global Outage Causes: key facts
- Outage date: Thursday, 12 November 2026; the root-cause explanation was posted on Monday, 16 November 2026.
- Factor 1: a latent defect caused gateway servers to lock up under certain loads; it came from a fix made specifically for Microsoft 365's networking gateway servers and first began deploying in July 2026.
- The change ran worldwide for more than three months without problems; Microsoft's load tests missed it because they focused on weaker hardware with fewer processor cores, while the defect was worse on newer machines with more cores.
- Factor 2: about 15 hours before the outage, Teams failed over from a secondary gateway to the primary gateway that also serves Exchange Online, adding load.
- Factor 3: nearly 14% of the gateway's server capacity was already out of service from an unrelated issue the previous day.
- Spread: as traffic moved from failed servers to healthy ones, the same fault hit them too; within two hours more than 80% of servers were unresponsive.
- Microsoft said the cause was not a cyberattack, and that a separate issue stopped its normal regional "bulkheads" from containing the failure.
Microsoft Outlook Global Outage Causes: why it matters
On 12 November, users around the world lost access to Outlook email through Exchange Online, Microsoft's cloud email service, with knock-on effects on other Microsoft 365 services. Our earlier report covered Microsoft's first explanation that day: servers had failed automated health checks and the remaining servers were overloaded, and Microsoft had not yet found a final cause. The new explanation fills that gap.
The key lesson for businesses is how small, separate problems can add up. Each factor alone was harmless, according to Microsoft: the July change had run for months without trouble, Teams switching gateways is a normal part of operations, and the service had enough spare capacity to cover the 14% that was offline. Together, they pushed the gateway into the hidden fault. Then the system's own safety feature, which redirects users away from failed servers, spread the load onto the remaining machines and made them fail too. Engineers call this a cascading failure.
The testing gap is a second lesson. The defect was worse on newer, more powerful servers, but Microsoft's load tests mainly used older hardware. That is why a change that passed testing and months of real use could still bring down the service. For Indian companies, banks, schools and government offices that run their email and documents on Microsoft 365, the episode shows why a business-continuity plan should not assume a large cloud provider never goes down.
Peepals calculation: before the cascade, about 86% of the gateway's server capacity was in service (100% minus the nearly 14% already offline). At the low point, more than 80% of servers were unresponsive, so fewer than one server in five was still answering (100 minus 80 = under 20%). The capacity in service therefore fell from about 86% to under 20% in less than two hours. Our calculation from the reported figures.
| Factor | What Microsoft said |
|---|---|
| Latent defect | Lock-up bug from a gateway fix first deployed in July 2026 |
| Extra load | Teams moved onto the primary gateway about 15 hours earlier |
| Lost capacity | Nearly 14% of gateway servers out from an unrelated issue |
| Result | More than 80% of servers unresponsive at the lowest point |
Impact
Short-term: Microsoft says the cause has been addressed; business customers can read the full root-cause report in the Microsoft 365 admin centre.
Long-term: The explanation points to two weak spots Microsoft named itself, load testing on older hardware and regional barriers that failed to contain the fault, which business customers will watch for fixes.
Who is affected: Businesses, schools, banks and government offices worldwide, including in India, that rely on Outlook, Exchange Online and other Microsoft 365 services.
Key Takeaway
Microsoft says the 12 November Outlook outage was caused by a hidden July bug, extra Teams traffic and 14% lost capacity together, which knocked more than 80% of its gateway servers offline in under two hours.
Questions and Answers
What caused the Microsoft Outlook outage on 12 November 2026?
Microsoft says three things combined: a hidden defect from a gateway update first deployed in July, extra load after Teams failed over to the primary gateway, and nearly 14% of gateway capacity being offline from an unrelated issue.
Was the Outlook outage a cyberattack?
No. Microsoft said the outage was caused by a software defect and load conditions, not by hackers.
How bad was the Microsoft 365 gateway failure?
At its lowest point, more than 80% of the networking gateway servers that front many Microsoft 365 services were unresponsive, and the failure spread across the fleet in less than two hours.
Who explained the cause of the Outlook outage?
Charles Lamanna, Microsoft's executive vice president for Copilot, Agents and Platform, posted the explanation on 16 November 2026 and apologised to customers.
Disclaimer: Prepared by the Peepals newsroom from publicly available sources with AI assistance. Information is accurate to the best of our knowledge at the time of publication and may change. Images may be representative. Not professional advice. Report an error via our contact page.
By Arjun Mehta, Staff WriterCovers Start-ups & Opportunities and more for Peepals Business. All stories by Arjun Mehta
Bharat Taxi Pune launch: cooperative cab app reaches Pune, Pimpri-Chinchwad
Corma valued at $1 billion 98 days after leaving stealth, raises $125 million
Your week ahead, every Sunday. Free.
Exam and result dates, IPOs opening, scheme deadlines, government holidays and the RBI decision for the next 7 days, plus the week's top stories. One email a week, unsubscribe in one click.
Arjun Mehta is a pen name of the Peepals Global Editorial Team, which researches, fact-checks and publishes every story. The portrait is an illustration.
Responsible for this story: the Peepals Global Editorial Team, led by editor Prashant Sonar. How we report









