The company stated that the disruption was caused by a large number of servers becoming unexpectedly unavailable. Microsoft clarified that the elevated load on its infrastructure was not driven by an increase in traffic, but rather by the absence of these servers, which shifted the workload onto the remaining systems. This strain contributed to connection errors across multiple regions, with the company confirming that the issue could affect Microsoft 365 service connectivity for users in any region.
Technical investigations revealed that the server failures may originate from a specific component responsible for automated health checks. When servers failed these checks, they were taken out of service. In response, Microsoft deployed a targeted change to bypass this component on a subset of servers, allowing them to successfully return to service. By 9:00 p.m. UTC, the company confirmed it was applying this fix more broadly and preparing an automated process to detect and restart unresponsive servers. Microsoft also paused all deployments and configuration changes as a precaution while reviewing recent updates for correlation with the event.
The outage impacted a wide range of Microsoft 365 services. Exchange Online, which provides back-end support for Outlook, was among the primary affected areas, initially showing problems in the Americas before expanding globally. Other affected services included Teams, SharePoint Online, Defender XDR, and Copilot 365. The Microsoft 365 admin center also experienced brief downtime, with the company directing users to alternative status updates if the primary portal was inaccessible.
Microsoft has not provided a specific timeline for full service restoration. As of the latest updates, the company is “aggressively pursuing all pathways to reduce impact” by restarting affected servers and validating alternative health check methods. It is also assessing whether reverting a small number of recent configuration updates could accelerate recovery. The incident highlights the critical reliance on automated infrastructure monitoring, as the failure of the health-check mechanism itself contributed to the scale of the outage.
Users across the globe reported frustration, with some noting that emails were not being sent or received, while others could not open their inboxes at all. The disruption extended beyond email to workplace messaging and productivity tools, affecting both enterprise and consumer users who rely on the Microsoft 365 suite for daily operations. Microsoft continues to post regular updates on its official status page and social media channels, tracking progress under incident identifiers EX1550543 and MO1550821.
The company emphasized that it is working to safely return all affected servers to service. While the initial spike in reports has subsided, Microsoft has not declared the incident fully resolved. The ongoing focus remains on stabilizing the infrastructure and ensuring that the bypass for the faulty health-check component is effective across the entire network. No data loss or security breach has been reported, with the issue strictly technical in nature, related to server availability and load distribution.
