The Microsoft 365 and Outlook outage of 12 to 13 November 2026: what happened, and was your email lost?

For almost a day, most people could not open their mailbox in Outlook, and email was delayed around the world. What Microsoft's own posts and its preliminary report say about the timeline, the cause and, most importantly, the mail that was in transit, plus the fake outage emails that followed.

Published Facts checked 5 min read
Timeline of the outage in UTC, from Microsoft's preliminary report and posts. 12 November, 16:20: impact begins. 17:54: Microsoft acknowledges mailbox access problems in the Americas, incident EX1550543. 18:07: users in any region may be affected. 13 November, 07:20: the fix starts to roll out. 13:00: queues of delayed email begin to shrink. 16:10: impact ends; queued mail processed. 14 November, 06:09: Microsoft says it has restored the remaining regions.
Times are UTC. Microsoft extended its delivery window so delayed mail was not bounced.

On 12 November 2026, a fault in the network gateway in front of many Microsoft 365 services left most people unable to reach their mailbox through Outlook, and email was delayed worldwide. Microsoft’s preliminary post-incident report gives the impact window as 16:20 UTC on Thursday 12 November to 16:10 UTC on Friday 13 November, under incidents EX1550543 and MO1550821. Microsoft says delayed messages were kept and delivered, not bounced.

In short:

  • Was email lost? Microsoft says it “extended the email delivery window to ensure delayed messages weren’t returned as undeliverable” and that “all messages that were queued for delivery during the event were processed.”
  • Was it a hack? No. Microsoft said: “This was a technical issue not related to cyber or AI / agents.”
  • Do you need to do anything? Usually not. If someone says a message never arrived, ask them to check for a bounce and send it again.
  • Watch out for fake outage emails. Within a day, phishing emails claimed that “held” messages would be deleted unless you clicked. See the fake Microsoft 365 outage emails.

What happened, in order

The times below are UTC, from Microsoft’s posts on its @MSFT365Status account and its preliminary report.

When (UTC)What Microsoft said or did
12 Nov, 16:20Impact begins (the start time in the preliminary report)
12 Nov, 17:54First public post: “investigating reports of users experiencing issues accessing Exchange Online mailboxes through multiple connection methods in the Americas” (EX1550543)
12 Nov, 18:07The problem “may affect Microsoft 365 service connectivity for users in any region”
13 Nov, 07:20A fix that “returned the code path to the previously known good state” starts to roll out
13 Nov, 12:09“The extended 48-hour email timeout window remains in place to help protect delayed messages as delivery catches up.”
13 Nov, 16:10Impact ends; Microsoft continued “ensuring that all queued mail had been processed”
14 Nov, 06:09“We have completed our efforts to address the underlying issue” for the remaining customers and regions

Mailbox access failed through “Outlook, Outlook on the web, Exchange ActiveSync, and Messaging and REST APIs”. The report lists Exchange, Copilot, Teams, SharePoint, OneDrive, Defender, Purview, Intune, Planner and other services among those affected. Microsoft’s report covers Microsoft 365 work and school services; it does not say whether personal Outlook.com accounts were affected.

Was your email lost?

Microsoft’s answer is no. Its repair list in the preliminary report includes, marked completed: “Extended the email delivery window to ensure delayed messages weren’t returned as undeliverable and all messages that were queued for delivery during the event were processed.”

So mail sent to a Microsoft 365 mailbox during the outage should have arrived late rather than bouncing. What Microsoft does not say is how every other company’s mail server behaved while it could not deliver: a sender’s own server may have given up after its own retry period. So:

  • If you were waiting for an email sent on 12 or 13 November, it should be in your inbox, dated when it was sent but delivered later. Use search rather than scrolling, since it may be further down than expected.
  • If a sender got a bounce (a “delivery failed” message) dated 12 or 13 November, ask them to send it again.
  • If you sent important mail during the outage, check that it left your Sent Items and that no bounce came back.

Mailtria’s email header analyzer shows when each server handled a message, which tells you whether a late email was held up in Microsoft’s queue.

What caused it

Microsoft’s preliminary report says the outage was caused by “three main factors that together caused a global outage for the networking gateway that fronts many Microsoft 365 services”. A Microsoft executive, Charles Lamanna, summarised it on X: a latent software defect, a large shift of traffic onto the shared gateway, and part of the server capacity already out of service. “At its lowest, more than 80% of servers were unresponsive.”

That also explains why Teams recovered before Outlook: “not all services, like Exchange Online, can fail out of this network gateway for scale reasons.”

Microsoft apologised the next day: “We are deeply sorry for the disruption this incident has caused our customers and partners.”

Do you need to fix anything in Outlook?

Microsoft’s report describes a fault in its own network and does not ask users to change anything in Outlook. Nothing in it suggests repairing or rebuilding Outlook files. If Outlook still shows connection errors now, the outage is over, so look for a different cause: your network, a sign-in prompt waiting in the background, or a new problem on Microsoft’s status page.

For administrators

  • The incident record is MO1550821 (and EX1550543) in Service health in the Microsoft 365 admin center. Microsoft says the final post-incident report, with “a comprehensive list of repair items”, is due on 20 November 2026.
  • Microsoft’s advice for checking any outage is to “confirm service disruptions directly through the Microsoft 365 admin center”, or the public status page if you cannot sign in.
  • Warn staff about the outage-themed phishing that started the next day.
Decision tree after the outage. Did you get an email saying messages held during the outage will be deleted unless you click? If yes, it is phishing: do not click, report it. Was a message sent to you on 12 or 13 November missing? If yes, search your mailbox; if it is not there, ask the sender to check for a bounce and resend. Is Outlook still failing to connect now? If yes, the outage is over: check Microsoft's status page, your network and any sign-in prompt. Otherwise nothing needs doing.

Not the same as the Outlook.com bounces

A week earlier, between about 5 and 10 November, mail to Outlook.com and Hotmail addresses was rejected with SPF errors because of a faulty spam rule, incident EX1545193. That was a different problem, with bounces that did need resending. Our article on the Outlook.com rejected emails covers it.

Frequently asked

Was my email lost in the outage? Microsoft says no: it extended its delivery window so that delayed messages “weren’t returned as undeliverable” and processed all queued mail.

When did the outage start and end? Microsoft’s preliminary report gives 16:20 UTC on 12 November to 16:10 UTC on 13 November. Microsoft posted that it had restored the remaining regions at 06:09 UTC on 14 November.

Was it a cyberattack? No. Microsoft said it “was a technical issue not related to cyber or AI / agents.”

I got an email about messages held during the outage. Is it real? Almost certainly not. Microsoft warned about a phishing campaign using that exact story. Do not click; see the fake outage emails.

Do I need to repair Outlook or my PST or OST file? Microsoft’s report describes a fault in its own network and does not ask users to repair anything.

Where is Microsoft’s full report? Administrators can find it under MO1550821 in Service health; the final version is due on 20 November 2026.

Sources

This article is general information, not legal, security or professional advice. Services change their rules and screens; check the official pages linked above before you act, and keep a backup before changing your mail.

Email Header AnalyzerSee who really sent an email and where it was delayed. It runs in your browser; nothing you paste is uploaded.
Open Email Header Analyzer