When Microsoft's email service began malfunctioning on Thursday, November 12, the outage quickly spread beyond just missed messages, affecting calendars, productivity tools, and enterprises reliant on the company's cloud systems.
This large-scale disruption continued into Friday, November 13, demonstrating how a failure in one widely used service can trigger a chain reaction across the entire work ecosystem.
According to Microsoft incident logs, the Exchange Online incident with code EX1550543 began at 16:17 UTC on Thursday, corresponding to 21:47 in India. Users faced an inability to connect to their Exchange Online mailboxes through various connection methods.
Microsoft Exchange Online functions as a server system that stores and manages user data, while Microsoft Outlook is a client application used to view and interact with this data.
A broader Microsoft 365 incident, designated with code MO1550821, disrupted numerous corporate and consumer Microsoft 365 services globally. It started at 18:26 UTC, or 23:56 IST.
The first reports of issues came from America, but Microsoft later warned that users in any region could be affected.
The Downdetector platform, which tracks online service outages in real time, recorded over 130,000 reports of Outlook problems in the United States at its peak on Thursday afternoon. In India, complaints began shortly before midnight and reached 2,157 by 23:42. The number of reports rose again to 1,960 by 8:42 AM on Friday as people started working.
In its latest post on X, Microsoft announced that traffic optimization measures were yielding positive results for service stability and throughput. These measures are being applied more broadly in affected regions as part of ongoing recovery efforts. While this indicated progress, the company did not announce a final resolution.
Microsoft directed users to incident MO1550821 in the Microsoft 365 admin center or to its public status page. MO1550821 is one of the official incident tracking identifiers assigned by Microsoft for the current service degradation and outage.
Microsoft's explanation emerged in stages. Initially, it was stated that a number of servers unexpectedly became unavailable, placing additional load on the remaining infrastructure. The company emphasized that this increased load was not caused by a sudden surge in customer traffic.
Later, Microsoft reported that a process on the affected servers responsible for establishing secure connections overloaded, causing the servers to stop processing requests. Furthermore, the company began rolling back a recent network configuration change, which it stated correlated with the start of the incident. Earlier updates claimed that no recent change was related to the problem.
Recovery was complicated by the fact that the servers became unresponsive again when traffic returned to them. Microsoft attempted restarts and recoveries of the affected servers, limited certain types of traffic, rerouted connections via alternative paths, and improved throughput. The difficulty lay not only in bringing the servers back online but also in maintaining their stability as traffic returned.
Microsoft stated that it had no indication that malicious activity was the cause of the outage. The exact root cause remains unconfirmed, and the company promised to publish a report after the incident.
Exchange Online is Microsoft's cloud email and calendar service. Other Microsoft 365 features use it for mail, contacts, calendar entries, and meeting information. When Exchange Online became unreliable, dependent functions were disrupted, even where the main application was still working.
Users experienced difficulties accessing mailboxes via Outlook on the web, desktop, and other connection methods, and email delivery slowed down. Copilot for Microsoft 365 failed to load or respond, or struggled to retrieve working data. Calendars and meeting scheduling in Teams were affected, but core calls, meetings, group chats, and channel messages remained accessible. SharePoint files stored directly in the service remained available, although some related functions were impacted.
Microsoft also listed issues with specific features in Planner, To Do, Defender, Purview, Power BI, Intune, and Microsoft Graph—a set of APIs that allows software to exchange data with Microsoft services.
Reuters reported that OpenAI and Anthropic encountered issues in their Microsoft 365 connectors, which link AI services to users' work information.
In India, airlines IndiGo and Akasa Air reported disruptions in their email support services. However, there was no indication that flights were affected.
The consequences also reached government institutions. Reuters reported that Australian government bodies, including the Australian Security Intelligence Organisation and the Australian Federal Police, as well as Japan's government IT infrastructure and users in the US House of Representatives were affected. Taiwanese financial firms also reported disruptions in fund management operations.
On social media, users expressed a mix of frustration and humor, joking about closing laptops, missing meetings, and taking Friday off. Others linked the latest Microsoft outage to the long wait for Grand Theft Auto VI. Social media became an arena for memes.
This is not the first major Microsoft 365 outage this year. Another outage began on August 31 and was resolved on September 3. Microsoft attributed it to an issue with the core authentication configuration used by several services, affecting Exchange Online, parts of Copilot, OneDrive, and SharePoint. However, it was a different, identified issue.
A similar cloud outage occurred in October with Google, when a power failure at a data center disrupted services in the europe-west2 Google Cloud region—the cloud computing center in London. According to Google's incident report, the main effect lasted about six hours and eight minutes. The cause was different, but the incident showed how a local infrastructure failure can impact customers across an entire cloud region.
The CrowdStrike incident in July 2024 was different. A faulty software update from the cybersecurity firm led to a global outage of Windows computers. Microsoft estimated that 8.5 million devices were affected. The mechanism was different, but the outage highlighted the risks when a small number of vendors underpin critical systems.
The current test is whether the traffic optimization changes can maintain server stability as Microsoft increases traffic and capacity in different regions. The company promised to provide a post-incident report covering the root cause and preventative measures.
Customers need to know not only what broke but also why the safeguards failed to prevent the outage sooner.
The ongoing incident demonstrates how heavily workplaces have become dependent on overall cloud infrastructure. The lesson for organizations is the necessity of planning for key vendor failure. They must maintain emergency communication channels outside the primary email system, make critical information available through other means, and preserve alternative ways to contact employees and clients. Cloud services allow applications to work together, but these connections can also create single points of failure. Products may appear separate, but they rely on the same underlying systems.
