Back to Blog

Microsoft 365 Went Down for Half a Day. Your Continuity Plan Probably Assumed It Would Not

• 3 min read • Ahmed Daoudi

On the afternoon of November 12, 2026, a large part of the working world lost email, chat and its AI assistant at the same time. Microsoft 365 services including Outlook, Teams and Copilot started failing around 16:17 GMT, and parts of the incident were still open the next morning.

What we know so far

The failure pattern engineers should recognize

This looks like a classic cascading failure. A change makes some servers unhealthy. The load balancer removes them. Their traffic moves to the remaining servers, which now handle more than they were sized for, start failing health checks too, and get removed in turn. Retrying clients make it worse by sending more requests at the moment the system can least handle them.

None of this is unique to Microsoft. The same pattern takes down small APIs every week. The defenses are well known and often skipped:

The AI dependency nobody mapped

One detail stood out to me. Copilot for work stopped answering because it depends on the same Exchange infrastructure as email. Many companies have spent 2026 wiring AI assistants into daily workflows without asking what those assistants depend on. When the mail system fell over, the "AI layer" fell with it.

What to put in your continuity plan

Outages at this scale are rare, but they are certain to happen again. The useful question is not whether a vendor this big can fail. It is which of your processes stop when it does.

Sources