The disruption began on Thursday, 12 November, when users reported difficulties accessing Outlook email services. The problems subsequently affected other Microsoft 365 applications, including Teams and Copilot, while some third-party services relying on Microsoft's infrastructure also experienced operational difficulties.
Downdetector recorded reports from 74 countries and territories within approximately one hour of the disruption. In the United States, nearly 130,000 reports of Outlook problems were recorded shortly after 1 p.m. Eastern Time.
Microsoft acknowledged the incident and said affected infrastructure was experiencing elevated server loads that were contributing to connectivity errors. The company initially concentrated its response on Exchange Online mailbox access before confirming that users in other regions could also be affected.
The recovery process proved more complicated than expected. Microsoft reported that some servers stopped responding after being restarted and that earlier technical changes had not restored services as anticipated. In its Friday updates, the company said it was continuing to investigate server performance and alternative recovery measures.
The outage also affected services operated by other technology companies. OpenAI reported problems involving Microsoft connectors, while Anthropic identified an issue with an upstream provider affecting its Microsoft 365 connector.
The incident illustrates the extent to which organisations depend on a relatively small number of cloud infrastructure providers for communications, collaboration and access to digital tools. When a major provider experiences an interruption, the consequences can extend beyond its own applications to businesses and services connected through its infrastructure.
For companies, the disruption could delay correspondence, interrupt internal coordination and affect customer-facing operations. Organisations that rely heavily on cloud-hosted productivity platforms may face operational difficulties when alternative communication and recovery arrangements are limited.
Microsoft has not published a definitive root cause. However, company representatives said there was no indication that the incident resulted from malicious or cyber activity.
The outage raises questions about infrastructure resilience, server redundancy and disaster-recovery planning across the technology sector. Businesses will be watching for Microsoft's full recovery, a detailed explanation of the incident and measures to reduce the risk of similar disruptions.
For enterprise customers, maintaining alternative communication channels and tested business-continuity procedures remains an important safeguard against dependence on any single technology provider.
Republished from the existing Aldrenor collection. Aldrenor editorial archive.
