Microsoft Says a July Change Took Down Microsoft 365. 3 Things MSPs Tell Clients.
If your phone lit up on November 12 with "is email down for everyone or just us?", you were not alone. Microsoft has now published a preliminary explanation of that outage, and the short version is this: it was not a hidden Windows bug on your clients' PCs. It was a problem inside Microsoft's own cloud, and it had been sitting there since July.
That matters for how you talk to clients this week. Here is what Microsoft says happened, and the three things I would tell every client.
You can watch the short version here:
What Microsoft published
Early on November 16, the Microsoft 365 Status account said the Preliminary Post-Incident Report for last week's outage is available in the Microsoft 365 admin center under two incident IDs: MO1550821 and EX1550543. Charles Lamanna, Microsoft's EVP of Copilot, Agents, and Platform, posted an abridged version of the root cause publicly the same morning.
Microsoft describes three factors that together caused a global outage of the networking gateway that sits in front of many Microsoft 365 services.

1. A defect that started rolling out in July
A change that first started deploying in July carried a latent defect. Under certain load, lock contention inside an internal process made the gateway servers overwhelmed and unresponsive. Microsoft says the fix that introduced the defect was prepared specifically for the Microsoft 365 networking gateway servers, and that neither the defect nor that fix applies to broader Windows deployments.
The change ran worldwide for more than three months with no visible issue. Microsoft's load testing missed it because the tests leaned on weaker hardware with fewer cores, and the contention gets worse on newer machines with more cores.

2. A routine Teams failover
About fifteen hours before the outage, Teams failed over from an alternative networking gateway onto the "primary" gateway, the same one Exchange Online uses. That added load. Microsoft describes this kind of failover as part of normal operations.
3. Capacity already out
At the same time, nearly 14 percent of the gateway's server capacity was out of service from an unrelated issue. Microsoft says the service had enough headroom that the drop, on its own, had no impact.
How three ordinary things became one big outage
Put the extra load and the reduced capacity together, and the gateway hit the July defect. When servers stopped responding, automated traffic management did what it normally does and sent users to other healthy endpoints. That pushed the same load onto fewer servers, which hit the same defect. In less than two hours, it had spread across the fleet. At its lowest point, more than 80 percent of servers were unresponsive. Microsoft also says the normal boundaries between regions did not stop the cascade, because of a separate issue.
Teams, OneDrive, SharePoint, and Office apps were able to move off the faulty gateway, which is why they came back earlier. Exchange Online could not, which is why mail was out the longest.
Recovery was slow for two reasons Microsoft names. Servers that came back were immediately overwhelmed by the traffic waiting for them. And because the defect came from a change made months earlier, the usual rollback tools could not quickly undo it. Engineers built an update that returned the code path to its previous known good state and applied it to groups of servers at a time.
Microsoft says the final post-incident review will come later this week. The Register and Cybersecurity News, quoting the preliminary report, put that date at November 20. If numbers move in the final report, go with the final report.

Why this matters to MSPs
None of this was in your clients' control, or yours. No patch you pushed, no setting you missed. But your clients will still judge you on the hours it was down: whether they heard from you first, whether they knew what to do, and whether they had a way to keep working.
A change can sit quietly for months and still take the cloud down. You cannot plan around the bug. You can plan around the hours.
3 things to tell clients
1. This was a Microsoft cloud issue, not your computers
Say it plainly, because the headlines did not. At least one outlet called this a "hidden Windows bug," and that is exactly the kind of line that makes a client wonder whether their own laptops need fixing. Microsoft's own text says the defect does not apply to broader Windows deployments.
Then show your work. Have an admin pull up the Service health page in the Microsoft 365 admin center and find MO1550821 and EX1550543, so the client sees Microsoft's report, not just your word for it. If the admin center itself is hard to reach during an incident, Microsoft also runs a public service status page.
2. Keep a second way to reach staff when email is down
If email is the only way you tell staff what is going on, an email outage leaves everyone guessing. Pick a channel that does not ride on the same service: a phone tree, a text list, even a printed roster with mobile numbers.
Teams came back earlier this time. Do not build the plan around that. Teams was in the blast radius too, and its own routine failover was one of the triggers. Next time the order could be different.
3. Ask your MSP for the outage playbook, or write it if you are the MSP
This is the conversation I would have with every client this month. When the cloud is down, who does what? A good outage playbook answers four questions:
Who tells the staff, and through which channel.
Who watches Service health and posts updates on a set schedule, even when the update is "no change."
How mail is handled while the queue builds: what staff should expect, and what to do with anything time sensitive in the meantime.
What the backup channel is, and that everyone already has it before they need it.
If you are the MSP, write this once, adapt it per client, and walk them through it before the next incident. One page is enough. The value is that nobody has to invent it in the first hour.
The takeaway
Microsoft's report is a good reminder that resilient systems still fail in surprising ways: a months-old change, a normal failover, and a capacity dip that was fine on its own. The part you control is what happens in the hours after. Tell clients the truth early, give staff a second channel, and have the playbook written before you need it.
That is the kind of planning we do with our clients at Chibitek. If you want a second set of eyes on your outage playbook, reach out.
Sources
Microsoft 365 Status (@MSFT365Status), post announcing the Preliminary Post-Incident Report under MO1550821 and EX1550543, Nov. 16, 2026: https://x.com/MSFT365Status/status/2122205066157257160
Charles Lamanna, EVP of Copilot, Agents, and Platform at Microsoft, abridged root cause from the preliminary report, Nov. 16, 2026: https://x.com/clamanna/status/2122209697226948729
Microsoft Learn, "How to check Microsoft 365 service health": https://learn.microsoft.com/en-us/microsoft-365/enterprise/view-service-health
Microsoft service health status page: https://status.cloud.microsoft/
Microsoft Power Platform Blog, author page for Charles Lamanna (title): https://www.microsoft.com/en-us/power-platform/blog/author/charles-lamanna/
The Register, "Microsoft blames monster email outage on software defect introduced in July fix," Richard Speed, Nov. 16, 2026: https://www.theregister.com/saas/2026/11/16/microsoft-blames-monster-email-outage-on-software-defect-introduced-in-july-fix/5310026
Cybersecurity News, Microsoft 365 outage incident report coverage, Guru Baran, Nov. 16, 2026: https://cybersecuritynews.com/microsoft-outage-incident-report/








Comments