Microsoft 365 Outage: Outlook and Teams Recover After 18-Hour Global Disruption

Microsoft spent Friday, November 13, 2026, bringing its services back online after a global outage that began the previous afternoon and knocked out Outlook, Teams and large parts of Microsoft 365 for roughly 18 hours. The disruption hit email, cloud files and documents for consumers and businesses, and rippled into emergency call handling, government offices, courts, schools and healthcare providers. Microsoft says it has found no evidence of malicious activity and has pledged to publish a root-cause report once mitigation is complete.

  • Scope of the failure: Outlook email, Teams meetings, Exchange Online, Copilot and Defender filtering were affected, and some administrators lost access to Intune management panels.
  • Duration: Network analyst Doug Madory of Kentik observed traffic returning after about 18 hours down, with recovery spreading from North America to Europe and Asia-Pacific.
  • Cause still unconfirmed: Microsoft described a large number of servers becoming unexpectedly unavailable and pointed to overwhelmed core processes, but has not published a definitive explanation.
  • Economic toll: One research center estimate put lost productivity at no less than US$7 billion.

How the outage unfolded

The trouble started around midday US Eastern time on Thursday, according to Microsoft’s own timeline, initially surfacing in Outlook mail and Teams meetings before spreading across the Microsoft 365 stack. Exchange Online, document sharing, corporate data services and email protection all showed degradation. Copilot, Microsoft’s AI assistant, was caught in the blast radius, and some users reportedly could not sign in to cloud-hosted Windows machines.

Downdetector recorded reports from 74 countries and territories within roughly an hour, and more than 140,000 users flagged problems on the monitoring platform. Early remediation attempts on Thursday night failed to take hold, and engineers spent Friday stabilizing systems region by region. Microsoft later reported encouraging progress in Europe, comparatively stable service in Japan and improving availability in North America, while warning that some users could still see intermittent access issues or delayed mail delivery.

The recovery was less a single fix than a traffic-management exercise. Microsoft isolated affected infrastructure, restarted components, rerouted network traffic and gradually returned servers to service. A 48-hour email timeout window stayed in place to protect messages queued during the blackout, and the company said pending mail queues had shrunk significantly toward normal levels.

Why email outages drag on

Email’s underlying architecture explains much of the duration. Unlike a modern web app that fails fast and locks users out, mail runs on a decentralized store-and-forward model built to never lose a message. While Microsoft’s servers were unresponsive, senders on Gmail, corporate systems and other platforms kept composing mail without seeing errors; their providers simply held messages in outbound queues and retried delivery. The result was a backlog that had to be drained carefully once service returned, a process that typically takes hours to days.

“We’re seeing encouraging recovery progress, with service availability and email delivery performance improving across a growing portion of affected infrastructure,” said Charles Lamanna, executive vice president of Copilot, Agents and Platform at Microsoft. “We know our customers rely on our services to get important work done every day, and regret the impact these outages had on those who depend on us.”

Microsoft’s public status feed described a core process on affected servers becoming overwhelmed, causing servers to stop responding and reducing capacity. The company has not confirmed a definitive root cause, and no executive fronted public briefings beyond official status updates.

Real-world fallout and a pattern of fragility

The human impact stretched well beyond inboxes. The Los Angeles County Sheriff’s Department reported disruptions to email and other communication platforms. In Colorado, the Arapahoe County Sheriff’s Office said online bond payments stalled because jail officials were not receiving the email notifications needed to process them, forcing in-person payments. The US Court of Appeals for the Tenth Circuit said its clerk’s office could not send or receive email for much of Thursday. In the UK, the National Pharmacy Association warned that mail problems could delay some prescriptions; in Japan, some businesses temporarily fell back on fax machines.

This is Microsoft’s second serious outage in two months. A September 2026 incident lasted days and was attributed to a central authentication configuration problem. The recurrence sharpens a structural concern: critical sectors have consolidated onto a handful of cloud providers with no true failover. When Outlook goes down, there is no second Outlook to switch to. Microsoft’s promise of a post-incident report with root cause and defense-in-depth actions will be the first real test of whether that fragility is being addressed or merely documented.

Sources & References