On the 1st of March, a widespread outage from Microsoft left tens of thousands of users stranded without access to vital services like Outlook, Teams, and Office 365 for more than three hours. The cause of this major disruption was not fully explained by Microsoft, but they attributed it to a “problematic code change.”
According to data from Downdetector, the issues began around 3:30 p.m. ET, with a staggering number of complaints flooding in for Outlook, Office 365, and Teams. The majority of reports came from major U.S. cities such as New York, Chicago, and Los Angeles, with users worldwide also experiencing disruptions.
As users grappled with the sudden loss of access to these essential services, many took to social media to express their frustration and concerns, with some initially fearing a potential cyberattack on Microsoft’s systems.
Microsoft officially acknowledged the issue in an update at 4:34 p.m. ET through its Microsoft 365 Status account, stating that they were investigating the situation where users might be unable to access Outlook features and services. However, the impact extended beyond just Outlook, affecting other Office 365 apps like Word, Excel, Teams, and Exchange.
Despite the company’s efforts to rectify the situation, users continued to face challenges even after services started recovering. Microsoft later identified a possible cause around 5:00 p.m. ET and eventually resolved the issue by rolling back the faulty code by 7:02 p.m. ET. They advised users to check MO1020913 in the admin center for further details on the resolution process.
Even after the services were restored, Microsoft’s service status page still displayed ongoing issues with Outlook, indicating that they were actively working on resolving the remaining disruptions. This persistent problem triggered user frustration and raised concerns for businesses relying on these services for their daily operations.
As the outage persisted, Adam Pilton, a Senior Cybersecurity Consultant at CyberSmart, highlighted the widespread impact of the outage on businesses globally. He emphasized the frustration faced by users unable to work effectively due to the lack of access to emails and important documentation. Pilton pointed out the critical need for businesses to have contingency plans in place to mitigate the risks associated with relying on third-party software services like Microsoft.
While the exact cause of the outage remained unclear, Pilton suggested that it may have been triggered by a recent code change implemented by Microsoft to a segment of their infrastructure. He underlined the significance of businesses being prepared for such contingencies to ensure the continuity of operations and revenue generation.
Despite not being a cybersecurity incident, the Microsoft outage served as a stark reminder of the vulnerabilities businesses face when heavily dependent on third-party software providers. This incident highlighted the need for robust contingency plans and preparedness to navigate disruptions caused by unforeseen circumstances in the digital landscape.