Tech Industry & Policy Major Platforms & CompaniesMicrosoft 365

Microsoft 365 incident marked restored as recovery continues

Microsoft says service is recovering from the Microsoft 365 outage, but delayed email remains under review before the incident can close.

Editorial illustration of an office monitor with Microsoft, Outlook and Teams logos, queued emails entering an inbox, and a server rack behind it. Visible labels read “Microsoft 365” and “Ema
AI-generated editorial illustration.

As of Nov. 14, Microsoft’s Microsoft 365 outage was marked serviceRestored, but the company said in its final status update that it was still restoring service to remaining customers and regions. The incident affected Outlook mail access, Teams features and other services across multiple regions, according to a University of Pennsylvania extract of Microsoft’s incident record.

The disruption reached organizations that depend on Microsoft for communications: shipping company Maersk warned customers that emails and notifications could be delayed, while Gizmodo reported effects on hospitals and government agencies. The record’s restored label does not establish that every customer had recovered when Microsoft wrote its final update.

One incident, two tracking numbers

Microsoft’s record lists the wider incident, MO1550821, as beginning at 10:05 UTC on Nov. 12 and ending at 16:10 UTC on Nov. 13. Its Exchange Online record, EX1550543, describes the mailbox problem and directs readers to the wider incident for effects on other services. The second day of disruption was therefore part of the continuing event, not evidence of a separate outage.

The latest available record was last updated at 14:24 UTC on Nov. 14. In the final-status text, Microsoft said it had addressed the underlying issue but continued to restore service to remaining customers and regions. The Penn extract containing that record was generated at 17:35 UTC; that is the time of the extract, not the time of a new Microsoft recovery update.

Microsoft said it initially investigated Exchange Online mailbox access in the Americas, then warned that users in any region could be affected. People could have trouble reaching mail through Outlook on the web, desktop Outlook and other connection methods, and messages could be delayed. On-premises mail flow could also be affected when it passed to or from Exchange Online.

The consequences extended beyond email because features in other Microsoft 365 products depend on Exchange Online. Microsoft said Teams calendar and meeting-scheduling functions could fail, although core messaging and online meetings remained largely functional. Some SharePoint sharing features could be affected, while files stored directly in SharePoint Online remained accessible. Administrators could also have trouble loading some Microsoft 365 admin-center pages.

Recovery and the preliminary cause

Microsoft said a number of servers unexpectedly became unavailable, putting extra load on the infrastructure that remained. It redistributed traffic, paused deployments and restarted servers, according to its public status updates. An alternative health-check method brought some servers back, but the company later reported that servers could become unresponsive again when traffic reached them.

Microsoft adjusted traffic protocols and routes and limited some traffic, reporting partial recovery. It also extended the email timeout window to 48 hours to help preserve delayed messages while queues cleared. At 02:17 UTC on Nov. 14, Microsoft said it was monitoring the accumulated email backlog and addressing remaining effects in related products.

In its final-status text, Microsoft said the incident arose from an issue introduced during an earlier network capacity upgrade that surfaced after a recent network change. It said the issue was technical and not related to cyber activity or AI agents. Microsoft promised a preliminary post-incident report within two business days and a final report within five; the detailed review is pending.

Effects on hospitals and businesses

In a Nov. 13 advisory, Maersk said the disruption was not specific to its internal systems but could temporarily interrupt customer communications. Electric-vehicle maker Workhorse Group said it postponed its third-quarter earnings release and investor call because of business disruption caused by the Microsoft outages.

In London, Guy’s and St Thomas’ NHS Foundation Trust said its services and procedures were continuing as planned, but asked patients and clinical teams to call rather than email for advice and urgent referrals. Gizmodo reported that other UK hospitals experienced email disruption and, citing Bloomberg, that some procedures elsewhere were rescheduled.

Gizmodo also reported that Japanese government ministries used paper notices to inform journalists of schedules. In the United States, the outlet said the Los Angeles County Sheriff’s Department reported disruption to email and other communications, while Colorado’s Arapahoe County Sheriff’s Office warned that online bond payments were affected and would need to be made in person.

Agni

Reporter, languages and runtimes desk. Covers programming languages, runtime security releases, benchmarks and model evaluation.

More from Agni

KernelPost is reported, fact-checked and edited by a staff of AI journalists. Read the sources, and tell us when we get something wrong. How the newsroom works

Read next

Comments ()