Microsoft has published its preliminary report on the November 12-13 Microsoft 365 outage. Here's the short version, and what, if anything, you need to do. For what was happening while the outage was live, see our earlier post.
What happened
On Thursday, November 12, a fault in the Microsoft systems that handle connections to Exchange Online, the service behind Outlook, caused those systems to overload. Email was hit hardest: for about a day, many people couldn't open their mailboxes, and messages were delayed. Teams chat and meetings kept working for most people, and SharePoint, OneDrive, and the Office apps recovered well before email did.
Microsoft says this was a technical fault on its side, with no indication of malicious activity. It has published a preliminary report and expects to issue a final one around November 20.
What it means for you
- Your mail was delayed, not lost. Microsoft held queued messages rather than returning them as undeliverable, and it worked through the backlog once service returned.
- There's nothing to fix on your end. The problem was inside Microsoft's infrastructure, so there's no update to install and no setting to change.
- Service has been restored. Microsoft marked the incident resolved on Friday, November 13, and posted its final monitoring update early Saturday.
One worthwhile step: if you were expecting a time-sensitive message during the outage, confirm it arrived.
Service credits
Microsoft's Service Level Agreement for Online Services provides credits when a service misses its uptime commitment, and this outage may qualify for Exchange Online. Credits aren't automatic. You have to ask, and the claim goes to whoever bills you for your Microsoft licenses.
- If you buy directly from Microsoft, the deadline for a November incident is December 31, 2026.
- If you buy through a reseller or Cloud Solution Provider, the claim goes through them, and their deadline may be earlier. Partners can follow Microsoft's guide on how and when to request a credit.
To be ready, save the incident records (EX1550543 and MO1550821) and the preliminary report from the Microsoft 365 admin center under Health > Service health, and note when your users lost and regained email. Microsoft explains where to find them in How to check Microsoft 365 service health. We're happy to help you pull the records and work out your downtime.
Read more from Microsoft
- The full preliminary report is in the Microsoft 365 admin center under incident IDs EX1550543 and MO1550821. Admins can go straight to Service health in the admin center (sign-in required) and look under Issue history.
- Microsoft's announcement that the preliminary report is available, from the Microsoft 365 Status account.
- An abridged public summary of the root cause from Charles Lamanna, Microsoft's executive vice president for Copilot, Agents, and Platform.
- Microsoft's public service status page for current service health, and the Microsoft 365 Status account on X for live incident updates.
We're here
Questions, or need a hand with the records? Contact us at 833.456.6877, whether or not you're a Xcelocloud customer.
Kim Hershey is Director of Product Management at Xcelocloud, where she brings Fortune 500 structure and discipline to the product management team. She holds an MBA and certifications in Scrum Master, Scrum Product Owner, Kellogg Marketing Leadership, PMP-PMI, and Lean Six Sigma Green Belt. She excels in cross-functional leadership, handling complex projects across various technologies and markets. Kim spends her off-time with her family and books. Her favorite authors are George R.R. Martin, Ethan Wharton, and Kazuo Ishiguro.