Microsoft 365 Outage Hits Multiple Services

User reports flooded Microsoft today, as thousands of Microsoft 365 users discovered they could not access their email. Exchange Online accounts for 70% of the reported problems, with the M365 Admin Center (13%) and login failures (9%) rounding out the top complaints. The disruption is not isolated to a single region, with impact reported across the United States and abroad.

According to Microsoft's own service health data, the incident was formally logged 11:17 AM EST on November 12. The company confirmed that users may be unable to connect to their mailboxes in Exchange Online through multiple connection methods. 

Microsoft's service health updates paint a picture of an infrastructure under stress. In an initial disclosure, the company confirmed that affected systems were experiencing elevated load across multiple regions and that this load was "likely contributing to the connectivity errors" users were reporting. Engineers began restarting and repairing impacted infrastructure components to restore capacity while simultaneously evaluating options to redirect traffic to unaffected alternate infrastructure.

In a follow-up update, Microsoft reported that it had completed redistributing connection traffic across its worldwide infrastructure and was moving additional traffic off the affected systems to further reduce load. Affected servers are being restarted to return them to service. The company is also actively investigating whether the elevated traffic reflects a genuine surge in user requests or a shift in how traffic is being internally routed across its own infrastructure, a distinction that matters considerably for how Microsoft ultimately resolves the issue.

What Microsoft Knows and What It Doesn't

The fact that Microsoft is still working to determine whether the traffic increase is real or a routing anomaly points to how early the diagnostic phase still is. If legitimate user demand caused the overload, the fix likely centers on capacity expansion and load balancing. If the cause is a misconfiguration or an unexpected shift in internal routing behavior, the resolution path looks different and the risk of recurrence without a root-cause fix is higher.

This ambiguity is not unusual in the early hours of a large-scale cloud incident, but it does mean organizations cannot yet plan around a firm resolution window. Microsoft's last update indicated a follow-up was expected by 4:00 PM EST on November 12, though that window has now passed without a public resolution announcement as of this writing.

What Organizations Should Do Now

With no confirmed resolution timeline in place, IT administrators and business owners should take a few immediate steps:

• Admins should monitor the Microsoft 365 Service Health dashboard under Health > Service health in the admin center for tenant-specific status updates, as the impact scope can vary by region and service plan.
• Teams with time-sensitive workflows dependent on Exchange Online should activate any available backup communication channels, including Microsoft Teams if it is unaffected in your tenant, or secondary email accounts.
• Document the business impact now, including any affected workflows, missed communications, or compliance-sensitive delays, in case the incident needs to be referenced for SLA purposes or regulatory reporting later.

The situation is actively developing, and Microsoft has committed to providing additional updates as its investigation progresses. You can check out Downdetector for updates and more info.