Microsoft Says AI Did Not Break Outlook. A July Update Tested on Weaker Hardware Did, It Could Not Be Rolled Back, and Copilot, ChatGPT, and Claude Lost Your Mail With It.
Microsoft 365, Exchange Online above all, was disrupted worldwide from November 12 into November 13. Microsoft's preliminary post-incident report, published to tenant admins as MO1550821 on November 15 and quoted by The Register, blames a defect shipped in a July update to Microsoft 365 network gateway servers: lock contention inside an internal Windows process exhausted CPU and memory, worse on machines with more cores and newer hardware, while load testing had focused on weaker hardware with fewer cores. A Teams failover plus about 14% of gateway capacity out of service triggered it, more than 80% of servers went unresponsive at the worst, and a months-old change could not be rolled back. Copilot could not reach mail, files, or calendars, and OpenAI and Anthropic posted that their Microsoft 365 connectors were broken. Microsoft says the incident was not related to cyber or AI agents. The final report is due November 20.
By T.W. Ghost
Microsoft 365 was disrupted around the world from November 12 into November 13, 2026, with Exchange Online the hardest hit. Yesterday, November 15, Microsoft published a preliminary post-incident report to tenant administrators under incident MO1550821. It is not on a public page we could read; every quotation below is as reported by The Register today, and the final report is due November 20. The cause, per the report as relayed: a defect introduced in a July 2026 update to Microsoft 365 network gateway servers. It caused lock contention inside an internal Windows process that exhausted CPU and memory, and it was worse on machines with more cores and newer hardware, while, in the report's words, "our load testing tended to focus on weaker hardware with fewer cores." The defect sat in production for months until a Teams failover to the primary gateway at 01:07 UTC on November 12, with about 14% of gateway capacity already out of service, tipped it over. At the worst point more than 80% of the servers were unresponsive.
Recovery was slow for a reason the report states plainly: a change that old could not be rolled back, and the automated recovery "was not designed to restore service from this broad unresponsive state." Engineers built an update that returned the code path to its known good state, identified and applied it at 07:20 UTC on November 13, and declared the service healthy at 16:10 UTC that day. Teams, OneDrive, SharePoint, and the Office apps were failed away from the gateway during the incident; Exchange Online could not be, "for scale reasons." The AI angle is simple. Copilot could not reach email, files, or calendars, and both OpenAI and Anthropic posted that their Microsoft 365 connectors were broken. Microsoft told the BBC the incident was a "technical issue not related to cyber or AI/agents." We read The Register, the BBC live page, Yahoo Finance, and IT Pro. Here is what held up.
The Timeline, as Reported
| Time (UTC) | Event | Who |
|---|---|---|
| July 2026 | Defect introduced in an update to Microsoft 365 network gateway servers; passed load testing | Press (The Register quoting the PIR) |
| Nov 12, 01:07 | Teams failover to the primary gateway; about 14% of gateway capacity already out of service | Press (quoting PIR) |
| Nov 12, 16:03 | Anomaly monitor fires | Press (quoting PIR) |
| Nov 12, 16:33 | First support case (10:33 AM Central) | Press (quoting PIR) |
| Lowest point | More than 80% of servers unresponsive | Press (quoting PIR) |
| Nov 13, 07:20 | Mitigation identified and applied | Press (quoting PIR) |
| Nov 13, 16:10 | Service healthy | Press (quoting PIR) |
| Nov 14, 04:15 | Final customer update | Press (quoting PIR) |
| Nov 15 | Preliminary PIR to admins (MO1550821) | Press |
| Nov 20 | Final PIR due | Press |
A latent defect, untested on production-class hardware. The report's own admission, as relayed: contention grew with core count and newer machines, and the load tests ran on weaker ones. That is a test-coverage gap, not a zero-day.
No rollback path for a months-old change. The fix was a patch for the patch, hand-built while the gateways were down. Months are long enough that "revert" stops being a button.
AI assistants inherit the outage. Copilot reads your mail through Exchange. So do ChatGPT's and Claude's Microsoft 365 connectors. When the gateway fails, every assistant on top of it fails, and the vendor whose model you chose has nothing to fix.
The "not AI" line is narrow. Microsoft's statement rules out AI and agents as a cause. It says nothing about them as casualties, which they were.
Verified vs Unconfirmed: The Scorecard
| Claim | Verdict |
|---|---|
| Timeline, July defect, load-testing gap, 14% and 80% figures, no rollback | Press (The Register quoting the PIR); not read in Service Health |
| Teams, OneDrive, SharePoint, Office failed away; Exchange could not be | Press (quoting PIR) |
| Final PIR due Nov 20 | Press |
| "Technical issue not related to cyber or AI/agents" | Verified (Microsoft statement to the BBC) |
| Copilot lost mail, files, calendars; OpenAI and Anthropic connectors broken | Press (Yahoo Finance; IT Pro relaying status wording) |
| 430 million Microsoft 365 users | Vendor number |
| SLA 99.9%; credits 25% to 100% of the monthly fee; admin must file | Press summary; check the Microsoft Online Services SLA before relying on it |
| Microsoft blamed its own changes for disruptions in at least six months this year | Press tally; unverified |
| Whether connectors needed re-authorization after recovery | Not checked |
What To Do
Read the PIR in your own admin center, or in a university mirror, before quoting it as Microsoft's words; everything above is second-hand until you do.
Skip assuming a credit arrives; the SLA terms as summarized put the filing on the administrator, and the tiers need checking against Microsoft's own document.
The frontier is elsewhere: an AI assistant is only as available as the mail system under it, which is one argument for knowing exactly what a self-hosted agent stack does and does not move inside your walls. Our model comparison has the current standings side by side.
Sources
- The Register: Microsoft blames monster email outage on software defect introduced in July
- BBC: live coverage of the Microsoft 365 outage
- Yahoo Finance: Microsoft's latest outage hit Outlook and Copilot
- IT Pro: Microsoft 365 outage disruption continues with issues spanning Copilot, Exchange, and SharePoint
- UPenn ISC: Microsoft incident alerts (possible PIR mirror, not read)
*Not sure how much of your AI stack depends on one vendor's gateway staying up? Take the free 2-minute quiz and get matched. Then read about the agent stack you can run yourself, and what stays hosted: self-hosted Claude Managed Agents.*