On Thursday, November 12, Microsoft announced that its services, including Outlook, Teams, Office 365, and several cloud services, experienced significant outages affecting users across North and South America.
The initial announcement came around 12:45 PM via the social media platform X, where Microsoft stated that users were encountering issues accessing their Exchange Online mailboxes. The company’s message indicated that they were investigating reports from American users who were having difficulty connecting through various methods to their Exchange Online accounts. For more detailed information regarding this issue, users were directed to check the Microsoft 365 admin center under the reference EX1550543.
As the situation unfolded, Microsoft acknowledged that the outage was not limited to the Americas and could potentially impact Outlook, Teams, Office 365, and cloud services users globally.
By 1:07 PM, Microsoft provided an update stating that efforts were being made to mitigate the impact of the outage. The company confirmed that the connection issues were affecting Microsoft 365 services for users in any region, not just in the Americas.
According to data from outage monitoring site Downdetector, reports of issues with the email client Microsoft Outlook peaked at approximately 129,000 around 1:09 PM EST. Many users found themselves unable to send or receive emails, leading to significant disruptions during the workday.
As the afternoon progressed, the number of outage reports began to decline, falling to about 93,000 by 1:50 PM. However, by 3:20 PM, approximately 69,000 users were still reporting problems with Outlook, and another 31,000 users stated they were unable to use Microsoft 365 effectively.
Other Microsoft products were similarly affected. Reports regarding Teams reached a peak of around 4,600 at 1:58 PM, while outages for Microsoft’s AI assistant, Copilot, saw reports near 6,000 at its highest point.
Initially, Microsoft suggested that the issues might stem from increased load on infrastructure across multiple regions. However, they later clarified that the heightened load was not due to an increase in user traffic, but rather because some servers had unexpectedly become unresponsive, placing additional stress on other devices.
The company maintained that there had not been any recent changes associated with the time the outage began concerning system, software, or server infrastructure.
Further investigation indicated that the failures in server status checks could be attributed to problems within a component responsible for monitoring server status.
In response to the incident, Microsoft quickly took to social media to communicate that they were working diligently to alleviate the outage’s impact and prevent further servers from being affected. They also aimed to restore the affected servers swiftly.
Microsoft disclosed that actions taken included pausing all deployment operations, rerouting traffic away from impacted infrastructure, and restarting relevant servers.
By 1:48 PM, Microsoft reported that they had begun to distribute connection traffic across other global infrastructure to balance the load.
As of Thursday afternoon, some users had begun to regain access to their services, though full restoration of functionalities had not yet been achieved.
Later, Microsoft indicated that their mitigation efforts had successfully restored normal operation for Teams. They acknowledged that they were continuing to address other ongoing issues and would provide updates as they made progress.
In the wake of the widespread outage news, social media users expressed their thoughts and created humorous memes regarding the situation.
One user shared a lighthearted image of office workers joyfully packing their bags and heading home, while another commented, “Please keep my boss’s email disconnected, so he can’t send me…” This illustrates the mix of frustration and humor that often accompanies service interruptions in the corporate world.