Microsoft’s 365 business and enterprise services experienced a significant outage on Thursday, leaving many users unable to access their accounts. Starting around 10:40 AM ET, reports emerged about disruptions affecting functionality on Microsoft Teams, particularly in North America. By 1 PM ET, the company acknowledged that users were facing difficulties accessing Exchange Online mailboxes through various methods in the Americas.
As the situation unfolded, Microsoft reported elevated network loads across multiple regions, which contributed to connectivity issues. The company clarified that the problem stemmed from servers going offline rather than increased traffic. Approximately an hour later, efforts to redistribute connection traffic worldwide were announced to help mitigate the impact of the outage. Microsoft also indicated that it had temporarily paused all deployments, moved extra traffic off the affected infrastructure, and initiated a restart of the affected servers to restore service.
Official updates from Microsoft indicated that several key services were impacted, including Exchange Online, Microsoft Teams, SharePoint Online, Microsoft Copilot 365, and Microsoft Defender XDR. A spokesperson from the company confirmed awareness of the issues, particularly with Exchange Online, and expressed appreciation for customers’ patience during the restoration efforts.
User reports of the outage began to decrease around 1:15 PM ET on Downdetector, which tracks service uptime. This followed a notable spike in reports concerning Outlook and other Microsoft 365 applications reported around noon. As of the latest updates provided just before 3 PM ET, Microsoft was troubleshooting a system issue that caused servers to fail automated health checks, rendering them unavailable. The company was actively working to reboot its systems to restore normal operations.
Outages of this nature in cloud services are not uncommon, with various factors including configuration errors, DNS resolution troubles, and cyberattacks potentially at play. At present, there is no evidence suggesting that this particular incident was triggered by a malicious cyberattack. While major outages at Microsoft are relatively rare, they are not unprecedented. Noteworthy past incidents include a corrupted security update from CrowdStrike that caused widespread “blue screen of death” errors in July 2024 and an Azure service outage that resulted in significant disruptions for businesses reliant on those services.
In the wake of this outage, organizations should consider the possible implications for operational continuity and data protection strategies. Understanding the potential lifecycle of such incidents aligns with the MITRE ATT&CK framework, where tactics such as initial access and persistence may be relevant considerations in the broader context of cybersecurity. By focusing on preparedness and response planning, businesses can better navigate the complexities of contemporary cyber threats and service disruptions, ensuring they remain resilient in the face of future challenges.
This incident serves as a critical reminder of the importance of maintaining a robust incident response strategy and continuing vigilance against risks that could compromise service availability or data access.