Here's what Microsoft confirmed, what's still unknown, and what admins and users can reasonably do while they wait.
What Microsoft actually said
The first public acknowledgment came from the Microsoft 365 Status account on X. Microsoft said it was investigating reports of users experiencing issues accessing Exchange Online mailboxes through multiple connection methods in the Americas, and it sent admins to incident EX1550543 in the Microsoft 365 admin center. Variety reported that this post went out at 12:54 p.m. ET.
Microsoft then widened the scope. According to reporting by Click2Houston, the company said: "While we're working to mitigate impact, we've confirmed the issue may affect Microsoft 365 service connectivity for users in any region." Deadline carried the same statement, along with a follow-up saying that part of Microsoft's infrastructure was under elevated load across multiple regions, which was likely contributing to the connectivity errors.
A later service-health update, mirrored on the 365Fanatic status tracker and timestamped 19:27 CET (18:27 UTC, or 1:27 p.m. ET), described the mitigation work in progress. Microsoft said it was:
- Restarting and repairing the affected parts of the infrastructure to restore capacity
- Looking into an unexpected increase in a specific type of service traffic to see whether it was driving the load
- Considering moving traffic to alternate infrastructure to speed up relief
That update promised its next communication by 8:30 p.m. UTC on November 12. None of the material reviewed for this piece shows that a root cause was confirmed or that the incident was resolved, so treat the "unexpected traffic" lead as a hypothesis under investigation, not a diagnosis.
Section summary: Microsoft confirmed an Exchange Online mailbox-access problem that started in the Americas, then said Microsoft 365 connectivity could be affected in any region. Its working theory is elevated load on shared infrastructure.
Which connection methods were hit
The most useful technical detail came from the University of Tennessee at Chattanooga's IT status blog, which reposted Microsoft's service-health text. The potentially impacted connection methods may include Outlook on the web, Messaging API (MAPI), Exchange ActiveSync (EAS) and Representational State Transfer (REST) API. In plain terms:
| Connection method | What typically uses it |
|---|---|
| Outlook on the web | Browser access to a work mailbox |
| MAPI (over HTTP) | Classic Outlook for Windows connecting to Exchange Online |
| Exchange ActiveSync | Many phone mail apps and built-in mobile mail clients |
| REST API | Modern clients and integrations that call mailbox data over APIs |
Microsoft also said it had identified connectivity errors occurring on a portion of Exchange Online infrastructure which receives and processes users' access requests. That explains why switching from desktop to browser to phone probably didn't help anyone: every route goes through the same front door, and the front door was the part that was struggling.
When it started
Deadline and Variety published at 18:37 and 18:39 UTC, but the trouble began earlier. The Statusfield tracker, which reads Microsoft's service-health feed, shows a serviceDegradation entry at Nov 12 · 17:17 UTC titled "Users may be unable to connect to their mailboxes in Exchange Online through multiple connection methods". At that point Statusfield also listed both Exchange Online and SharePoint Online as degraded.
Approximate timeline (UTC / ET):
- 17:17 / 12:17 p.m.: The Exchange Online mailbox-connectivity entry shows up in the service-health feed.
- About 17:39 / 12:39 p.m.: Variety, citing Downdetector, says Outlook problem reports started spiking.
- 17:54 / 12:54 p.m.: Microsoft 365 Status posts on X and references EX1550543 (Variety's timing).
- 18:27 / 1:27 p.m.: The service-health update describes elevated multi-region load and the mitigation steps.
- 20:30 / 3:30 p.m.: The next update Microsoft committed to in that notice.
One small correction to the coverage: Variety said the outage happened on Wednesday. November 12, 2026, was a Thursday, which matches Deadline, local broadcasters and Microsoft's own update text.
How big was it?
The disagreement starts here. Variety cited Downdetector as showing more than 129,000 error reports by 1:09 p.m. ET. Lexington station WKYT, also citing Downdetector, said reports began appearing around noon EST Thursday, and by 1:30 p.m. EST, over 12,000 reports had been submitted. Those numbers differ by a factor of ten. Downdetector counts move quickly and depend on how a site's dashboard is filtered and captured, so readers should take both as rough signs of a large spike, not a measurement.
"Nationwide" needs the same caution. Microsoft's own wording started with "the Americas" and moved to "any region." Neither phrase gives a map, a count of affected tenants, or a percentage of users. Microsoft's language supports a widespread incident, but none of the available evidence quantifies how many organizations actually lost access.
Outlook was "up" while business email was down
Deadline captured a nuance that matters to Windows users: it reported that Outlook as a stand-alone service was deemed operational, as were Teams and OneDrive, while enterprise and business Microsoft 365 customers had trouble connecting to email through Exchange. A personal Outlook.com account and a work mailbox in a Microsoft 365 tenant are different things, even when you open them in the same app.
Exchange Online is the server side, and Outlook is the client. A Microsoft 365 status tracker describes Exchange Online as Microsoft 365's hosted email and calendar service. That tracker also notes it does not cover self-hosted Exchange Server installations. So organizations running on-premises Exchange should not have been affected by this particular incident unless their hybrid setup sends traffic through the cloud.
Other services were caught up too. The 365Fanatic mirror of the multi-region update listed it as an issue affecting multiple Microsoft 365 services. Variety reported that Teams and Copilot were affected. WKYT reported that the disruption is also affecting scheduling and messaging in Microsoft Teams, and Click2Houston said the company also reported a separate issue Thursday affecting Microsoft Teams functionality in North America. Whether that Teams problem was part of the same event or a coincidence wasn't clear from the material available. That's worth watching when Microsoft publishes its post-incident report.
What admins should do now
This is general IT practice, not Microsoft-issued guidance for this incident:
- Check the admin center first. In the Microsoft 365 admin center, open Health > Service health and look for EX1550543 and any related multi-service entry. Tenant-specific notes there carry more weight than headlines or Downdetector.
- Tell users early. UTC's IT team posted a short notice saying users may experience issues accessing Outlook and other Microsoft 365 applications this afternoon. A note like that heads off a pile of duplicate tickets.
- Don't change anything on endpoints. Reinstalling Office, rebuilding Outlook profiles or resetting passwords won't fix a server-side capacity problem, and they can leave you with a second set of problems after service returns.
- Plan for a backup channel. If Teams is shaky too, decide ahead of time where urgent communication goes: phone trees, SMS, or a non-Microsoft fallback.
- Watch for after-effects. Once access returns, look for help-desk reports of sync lag, missing calendar updates or stuck items in Outbox folders.
What users can try
- Classic Outlook in Cached Exchange Mode (the usual default) keeps a local copy of your mailbox, so you can often still read and search older mail offline. That's general Outlook behavior, not something Microsoft documented for this incident.
- Don't keep hitting Send. An outgoing message may be sitting in the Outbox. Resending it repeatedly can produce duplicates once things recover.
- Check whether it's your account type. If personal Outlook.com works but your work mailbox doesn't, that matches the business-tenant pattern Deadline described.
The bigger picture
Concentration risk explains why one "elevated load" message can stall half a workday. When email, chat, files and AI assistants all depend on the same cloud backbone, a capacity problem in one layer spreads to all of them. Microsoft's response shows the standard playbook: restart, repair, look for unusual traffic, and move load elsewhere. Still, the hint about an unexpected surge in a specific type of traffic deserves a clear explanation in the post-incident report. Was it a bad deployment, a misbehaving client, or something external? Customers paying per seat for productivity tools should expect a real answer.
Variety's "massive outage" and Deadline's "paralyzing" both describe something real for anyone who couldn't reach their inbox. The verified record is narrower and more technical: an Exchange Online front-end connectivity problem, labeled a service degradation, that Microsoft says could reach users in any region and was still under active mitigation at last report. Keep the incident ID handy and watch for the closing notice.