On 2026-11-12, Microsoft 365 broke. For close to 24 hours, Outlook, Teams, Copilot and more were disrupted for users in dozens of countries.
Outages like this attract speculation within minutes: a cyberattack, an AI agent gone wrong, a bad patch. So this post sticks to what Microsoft has said, marks what is still unknown, and then gives my view on what developers should take from it.
Sourcing: Microsoft hasn't published a blog post about this incident that I could find. Its updates came through the Microsoft 365 admin center, its public status page, and posts on X. The statements quoted here come from news outlets that reproduced them. Microsoft has promised a post-incident report, and as of 2026-11-14 it hasn't been published in any source I checked.
What happened
Microsoft tracked the problem as EX1550543 (Exchange Online) and MO1550821 (everything that depends on it).
- EX1550543 began at 16:17 UTC on 2026-11-12: users couldn't reach Exchange Online mailboxes through several connection methods.
- MO1550821 opened at 18:26 UTC, covering Exchange Online, Teams, SharePoint Online, Copilot, and Defender XDR.
- Microsoft paused all deployments and configuration changes, tested a configuration change, and restarted affected servers. An alternative health check method then let a subset of servers return.
- Returned servers could turn unresponsive again once traffic reached them.
- On 2026-11-13 Microsoft reported encouraging recovery progress and extended Outlook's email timeout window to 48 hours.
What Microsoft says caused it
Microsoft apologized on 2026-11-13. It said the incident originated in a problem during an earlier network capacity upgrade, which surfaced after a more recent network change. It also called it a technical issue not related to cyber or AI / agents, and said it restored service gradually, validating stability at each stage.
How the story changed
- First hypothesis: elevated load.
- Corrected within about an hour: the load wasn't more traffic but a large number of servers being unexpectedly unavailable.
- On 2026-11-12: Microsoft said it had not identified any recent change correlated with the start of impact.
- Next day: an earlier upgrade plus a recent change.
These aren't necessarily contradictory. A latent flaw from an earlier upgrade can stay hidden until a later change exposes it. But the post-incident report should reconcile them.
What we still don't know
- What the flaw from the earlier upgrade was, and what the recent network change was
- Why servers failed their automated health checks, and why returned servers became unresponsive again
- The official scale: I found no Microsoft figure for affected users beyond its status updates
- Whether Azure workloads were affected: Azure's status page showed no active events at the time that source was written
What developers should take from it
This is my view, not a claim about Microsoft's internals.
- Health checks are code that can take you down. Microsoft's updates describe servers failing automated health checks and shifting load onto the rest. Ask what happens if every instance fails a check at once, and whether operators can turn automatic removal off.
- Your status channel can't depend on what's down. Microsoft's own status page wasn't loading for a stretch. Host status somewhere that doesn't share fate with your product.
- Recovery has its own failure mode. A backlog and a wave of reconnecting clients arrive with the fix. Design for the second spike.
- Map what silently needs email. Password resets, approvals, alerts, customer replies. Write the manual fallback down before you need it. UK police telling people to call 101 for time-critical reports is exactly that.
- Wait for the report. Microsoft felt it had to say this wasn't AI or a cyberattack. That shows how fast rumors move.
Read the full post
The full post adds the complete timeline, who was affected (including US House communications and Baltimore County government), a note on service credits for business customers, and all sources.
Read it here: Microsoft 365 Went Down for Nearly 24 Hours



Top comments (0)