Security
Microsoft says a July gateway bug and a Teams failover left more than 80 percent of servers unresponsive in the November 12 Microsoft 365 outage, which reportedly began in Switzerland
Microsoft’s preliminary account blames a July gateway bug and a Teams failover; reports say the outage began in Switzerland.
Microsoft has given a preliminary explanation of the Microsoft 365 outage of November 12–13: a software bug introduced in July, triggered by a Teams failover, left more than 80% of servers unresponsive. This follows our November 16 note that we could not find the report; it has now been covered by several outlets.
The essentials
- The cause: per BleepingComputer, a bug introduced in July through an update for Microsoft 365 networking gateway servers was triggered after Teams switched to Exchange Online’s infrastructure about 15 hours earlier.
- The spread: heise online says the entire gateway fleet was affected within two hours, as traffic moved to healthy servers carrying the same flaw.
- The start: Aroged, citing The Verge, says Exchange Online servers in Switzerland were the first to stop responding, then Mexico and other countries.
- The scale: at its lowest, more than 80% of servers were unresponsive, per BleepingComputer; Techmeme’s summary of The Verge says 80%+ of Exchange servers.
Why recovery was hard
BleepingComputer says restarting affected servers made them quickly overwhelmed again by backed-up traffic. Techmeme’s summary of The Verge says failover systems shifted traffic as the problem spread.
A wording difference
Microsoft’s account, as relayed by BleepingComputer, speaks of networking gateway servers; Aroged and Techmeme speak of Exchange servers. The two are linked but not identical.
What is not established
- Whether the 80% means gateway or Exchange servers: wording differs between outlets.
- The total number of affected customers: not stated in the coverage.
- Microsoft’s final post-incident report: only a preliminary account is covered.
- Any customer compensation: not mentioned.
Summary table
| Point | What is stated as of November 18, 2026 | Source |
|---|---|---|
| Dates | November 12–13, 2026 | heise online |
| Root cause | July gateway update bug | BleepingComputer |
| Trigger | Teams failover to Exchange Online infrastructure | BleepingComputer |
| First affected | Exchange Online servers in Switzerland | Aroged |
| Peak impact | More than 80% unresponsive | BleepingComputer |
FAQ
Was it a cyberattack?
The accounts in the coverage describe a software bug and failover cascade, not an attack.
Where did it start?
With Exchange Online servers in Switzerland, per Aroged citing The Verge.
Why did restarts not help quickly?
Restarted servers were overwhelmed by backed-up traffic, per BleepingComputer.
Sources
- Techmeme: Sources detail how the Microsoft 365 outage began in Switzerland and spread as failover systems shifted traffic (Tom Warren/The Verge) (verified 2026-11-18)
- BleepingComputer: Microsoft says months-old bug caused global Microsoft 365 outage (verified 2026-11-18)
- heise online: Exchange Online outage: Latent bug in July fix took down gateways (verified 2026-11-18)
- Aroged: More than 80% of Exchange servers are out of order: Microsoft explained how it itself aggravated the global Outlook failure (verified 2026-11-18)
Spotted an error in this article? Report it · Our corrections policy