On Thursday, 12 November 2026, Outlook, Teams, Copilot and other Microsoft 365 services went down for users around the world, and parts stayed slow into Friday. This explainer covers what broke, what Microsoft has said so far about the cause, who was hit, why delayed emails are still arriving, and what you can do the next time your work email disappears.
Everything here is as of Saturday, 14 November 2026 (around 14:30 UTC). At that time, Microsoft’s public status page listed all products as operational. Microsoft hasn’t yet published its full post-incident report, so the cause below is only what the company has said publicly so far.
What happened, in short
- Start: Microsoft says the Microsoft 365 incident began at 1:26 PM ET (18:26 UTC) on 12 November. Before that, it had been looking into Exchange Online mailbox problems in the Americas earlier the same day. User reports on Downdetector spiked around the same time, though different outlets give slightly different start times.
- What broke: Microsoft’s admin advisory (MO1550821) said customers might not be able to reach Exchange Online, Teams, SharePoint Online, Microsoft 365 Copilot and Microsoft Defender XDR. A separate Exchange Online incident was tracked as EX1550543.
- Scale: According to CBS News, as cited by Quartz, Downdetector logged reports from 74 countries and territories. Roughly 130,000 users reported Outlook problems at Thursday’s peak.
- Recovery: By Friday morning, Microsoft reported “encouraging recovery progress”. By Friday evening most people could send and receive mail again, though XDA said Outlook was still slow for some.
- Not a hack: Microsoft said it found “no evidence of malicious activity” and called it a technical issue.
What caused it (so far)
Microsoft’s own updates, as reported by BleepingComputer and SecurityWeek, tell the story in stages:
- At first, Microsoft blamed “elevated infrastructure load across multiple regions.”
- It then said the load wasn’t from extra traffic. Instead, “a number of servers being unexpectedly unavailable” left the remaining servers carrying the work.
- Affected servers were failing automated health checks. A core process on them, which SecurityWeek describes as the process that sets up secure connections, was getting overwhelmed, so the servers stopped handling requests.
- Microsoft began rolling back a recent network configuration change that coincided with the start of the problem. It also restarted servers and moved traffic to other routes.
Microsoft says it will publish “a full Post-Incident Report with root cause and defense-in-depth actions” once mitigation is complete. Until then, treat any single explanation as unconfirmed. That includes reports pinning the outage on a particular network change.
A smaller Teams outage hit North and South America earlier on Thursday, from 9:45 to 10:53 AM ET (tracked as TM1550488). Microsoft blamed resource contention for that one and said it was fixed. It hasn’t said whether the two incidents are connected.
Who was affected
Because Microsoft 365 runs email for so many businesses and governments, the effects spread well beyond office workers who couldn’t log in. According to reports gathered by Quartz from CBS News, CNN and The Wall Street Journal:
- The US House of Representatives was disrupted, and its engineers worked with Microsoft.
- Singapore’s government email went down. The Philippines’ Supreme Court said email and other operations were affected. Japanese government staff made paper copies of documents.
- Maersk couldn’t send some emails and alerts. Euronext stopped receiving mail from some clients, though its markets ran normally.
- IndiGo’s email support was disrupted, but flights weren’t. Air India rerouted its email.
- An email problem at the UK’s National Health Service was expected to delay some prescriptions.
- AI assistants that connect to Microsoft accounts had trouble too. OpenAI warned that new connections through its Microsoft connectors might fail, and Anthropic reported problems with its Microsoft 365 connector and Claude for Outlook.
SecurityWeek also noted that some Google Workspace users had trouble getting their Gmail-hosted mail through the Outlook apps.
Why old emails are still turning up
When a mail server can’t deliver a message, the sending system usually keeps it in a queue and retries for a while before giving up. To stop delayed messages from being thrown away, Microsoft extended its email timeout window to 48 hours. That’s why some people saw Thursday’s emails trickle in on Friday and later.
What this means for you:
- Don’t resend everything at once. Many messages sent during the outage were delivered late rather than lost.
- Check for bounce messages. If you got a “delivery failed” notice (a non-delivery report), that message really didn’t arrive, so send it again.
- Confirm anything time-sensitive. For invoices, contracts or deadlines sent on 12–13 November, check with the other person that it arrived.
What to do next time Microsoft 365 goes down
Step 1: Check if it’s just you
Open Microsoft’s public status page at status.cloud.microsoft. It covers consumer products and links business users to the admin centre. Downdetector and the official Microsoft 365 Status account on X are also useful, since Microsoft posted updates there throughout this outage.
Step 2: If you’re an admin, use Service health
Business and enterprise admins see the detailed incident notes, with IDs like MO1550821, on the Service health page in the Microsoft 365 admin center. Those notes are more detailed than the public page and tell you which features are affected.
Step 3: Try another way in
During this outage, some parts of Microsoft 365 that didn’t depend on Exchange Online kept working, according to Microsoft. If the desktop app won’t connect, try Outlook on the web or the mobile app, and the other way round. The Outlook desktop app may also still show mail that it had already downloaded.
Step 4: Have a backup channel
Agree in advance on how your team reaches each other if email and Teams are both down. A phone tree, a group chat on another service or a shared status document all work. Keep important contacts saved somewhere outside your work account.
Step 5: Watch out for scams
Big outages bring fake “reset your password” and “re-verify your mailbox” emails. Be suspicious of any message that says you must sign in again or reset your password “because of the outage”. Don’t click login links in unexpected emails. Go to the site directly instead. Our guide to what to do after a data breach notice covers more of the basics.
Common questions
Was it a cyberattack? Microsoft says no. It found no evidence of malicious activity. It came two days after Microsoft’s November Patch Tuesday, but Microsoft hasn’t linked the outage to any of those updates.
Is it fixed? As of 14 November, Microsoft’s public status page showed all products operational. Some users had still reported slow Outlook and delayed mail into Friday night.
Was this related to the US flight ground stop? There’s no sign of a link. The FAA’s nationwide ground stop the same week was a separate air traffic control problem. Read our explainer on why every US flight was grounded.
Will businesses get compensation? Microsoft hasn’t announced anything. Business customers can check the service credit terms in their Microsoft 365 agreement once the post-incident report is out.
Wrap-up
A chunk of servers dropped out, the rest couldn’t carry the load, and email around the world slowed to a crawl for more than a day. The full root cause is still to come in Microsoft’s post-incident report. In the meantime, check that important messages from 12–13 November actually arrived, and set up a backup channel before the next outage.
Sources
Links last checked on 15 November 2026.
- BleepingComputer: Massive Microsoft 365 outage disrupts Outlook, Teams, Copilot worldwide (updated 13 November 2026)
- SecurityWeek: Microsoft 365 Outage Disrupts Outlook, Exchange Online and Teams
- Quartz: Microsoft is still working to fix a 2-day global outage
- XDA: Microsoft’s massive outage is mostly over
- Microsoft Service Health Status





Write a response