In short
- On November 12, 2026, Exchange Online stopped letting many users open their mailboxes in Outlook on the web, the desktop app and on phones. Email arrived late, and more than a dozen Microsoft 365 services that depend on Exchange failed with it. Microsoft tracks it as EX1550543 and MO1550821.
- Service came back about 24 hours later, at 11:10 a.m. Eastern on Friday, November 13. The cause, per Microsoft: routine network maintenance exposed a hidden bug in the systems that open connections to Exchange Online, and requests piled up until the servers could not accept new ones. It was not a cyberattack.
- It is the third major Microsoft 365 email outage this year. You cannot prevent outages, but you can decide ahead of time how your team keeps working and how customers reach you.
Shortly after 11 a.m. Eastern on Thursday, November 12, a lot of offices lost their email at the same moment. Outlook would not open the mailbox, the web version kept loading, phones stopped syncing, and calendars and meeting scheduling in Teams stopped working. If your business runs on Microsoft 365, and ours does, you felt it.
What happened
Microsoft logged the problem as EX1550543 in the Microsoft 365 admin center, with an official start time of 16:17 UTC (11:17 a.m. Eastern). The title: “Users may be unable to connect to their mailboxes in Exchange Online through multiple connection methods.” It first described the issue as being “in the Americas” and later said it could affect users in any region.
The affected access paths, according to Microsoft, were Outlook on the web, Outlook for desktop, Exchange ActiveSync (which most phone mail apps use) and the REST API that other apps use to read mail. A second incident, MO1550821, covered everything else that depends on Exchange:
- Email delivery “may be delayed”, in Microsoft’s words.
- Teams: calendar and meeting scheduling failed. Chat and online meetings “remain largely functional”.
- Copilot could not load or reach email, calendar and files.
- The admin center and the Defender portal had pages that would not load, which made it harder for IT to see what was going on.
- Safe Links in Defender for Office 365 may have been unable to check links clicked in Outlook and Teams.
- Also affected: Planner, To Do, Purview, Intune, Universal Print and parts of SharePoint that depend on Exchange.
What went wrong, according to Microsoft’s updates during the day: it was not extra traffic. Servers began failing their automated health checks and dropping out of service, and the remaining ones could not carry the load. Microsoft later found that “a process on the affected servers responsible for establishing secure connections becomes overwhelmed, causing the servers to stop processing requests.” It paused all deployments, restarted and rebuilt servers, limited some types of traffic in specific locations, and began reverting “a recent network configuration change that correlates with the start of impact”.
Recovery was slow. Servers brought back in the afternoon became unresponsive again as soon as they took traffic. By 8:45 p.m. Eastern, almost ten hours in, Microsoft reported “positive results” from restarts and was watching stability before expanding the fix. By Friday morning, nearly a full day in, Microsoft reported recovery in Europe, Japan more stable and North America improving, with “intermittent issues” still possible. It also said it had “no evidence of malicious activity” and promised a full post-incident report with the root cause.
Microsoft set the official end at 11:10 a.m. Eastern on Friday, November 13, about 24 hours after it started, and kept clearing the backlog of delayed mail into Friday night. Its final update said this “was a technical issue not related to cyber or AI / agents.” The cause, in Microsoft’s words: “traffic shifts during standard network maintenance and upgrades exposed a latent bug causing a rapidly increasing number of requests to queue for processing.” In plain terms, routine network work exposed a hidden bug in the systems that open connections to Exchange Online. Requests piled up faster than the servers could handle them, until they ran out of capacity and stopped accepting new connections. Microsoft traced it to an earlier network capacity upgrade, and said it brought service back gradually, checking stability at each step, which is why it took so long. On Sunday night it published its post-incident report, which Microsoft 365 administrators can read in the admin center.
Did you lose any email?
Microsoft’s incident says email delivery “may be delayed”, not lost, and it extended the time its servers keep retrying delayed messages to 48 hours “to help protect delayed messages as delivery catches up”. That is how email normally behaves: when a receiving server cannot accept a message and answers with a temporary error, the sending server keeps the message and retries, usually for hours and up to several days. The message arrives late, but it arrives. Only a permanent error produces a bounce.
Two practical points:
- If someone tells you they got a bounce from you during the outage, ask them to send it again.
- Expect a flood of late messages when your mailbox comes back, and look at the time each one was sent before you act on it. A “please pay today” that arrives six hours late may already be stale, or may have been followed by a correction.
If you use Outlook on your computer in the default cached mode, the messages already downloaded stayed readable during the outage. You just could not receive new ones.
Where to check the real status
- Service health in the Microsoft 365 admin center (Health, then Service health). This is where Microsoft posts the incident number, what is affected and the next update time.
- status.cloud.microsoft, Microsoft’s public status page, for when the admin center itself is not loading, as happened this time.
- The @MSFT365Status account on X, which posts the same updates.
Downdetector is useful to confirm you are not the only one, but it counts complaints, not affected users, and it says nothing about cause or timing.
Watch out for the follow-up phishing
Every big outage brings emails that look like they come from Microsoft: “Your mailbox was affected by the recent service disruption, sign in to restore your messages”, or “verify your account to recover undelivered mail”. Microsoft does not ask you to sign in through an email link to fix an outage. When it is over, your mail is simply back.
This time there is one more reason for care: for part of the outage, Safe Links may not have been able to check the links people clicked. If something like that lands in your inbox in the next few days, do not click. Open Outlook or office.com the way you normally do, or check the message first with our free email analyzer.
A plan B for the next one
This is the third big Microsoft 365 email outage of 2026, after January 22 (MO1221364) and August 31 (EX1464935). You cannot prevent the next one, but an hour of preparation changes how it goes:
- A way to reach your team that does not depend on Microsoft. This time Teams chat mostly worked, but calendars did not, and in other outages Teams went down with email. A text message group or a phone list kept outside Microsoft 365 is enough.
- Your key contacts somewhere else too. Main customers, suppliers and your IT provider, on paper or in your phone, not only in Outlook.
- Today’s calendar somewhere else. When the calendar will not open, nobody knows who has a meeting at 2. A quick daily look, or a shared copy, helps.
- A way to tell customers. A short note on your website or social media (“our email is delayed, call us at…”) saves a lot of confused calls.
- Know who is watching. Someone should check Service health, tell the team what is going on, and confirm when it is over.
- A copy of your Microsoft 365 data. An outage like this one does not usually delete data, but a backup outside Microsoft protects you from the problems that do, like accidental deletion or ransomware.
The bigger point
Moving email to the cloud was the right call for almost every small business: no server in the closet, no patches, better security. But it also means that when Microsoft has a bad day, you do too, and there is nothing to restart on your end. That is why the plan matters more than the platform.
It has also been a busy month for Microsoft email: last week Outlook.com began bouncing mail from domains without DMARC. If you want someone watching your Microsoft 365, with backups and a continuity plan in place before the next outage, that is part of our managed IT and business continuity services. Or talk to us.
Sources: Microsoft 365 Service Health, incidents EX1550543 and MO1550821 (as mirrored by the University of Pennsylvania), Microsoft 365 Status (first update), Microsoft 365 Status (mitigation), ABC News, WGCU.
Frequently asked questions
Was Microsoft Outlook down on November 12, 2026?
Yes. Starting at 11:17 a.m. Eastern, many Microsoft 365 users could not open their Exchange Online mailboxes in Outlook on the web, the desktop app or on mobile, and email arrived late. Microsoft tracked it as EX1550543 and MO1550821. Microsoft set the end at 11:10 a.m. Eastern on Friday, November 13, about 24 hours later.
What caused the Microsoft 365 outage?
Microsoft says routine network maintenance exposed a latent bug in the systems that establish connections to Exchange Online. Requests queued faster than they could be processed until the servers ran out of capacity and stopped accepting new connections. It was not a traffic spike and not a cyberattack.
Will I get the emails sent to me during the outage?
Microsoft said email delivery may be delayed, not lost. When a server cannot accept mail temporarily, the sender’s server retries for hours or days, so messages arrive late. If someone got a bounce, ask them to resend.
How do I check if Microsoft 365 is down?
Look at Service health in the Microsoft 365 admin center, or at status.cloud.microsoft if the admin center does not load. The @MSFT365Status account on X posts the same updates.
