The year’s biggest outage had no villain, just servers failing their own health checks and a long night at Microsoft.
Around 11 AM Eastern yesterday, people across the Americas started losing access to their Exchange Online mailboxes. Within two hours, Downdetector reports for Outlook peaked near 140,000, with reports coming in from at least 74 countries. NBC News ran a live blog on it all afternoon, and New York City’s emergency management office warned residents that email to city agencies could be delayed.
This was not just email. Because so many Microsoft 365 services lean on Exchange Online, the outage spread to:
- Teams calendars and meeting scheduling
- SharePoint features, Copilot, Planner, and To Do
- Defender Safe Links, which started throwing errors on links in email and Teams
Is Microsoft Still Down?
As of Friday morning, November 13, Microsoft was still restoring service, more than 20 hours after the outage began. Some mailboxes are back, recovery has reached some regions before others, and Microsoft has warned that intermittent problems may continue.
The fastest ways to check right now:
- status.cloud.microsoft, which works even when you cannot sign in
- @MSFT365Status for Microsoft’s running updates
- Your Microsoft 365 admin center under incident IDs EX1550543 and MO1550821, if you manage your own tenant
One warning while you wait: do not reset passwords or reinstall Office. The problem is on Microsoft’s end, and fake “reset your password to restore access” emails are already circulating.
What Caused the Microsoft Outage?
The November 12 Microsoft outage happened when Exchange Online servers began failing Microsoft’s automated health checks and dropping out of service, which pushed their load onto the servers still standing, and those started buckling too. Overall traffic had not increased; capacity was disappearing. Later updates pointed to a process that sets up secure connections becoming overwhelmed, and Microsoft began rolling back a recent network configuration change that lined up with the start of the problem.
Worth repeating, because it is the first thing everyone asks: Microsoft has reported no sign of malicious activity. This was not a cyberattack.
What You Can Actually Do About It
Nobody in your office can fix Microsoft. What separates a rough afternoon from a lost day is what your business had in place before 11 AM:
- A communication plan that does not live in Microsoft. When email and Teams go down together, you need a way to tell your team what is happening. A text thread counts. Deciding on it in advance is the part that matters.
- Someone who knows where to look. The fastest way to lose a day is having everyone reinstall Office and reset passwords for a problem that is not on your end. Your IT provider should confirm within minutes that it is Microsoft, not you (this is a fifteen-minute panic we have talked several clients out of).
- A heads-up about the scams that follow. Outage-themed phishing shows up fast: fake “reset your password to restore access” emails that look exactly like a fix.
- Documentation for the SLA credit. Microsoft owes service credits when it misses its uptime commitment, but you have to claim them, with records of who was affected and when. Most businesses never do.
If yesterday turned into a lost afternoon at your company, it is worth a conversation about what a free IT assessment would catch before the next one.
When, Not If
Microsoft runs one of the most reliable platforms on earth, and it still lost a day. The lesson is not to leave Microsoft 365. It is that every business runs on somebody else’s servers now, and the ones that handle outages well decided how they would handle them in advance.



