← All Posts
MicrosoftOutageCloud

Microsoft 365 Outage: Exchange Online Incident EX1550543

November 13, 2026

Microsoft is dealing with an Exchange Online connectivity incident, tracked as EX1550543, that cut off Outlook mailbox access for many users on November 12. Microsoft's working explanation is elevated load on part of the infrastructure that handles user access requests, but it hasn't published a root cause. This article reflects what was public on the evening of November 12 (UTC), so check the Microsoft 365 admin center for the latest status.

Key Takeaways

  • Microsoft says users couldn't reach Exchange Online mailboxes through several connection methods, first in the Americas and later possibly in any region.
  • Microsoft's working explanation is higher than normal load. No root cause has been confirmed.
  • Reports of trouble with Teams, OneDrive and Copilot also appeared, but how they connect to this incident isn't established.
  • Downdetector counts show how many people reported problems, not how many were affected.

What happened to Microsoft 365 and Outlook?

TechRadar's live blog has outage reports starting around 12:30 PM Eastern on November 12, with Outlook complaints on Downdetector peaking above 131,000. Euronews puts the most visible Outlook disruption in the US at about 1:30 PM Eastern and says the Americas were hit hardest.

People reported trouble sending and receiving email and opening mailboxes, and Euronews also mentions delivery delays. Microsoft's own status page reportedly would not load for part of the afternoon, according to TechRadar.

What has Microsoft said about the cause?

Microsoft acknowledged the problem through its Microsoft 365 Status account and the admin center under incident ID EX1550543. KSAT reports that Microsoft said it was working to reduce the impact, that the connectivity problem could affect users in any region, and that it had started spreading connection traffic across its wider global infrastructure to balance the load.

The PennO365 incident log, which relays Microsoft's updates, adds more detail. According to that log, Microsoft traced the errors to the part of the infrastructure that handles user access requests and attributed them to elevated load across several regions. It then restarted and repaired affected infrastructure, moved some US traffic away, and noted that servers were intermittently going offline, adding strain. It was also checking recent changes for the source of the traffic increase. The same log moved related issues in other Microsoft 365 services to a separate incident, MO1550821.

Euronews also quotes Microsoft attributing the connection errors to infrastructure running under higher than normal load. A community write-up on WindowsForum lists Outlook on the web, MAPI, Exchange ActiveSync and the REST API as the affected access methods. Treat its timeline with care, though: its timestamps and the university log's don't line up, so I'm not quoting exact times from either.

Was this an outage or a degradation?

The WindowsForum write-up says Microsoft classified EX1550543 as a service degradation rather than a full outage. For users it felt like an outage, and reports varied by account type. Deadline reported that standalone Outlook worked while business Exchange connectivity did not, but that's a press report, not a Microsoft statement.

Do we know why Teams, OneDrive and Azure showed problems?

Not really. Downdetector showed reports for Teams, OneDrive, Copilot and Microsoft Store, and TechRadar notes that Azure issues were reported too. TechRadar also says Cloudflare, Google and Gmail showed up on Downdetector, likely as knock-on reports, with no other evidence of outages there.

Euronews says Microsoft reported Teams issues as resolved in North America, but some users still had connection problems. Whether the Teams reports belong to the Exchange incident hasn't been confirmed.

What should admins and developers do right now?

  • Watch EX1550543 and MO1550821 in the Microsoft 365 admin center's service health view rather than relying on social media.
  • Tell your users early. It cuts down on duplicate support tickets.
  • Hold off on client-side fixes such as reinstalling Office, rebuilding profiles or resetting passwords. The problem is on Microsoft's side, and WindowsForum's advice to avoid these is general practice, not Microsoft guidance for this incident.
  • Don't resend important messages repeatedly, since that can create duplicates once service recovers.

If your own apps call Exchange Online, expect failed or slow requests while Microsoft shifts traffic. Retry with backoff, and don't treat a timeout as proof that a message wasn't sent. That's my advice, not Microsoft's.

Wrapping Up

Microsoft hasn't named a root cause, so the open questions are what caused the extra load and why it spread across regions. Wait for the post-incident report, and in the meantime make sure your team has a backup channel that doesn't depend on Microsoft 365.

Sources

Frequently Asked Questions

What is Microsoft incident EX1550543?

It's Microsoft's tracking ID for the November 12, 2026 Exchange Online connectivity problem, in which users couldn't reach mailboxes through several connection methods.

What caused the Microsoft Outlook outage?

Microsoft hasn't confirmed a root cause. Its working explanation is higher than normal load on part of the infrastructure that handles user access requests, and it was checking recent changes for the source of the extra traffic.

Which regions were affected?

Microsoft first described the Americas and later said the connectivity issue could affect users in any region. Reports and Downdetector counts were concentrated in the US.

Were Teams and Copilot down too?

Users reported problems with Teams, OneDrive and Copilot, and Microsoft said Teams issues were resolved in North America. Whether they were part of the Exchange incident isn't confirmed.

Is the Microsoft outage fixed?

The sources I read didn't confirm a full resolution when I wrote this. Check the Microsoft 365 admin center service health page for the latest status.