Microsoft confirmed on Saturday that Outlook, Teams, Copilot and other Microsoft 365 services had returned to normal operation following a widespread disruption that began on Nov. 12 and lasted more than a full day. The company’s status page listed products as operating normally, and the backlog of delayed email had been processed.

The outage interrupted access to mailboxes, delayed email delivery and affected calendar features tied to email systems. Core Teams chats and online meetings largely continued to function for many users, though related scheduling and invitation tools experienced problems. SharePoint and certain administrative functions also saw interruptions in some regions.

Scope and Timeline of the Disruption

Problems first appeared around midday Eastern Time on Nov. 12, initially centered on Exchange Online. Within about an hour, user reports of disruption had reached 74 countries and territories. Both commercial and consumer versions of Microsoft 365 were affected. The company later stated that the incident had impacted customers across North America, Europe, Asia-Pacific and other regions.

Microsoft 365 serves more than 450 million paid commercial subscribers. While the exact number of accounts affected in this event was not disclosed, the disruption interrupted daily work for businesses, trading desks, government offices and other organizations that rely on the platform for communication and collaboration.

Recovery proceeded gradually. By Nov. 13, engineers reported improving stability and declining email queues in multiple regions. On Nov. 14, Microsoft announced that remaining affected customers and regions had been restored and that accumulated email had finished processing.

Technical Cause Identified

Microsoft attributed the outage to a technical problem that originated during an earlier network capacity upgrade. A subsequent network configuration change caused the underlying issue to surface. The company stated that the incident was unrelated to any cyberattack or to artificial intelligence systems.

Engineers worked to restore capacity, recover affected servers and return services to stable levels in stages to avoid further instability under high demand. Microsoft apologized for the disruption and said it would publish a full post-incident review once its internal examination is complete. No release date for that report has been given.

Operational Effects and Ongoing Monitoring

During the outage, users reported difficulty reaching inboxes, missing meeting invitations and unresponsive web interfaces for some tools. Organizations depending on email for internal processes and official communications faced temporary workarounds. Trading firms and public-sector offices in multiple countries experienced interruptions.

As of the latest updates, Microsoft’s status page showed all products operating normally. The company indicated it would continue monitoring systems for an extended period given the scale of the event and would track any remaining email backlog to confirm full delivery. Most related product issues, including those affecting Copilot, Teams calendars and SharePoint sharing, were described as addressed.

The incident remains under formal review pending the post-incident report. Microsoft has not issued a verified count of impacted accounts and has not detailed every technical component involved beyond the network capacity and configuration sequence already disclosed.