Microsoft is working to restore Microsoft 365 connectivity following a multi-region service disruption that initially affected Exchange Online mailbox access in the Americas before expanding into a potentially worldwide incident. According to updates from Microsoft’s official Microsoft 365 Status account, the disruption involves servers unexpectedly becoming unavailable, increasing the processing load on the remaining infrastructure and causing connectivity errors. Microsoft has acknowledged that users in any geographic region may be affected, although it has not disclosed the total number of impacted customers or the percentage of service capacity unavailable.

Microsoft’s investigation identified an infrastructure availability problem rather than an unexpected increase in customer traffic. A portion of its servers is failing automated health checks and becoming unavailable, leaving the remaining servers to handle a greater share of connection requests. Engineers have begun redistributing traffic across Microsoft’s worldwide infrastructure, moving connections away from affected systems and restarting servers to restore capacity. Microsoft has also paused deployments while testing a configuration change intended to address the health-check failures. The company has not yet identified the original trigger for the server failures or provided a definitive restoration timeline.

The incident is being tracked under service advisories EX1550543 and MO1550821 in the Microsoft 365 admin center. Microsoft initially reported Exchange Online mailbox connectivity problems involving multiple access methods in the Americas, but subsequently warned that Microsoft 365 service connectivity could be affected in any region. The company is directing administrators to its service health dashboard for updates as recovery proceeds. Its latest supplied statements indicate that remediation remains underway, with server restarts and infrastructure health monitoring continuing.

“We’re testing a configuration change to address a problem that’s causing servers to fail automated health checks and become unavailable.”

— Microsoft 365 Status (@MSFT365Status), November 12, 2026

Analysis

The disruption illustrates how automated health monitoring can become a critical dependency in large-scale cloud infrastructure. Health checks are designed to identify malfunctioning servers and remove them from service before they affect customers. However, when a shared health-check component fails across multiple servers, otherwise recoverable infrastructure may be removed from service simultaneously. The resulting capacity reduction can place additional pressure on surviving systems, potentially creating a cascading availability problem.

Microsoft’s recovery strategy combines traffic engineering with server-level remediation. Redistributing connection requests can relieve overloaded infrastructure, but it does not independently restore the capacity lost when servers become unavailable. Microsoft’s testing of a configuration change and controlled server restarts addresses the underlying availability problem. The incident also demonstrates why multi-region cloud deployments require both geographic redundancy and sufficient operational independence between shared infrastructure components.

For enterprise IT organizations, the disruption affects more than employee email. Exchange Online connectivity may use multiple client protocols and access methods, while broader Microsoft 365 connectivity can be disrupted when shared infrastructure is affected. The incident underscores the operational importance of monitoring SaaS dependencies and maintaining alternate communications channels during widespread service disruptions.

We’re tracking cloud infrastructure reliability, network availability and service disruptions at Converge Digest.