← All news

Microsoft 365 went down for a day. Here’s what happened.

November 16, 2026
A laptop showing an email inbox that won't load, with a row of mostly dark servers behind it

On Thursday, November 12, many people opened Outlook and found they couldn’t get to their email. For most of the next 24 hours, Microsoft 365 email was down or unreliable around the world, and new messages arrived hours late. Microsoft has now released its first report on what went wrong. Here’s what happened, in plain terms, and what it means for you.

What was affected

The trouble started around 11:20 AM Eastern on Thursday and lasted until about 11:10 AM Eastern on Friday, November 13.

  • Email took the biggest hit. Most people couldn’t open their mailbox in Outlook, Outlook on the web or the mail app on their phone, and incoming email was delayed.
  • Teams, SharePoint, OneDrive and Copilot had problems with features that depend on email, such as calendars and meeting invitations. Teams chats and meetings kept working for most people for most of the outage.
  • The severity varied by location and time of day, so some people saw partial access while others were completely locked out.

What caused it

This was a software problem on Microsoft’s side, not a hack. Microsoft says three things lined up at the same time:

  • A hidden flaw from an update in July. The update went to the servers that connect people to Microsoft 365, and it ran without trouble for more than three months. Under heavy enough load, though, it could make a server stop responding. Microsoft says this flaw only affected those specific servers, not regular Windows computers.
  • Extra traffic. The night before, Teams traffic was moved onto the same servers that handle email. That’s a normal step Microsoft takes to keep services running, but it added load.
  • Fewer servers than usual. About 14% of those servers were already out of service because of an unrelated issue from the day before.

Together, these pushed the servers over the edge during the busiest part of the U.S. workday. As each server stopped responding, its traffic moved to the next one, which then got overloaded too. Within about two hours, more than 80% of the servers had stopped responding.

Why it took so long to fix

Every time Microsoft brought a server back, the flood of people waiting to get in overloaded it again. Because the flaw came from an update months earlier, the usual quick ways of undoing a recent change didn’t apply. Microsoft’s engineers had to find the cause, build a fix that put the code back the way it was, and then apply it to large groups of servers one batch at a time. Email was the slowest to recover because, unlike Teams and OneDrive, it couldn’t be moved to a different set of servers.

What it means for you

  • Your email wasn’t lost. Microsoft held messages longer than usual so that email sent during the outage was delivered late instead of bouncing back.
  • Your account wasn’t hacked. Nothing on your computer or phone caused this, and there’s nothing you need to change.
  • If you were waiting on an important email from Thursday or Friday morning, it’s worth a quick check with the sender that it came through.

What to do next time

Outages like this are rare, but they do happen with every online service. A few simple habits make them easier to ride out:

  • Check whether it’s just you. Microsoft posts known problems at status.cloud.microsoft, and news of a large outage spreads quickly online.
  • Hold off on big fixes. Removing your email account, reinstalling Outlook or resetting your password won’t help during an outage and can leave you with extra setup to redo afterward.
  • Have a backup way to reach people. A phone number for key contacts, or Teams chat at work, can keep things moving while email is down.

Microsoft has promised a final report with longer-term fixes later this month. It has already added more capacity, extra monitoring and new safeguards meant to stop a problem on one server from spreading to the rest.

We can help

If we manage your Microsoft 365, we keep an eye on Microsoft’s service alerts, so we can tell you quickly whether a problem is on Microsoft’s end or yours. If something still isn’t working right after this outage, call us at (856) 566-1300 or send us a message.

Questions about this? We can help.

Call us or send a message and we'll get back to you quickly.