Illustration of a Microsoft 365 outage with one failed app tile marked by a red X

Microsoft 365 Outage Explained: What Broke Outlook and Teams, and What Microsoft Says Caused It

The Microsoft 365 outage on November 12 locked huge numbers of people out of Outlook, Teams and Copilot, and Microsoft now says a network capacity upgrade caused it. It wasn’t a cyberattack, and the company says AI agents weren’t involved. Microsoft declared the incident fixed by November 14, though a full post-incident report is still pending.

If you want the 10-second version, start here:

  • The trouble began on Thursday, November 12, 2026, and reached at least 74 countries, according to TechRadar’s live coverage.
  • Outlook, Copilot and Microsoft 365 were hit hardest. Teams, OneDrive and Azure had problems too.
  • Microsoft’s preliminary cause: an issue from an earlier network capacity upgrade, which surfaced after a later network change.
  • Delayed email is the main lingering effect. Microsoft extended Outlook’s retry window to 48 hours.

The sections below cover what broke, why, and what you should (and shouldn’t) do now.

What the Microsoft 365 outage actually broke

Exchange Online took the biggest hit, which is why Outlook dominated the headlines. Downdetector reports for Outlook in the US peaked above 131,000, per TechRadar. Many people simply couldn’t open their mailboxes.

The damage spread outward from there, because a lot of Microsoft 365 leans on Exchange. Copilot Chat couldn’t always reach your mail, calendar or files, and Teams struggled with meeting invites and scheduling.

This table lists the main services and what users saw, based on an admin-focused timeline from Azure Blog UK.

Service What went wrong
Exchange Online Mailboxes wouldn’t open; email delivery was delayed
Teams Calendar scheduling, meeting invites and edits failed; core calling and chat were mostly fine
SharePoint Online External sharing problems; files could still be opened
Copilot Chat Sometimes failed to load or to reach mail, calendar and files
Defender, Purview, Graph Policy delays, portal access issues and request timeouts

If you ran into odd errors in more than one app that day, this is probably why. It’s one fault showing up in many places.

What Microsoft says caused it

Microsoft first blamed “elevated load,” which tells you very little. Its later explanation was that an issue during an earlier network capacity upgrade surfaced after a recent network change. Servers then failed automated health checks and dropped out of service.

Microsoft also said there is “no indication this is the result of malicious or cyber activity,” and that the problem wasn’t related to AI or agents. Those statements came from Microsoft itself, and the root cause is still preliminary until the full report lands.

Overnight, engineers began reverting the network configuration change and bringing servers back in phases. By the early hours of November 14 UTC, the incident was marked remediated, with the end time logged as November 13.

How the recovery played out

Recovery was slow because Microsoft had to bring servers back carefully rather than all at once. A new health-check method let some servers return to service on the evening of November 12.

By early November 13, Microsoft reported positive results and stretched Outlook’s email timeout window to 48 hours. That protects messages that couldn’t be delivered during the disruption, so anything sent to you during the outage should still arrive.

It’s a useful reminder that a “fixed” status page and a clean inbox aren’t the same thing. Backlogs take hours to drain after the cause is gone.

What to do now if you were affected

Here’s a short checklist for people who still see odd behavior or missing messages:

  • Check your Spam and Junk folders before assuming a message never arrived.
  • Resend anything urgent that you sent during the outage, and ask the recipient to confirm.
  • Don’t reinstall Office, rebuild your profile or change your password. None of that fixes a server-side fault.
  • Admins should save the post-incident report once published, since Service health keeps issue history for only 30 days.

That password point matters more than it looks. Outages are prime time for scammers, and TechRadar reports Microsoft says it won’t ask you to reset a password or click a link to restore Outlook access. If a message does, treat it as phishing, and our guide to the fake verification page scam shows how these pitches are built.

Why one network change can take down so much

Modern cloud suites are tightly coupled. One underlying layer, in this case mail and networking, feeds dozens of features you’d never connect to it. A fault there doesn’t stay put.

It’s the same pattern we saw when a single power event froze banks and courts in the Google Cloud London outage. The lesson for businesses is to keep a backup way to reach your team that doesn’t depend on Microsoft 365, even if it’s just a phone tree.

Frequently Asked Questions

Was the Microsoft 365 outage a cyberattack?

Microsoft says there’s no indication of malicious or cyber activity. It blamed a network capacity upgrade issue, though the full report isn’t out yet.

Did I lose emails during the outage?

Probably not. Microsoft extended Outlook’s retry window to 48 hours so delayed messages could still be delivered. Resend anything critical that you never got a reply to.

Is the Microsoft 365 outage over?

Microsoft declared the incident remediated on November 13 to 14. Some mail delays may have lingered while queues drained, so check Service health if you still see problems.

Can my company get a refund for the downtime?

Possibly. Microsoft’s service level agreement may allow service credits, but claims usually have a deadline. Your admin should check your agreement and file promptly.

The takeaway

Treat this as a free fire drill. Individuals should stay calm, ignore any “fix” emails and let the backlog clear. Businesses should use the pending post-incident report to ask a hard question: if Microsoft 365 vanishes for a day, how does your team actually talk to each other?


Comments

Leave a Reply

Your email address will not be published. Required fields are marked *