Microsoft experienced a major service disruption on Thursday that affected a large number of users globally. According to data from the outage tracking website Downdetector.com, the incident began shortly before 1 p.m. and quickly impacted key Microsoft 365 applications, including Outlook and Teams. At the peak of the issue, approximately 130,000 users reported difficulties specifically with Outlook.
The technical problems extended beyond Microsoft's own platforms. Users of Amazon Web Services and Google also logged outages on the same monitoring site, suggesting a broader connectivity issue or simultaneous technical challenges across different providers. This widespread nature led to numerous reports of service interruptions across various regions.
In response to the growing number of complaints, a Microsoft spokesperson provided a statement to CNBC. The company acknowledged that it was aware of the reports and was actively investigating the issues. The statement noted that the primary problems were centered on Exchange Online, a core component of the Microsoft 365 suite. The spokesperson thanked customers for their patience while the technical team worked to restore full service capabilities.
Microsoft utilized its official Microsoft 365 Status account on the social media platform X to share real-time updates with affected users. These communications aimed to keep the public informed about the progress of the investigation and the steps being taken to resolve the connectivity issues. The company emphasized its commitment to restoring services as quickly as possible to minimize disruption for its customer base.
Amazon, which also saw reports of downtime, addressed the situation on X. The company stated that its services were operating normally and suggested that an unrelated disruption elsewhere on the internet was causing some inaccurate news reports. Amazon directed users to its health dashboard for the most accurate and up-to-date data regarding its infrastructure status.
By 4 p.m., Microsoft announced a significant development in its troubleshooting efforts. The company reported that it had validated an alternative service health check method. This new approach allowed some of the affected servers to come back online. Microsoft stated that it was now applying this change more broadly across its infrastructure to accelerate the recovery process.
To ensure long-term stability, Microsoft also mentioned that it was preparing automated recovery systems. These systems are designed to continually detect and restart unresponsive servers. The goal is to maintain service stability while the broader changes are implemented and to prevent similar issues from occurring in the future.
Initially, Microsoft attributed the connectivity problems to elevated load across multiple regions of its infrastructure. However, further investigation revealed the specific cause. The company determined that a number of servers had become unexpectedly unavailable. This loss of capacity placed a significant strain on the remaining infrastructure, leading to the widespread outages observed by users.
A key factor in the prolonged downtime was that some of the unavailable servers were failing automated health checks. This meant that the system did not automatically recognize the issues or recover them as intended. Microsoft noted that it had taken steps to prevent additional servers from being impacted by the same failure mode.
As the company continued to work on returning the affected servers to service, it maintained a focus on preventing further degradation. By isolating the problem and implementing the new health check methods, Microsoft aimed to fully resolve the incident and restore normal operations for all Microsoft 365 services.
