Microsoft 365 outage blocks Outlook inboxes worldwide as infrastructure hits elevated load

What happened

Microsoft's Outlook email service went down on November 12, 2026, leaving users unable to open their inboxes. According to TechCrunch, Microsoft initially scoped the problem to the U.S. and the Americas, but later widened its advisory to cover any region.

The company did not name a root cause. In a post on X intended for customers who could not reach the admin center, Microsoft said a portion of its infrastructure was under elevated load and that it was redistributing connection traffic across its broader worldwide footprint to balance it, TechCrunch reported. Complicating communication, the Microsoft 365 admin center — where status updates are normally published — was itself unreachable at the time of publication.

How the incident escalated

Status updates from Microsoft, quoted in a Hacker News thread that tracked the service health page, show the incident widening over roughly fifty minutes:

At 18:10 UTC, Microsoft confirmed connectivity errors on the portion of Exchange Online infrastructure that receives and processes users' access requests. Potentially affected connection methods included Outlook on the web, MAPI, Exchange ActiveSync and the REST API — meaning browser clients, desktop mail apps, mobile devices and third-party integrations were all exposed.

At 18:32 UTC, the advisory was broadened from mailboxes to multiple Microsoft 365 services, with Exchange Online, Microsoft Teams, SharePoint Online, Microsoft Copilot 365 and Microsoft Defender XDR listed as potentially impacted. Microsoft said the affected infrastructure was experiencing elevated load across multiple regions, that it was restarting and repairing impacted portions to restore capacity, and that it was reviewing an unexpected increase in a specific type of service traffic as a possible contributor.

By 18:59 UTC, Microsoft said it had completed redistributing connection traffic across its worldwide infrastructure and was moving additional traffic off the affected systems while restarting servers. In parallel, it was investigating whether the elevated traffic reflected a genuine increase in requests or a shift in how traffic was being routed across its infrastructure.

The original Hacker News poster also noted that the status page itself was loading extremely slowly during the incident, and that the RSS feed was a more reliable way to follow updates.

Broader impact

Beyond Microsoft's official list of affected services, commenters in the same Hacker News thread reported problems with Teams and OneDrive, while one commenter claimed consumer Microsoft 365 Family services were still functioning normally — which, if accurate, would suggest that product runs on separate infrastructure. Those reports are unverified.

The thread also raised a structural point: because products like Teams and OneDrive are built on top of Exchange and SharePoint plumbing, a failure in that shared layer can ripple outward into services that appear, on the surface, to be distinct products.

Recent history

This is not an isolated event. As TechCrunch notes, Microsoft's last major incident came in September, when a days-long outage hit Microsoft 365. The company attributed that disruption to a core authentication configuration issue that prevented users from signing in and using the suite, which includes Outlook.

It remains unclear how long the current outage will last. Microsoft's own status update committed to a next update by 20:00 UTC.

Why it matters

Microsoft 365 functions as core infrastructure for a large share of the world's businesses, and this incident illustrates the concentration risk that comes with that. When a single layer of Exchange Online infrastructure comes under excessive load, email, chat, document storage, Copilot and security tooling can degrade together rather than failing independently.

The incident also shows how communication channels can become collateral damage: with the admin center unreachable and the public status page barely loading, affected IT teams had to rely on social media posts and third-party forums for information. For organisations that plan around cloud productivity suites, out-of-band status channels are becoming as important as the services themselves.

Finally, coming barely two months after the September incident, a second high-profile disruption adds to pressure on Microsoft over the resilience of its platform, whatever the eventual root cause turns out to be.