Microsoft Outlook and Microsoft 365 Outage Lasts Nearly Two Days

Microsoft's Outlook and Microsoft 365 services suffered an outage lasting almost two days that affected millions of users worldwide. On Friday, 13 November 2026, The Verge reported that service was gradually recovering, with some users regaining email access but facing possible mail delivery delays.

In a status update timed at 7 a.m. ET on Friday, Microsoft reported encouraging recovery progress in Europe, with improving service availability and email delivery performance. Japan remained comparatively more stable, and North America was also improving. Some users could still experience intermittent issues in all regions.

The disruption reached beyond mail. It affected Outlook and Microsoft 365 features that depend on Exchange Online, Microsoft's cloud mail platform, including SharePoint Online, Teams, and Copilot AI, the company's AI assistant layer. Microsoft's public status portal lists service degradation affecting both Microsoft 365 Business or Enterprise and Microsoft consumer products, and states that users may be unable to connect to multiple Microsoft 365 services.

Microsoft also used that public page for service health information. According to the portal, the company posted updates there because Microsoft 365 administrators may be unable to access the admin center. That console is where IT staff normally run tenant-level diagnostics, so during an incident the public page becomes the main place to check whether the fault lies on Microsoft's side.

Recovery work is focused on the message pipeline. Microsoft said reducing email queues and backlogs remained a priority. An extended 48-hour email timeout window remained in place to protect delayed messages, meaning messages held in queue are retained rather than failed outright. At the time of reporting, Microsoft had not given an estimated time for full restoration of Outlook and Microsoft 365 service.

On the cause, Microsoft said it had found no evidence connecting the outage to malicious activity. It will share a full root-cause report and remediation actions after the issues are fully mitigated. Until then, the technical details remain with Microsoft.

In my view, the most useful lens here is dependency depth. Exchange Online sits underneath a set of collaboration and AI features, so a fault in mail propagates to every workload that reads or writes through it. Administrators whose tenants span Outlook, Teams, SharePoint, and Copilot should expect the impact to look like that, and should not assume a degradation confined to mail.

The broader context is the trade-off between queue retention and delivery certainty. A 48-hour hold protects messages from being bounced or lost during backlog drain, but senders and recipients may see delays that look like silent failure. For organizations with time-sensitive mail, such as legal notices, payment confirmations, or incident communications, the practical question is whether an out-of-band channel is ready for the window when queued messages are still in transit.

The outage also points to a design principle beyond this incident. Microsoft used a public status page as its fallback when the admin center was impaired, which keeps the status channel separate from the management plane. The root-cause report Microsoft has promised should show how the failure crossed those boundaries, and it will let engineers judge whether the mitigations address the actual fault or only its symptoms.