The News Central

Microsoft 365 Outage Hits 74 Countries, Disrupting Outlook, Teams, and Copilot

A widespread outage of Microsoft 365 services has affected users in 74 countries and territories, following a failure of automated server health checks

A widespread outage of Microsoft 365 services, including Outlook, Microsoft Teams, SharePoint, and Copilot, has affected users in 74 countries and territories, following a failure of automated server health checks that triggered a cascading drop in cloud capacity.

According to Microsoft, the Exchange Online incident began at 16:17 UTC, with user complaints on outage-tracking platform DownDetector surging worldwide within roughly an hour. By 18:25 UTC, reports about five Microsoft services combined reached 19,650 per minute, compared to fewer than 15 reports per minute on November 12. At the time of filing this report, the services were still down.

DownDetector reported that complaints for Microsoft 365, Copilot, Teams, and OneDrive each jumped more than a hundredfold, while Azure rose roughly a hundredfold. Consumer-facing and developer platforms owned by Microsoft, including Xbox, GitHub, and LinkedIn, saw comparatively minor spikes. Even Microsoft's public service status dashboard briefly went offline under the strain, and third-party AI providers, including OpenAI and Anthropic, reported connector failures affecting mail and calendar integrations.

Microsoft attributed the disruption to internal infrastructure failures rather than a cyberattack. A large pool of servers unexpectedly failed automated health diagnostics and dropped offline, causing a core process to become overwhelmed by elevated processor usage and resulting in healthy servers turning unresponsive in a domino effect.

To address the issue, Microsoft initiated restarts across affected machines and froze all routine software deployments and configuration updates. Engineers also rerouted user traffic onto alternative infrastructure pathways and deployed an alternative health-check method to allow restarted servers to safely rejoin the network.

By November 12 evening, complaint volumes on DownDetector had dropped from their afternoon highs to roughly 32,000 reports. In a subsequent update, Microsoft confirmed that recovery was underway, though it cautioned that full restoration would remain gradual. The company stated that it was returning a portion of affected servers to the service and shifting traffic to alternate routes wherever possible, with users expected to experience a gradual recovery as their clients reconnect.

The incident marks the third major Microsoft 365 disruption this year, following multi-hour outages in January and a code-update failure in August that took several days to fully resolve. Microsoft has provided updates on the status of the outage through its admin center and status.cloud.microsoft website, with further information available under incident numbers EX1550543 and MO1550821.

As the situation continues to unfold, users of Microsoft 365 services are advised to check the official status updates for the latest information on the outage and expected recovery time. The disruption has highlighted the importance of robust infrastructure and backup systems to minimize the impact of such outages on businesses and individuals relying on cloud-based services.

In the meantime, users are experiencing significant disruptions to their work and communication, with many taking to social media to express their frustration and concern. The outage has also raised questions about the reliability and resilience of cloud-based services, particularly in the face of increasing demand and dependence on these platforms.

Microsoft's efforts to restore services and provide updates on the outage are ongoing, with the company working to ensure that users can resume their normal activities as soon as possible. However, the incident serves as a reminder of the potential risks and vulnerabilities associated with cloud-based services and the need for providers to prioritize infrastructure resilience and redundancy to minimize the impact of such outages.

The company's response to the outage has been swift, with engineers working to address the issue and restore services. However, the incident has already had a significant impact on users, with many experiencing disruptions to their work and communication. As the situation continues to unfold, it remains to be seen how quickly Microsoft can restore services and minimize the damage caused by the outage.

In conclusion, the Microsoft 365 outage has highlighted the importance of robust infrastructure and backup systems to minimize the impact of such outages on businesses and individuals relying on cloud-based services. As the company works to restore services and provide updates on the outage, users are advised to check the official status updates for the latest information on the expected recovery time. The incident serves as a reminder of the potential risks and vulnerabilities associated with cloud-based services and the need for providers to prioritize infrastructure resilience and redundancy to minimize the impact of such outages.