Log entry Nº 658 · the stack watch
Bearing E 090° · November 13, 2026 · 4 min read
E 090°Watch log
Microsoft 365 outage passes 13 hours amid 130,000 Outlook reports
Microsoft 365 remained partly offline for more than 13 hours after a Nov. 12 Exchange failure, peaking at 130,000 Outlook reports and disrupting mail, Teams, Copilot and security.
By Amara Osei4 min read794 words
By Amara Osei
More than 13 hours after an Exchange Online failure disrupted Microsoft 365 on Nov. 12, the platform had not fully returned to service. Outlook email led the disruption, while the wider incident covered Teams, SharePoint Online, Copilot, Power BI and security products.
Downdetector logged more than 130,000 Outlook problem reports at the peak. Microsoft said its latest fixes were "not taking as expected" overnight, leaving the recovery incomplete.
How far did the outage spread?
Microsoft’s service-health dashboard placed the start at 16:17 UTC on Nov. 12 under incident MO1550821. Mailbox access could fail through Outlook on the web, desktop Outlook using MAPI, Exchange ActiveSync and REST-based connections, while email delivery could run late.
Users across the Americas first encountered failures through Outlook on the web, desktop Outlook, mobile clients and the REST API. Within two hours, Microsoft said any region could face the incident. It then opened a wider incident spanning Teams, SharePoint Online, Copilot, Defender XDR, Intune, Power BI and several Purview services.
Takeaway: One Exchange Online dependency turned a mail outage into a Microsoft 365 workflow event across regions.
What caused the service failures?
Microsoft initially investigated elevated infrastructure load and whether a recent change had contributed. It later determined that traffic volume had not risen overall. A large number of unexpectedly unavailable servers shifted demand onto the remaining infrastructure. The related Exchange Online update carried incident ID EX1550543.
In a subsequent update, Microsoft identified the failure mechanism: a process responsible for establishing secure connections became overwhelmed on affected servers. Once overwhelmed, those servers stopped processing requests, forcing Microsoft to restore both capacity and stable request handling.
During mitigation, Microsoft observed a surge in outbound calls from routing services to backend servers. It attributed the higher volume partly to traffic rebalancing, scaled virtual machines to add capacity and continued monitoring the resulting call volume.
Microsoft prepared a configuration change and tested it on a subset before wider deployment. It also reverted a recent network configuration change that correlated with the disruption’s start, restarted affected infrastructure and watched server stability. Restricted traffic and gradual connection returns supported the recovery work.
Some servers became unresponsive again after Microsoft restored traffic, forcing the company to resume analysis and mitigation. That sequence explains why fixes had not restored all Microsoft 365 functions more than 13 hours after the incident began.
Takeaway: Unexpected server losses, not higher overall demand, drove the outage, and traffic rebalancing complicated recovery.
Which workflows broke?
Microsoft said impact varied by service and feature, depending in part on Exchange Online. Outlook users could lose mailbox access across web, desktop, ActiveSync and REST routes, and email delivery could remain delayed.
Teams core messaging and online meetings remained largely functional. Calendar access and meeting scheduling could fail because those features depend on Exchange Online.
Direct access to files stored in SharePoint Online remained functional. Exchange-dependent SharePoint features could still fail. For Microsoft 365 Copilot, users might be unable to load Copilot Chat or receive responses; Copilot experiences could also lose access to work data in email, calendars and files.
Security functions suffered narrower, dependency-specific impairment. Defender for Office 365 Safe Links might fail to verify URLs clicked in Outlook and Teams, while some Defender XDR portal pages could fail. Selected Intune device-enrollment and compliance scenarios also faced disruption, along with Purview data-loss prevention, automatic labelling and communication-compliance functions.
Takeaway: Teams messaging largely survived, but email, scheduling, Copilot and security dependencies produced the practical damage.
What should enterprise teams prepare?
The incident has renewed scrutiny of the operational risks created when organisations consolidate email, collaboration and security functions in one cloud ecosystem. When mail, meetings and security tools such as Safe Links rely on the same service estate, one infrastructure disruption can hit several business functions at once.
Sanchit Vir Gogia, chief analyst at Greyhound Research, put the enterprise problem plainly: “Enterprises have priced Microsoft 365 as a licence and never as a single point of failure.”
He recommended a rehearsed fallback instead of a second suite: an out-of-band incident-command channel, mail continuity for business-critical roles and a written decision on whether each security control should fail open or fail closed.
For security teams, an unavailable service and an impaired dependent control require different operating assumptions. The Safe Links issue, for example, concerned URL verification rather than a complete loss of Defender for Office 365 capabilities.
Microsoft continued publishing service-status updates, but it has not released a final post-incident root-cause report. Gogia expects a detailed account showing when Microsoft identified each cause and how it validated its recovery measures.
Takeaway: Recovery remained incomplete because capacity and connection handling failed together, while enterprises need continuity playbooks.
Plot points
- The outage began at 16:17 UTC on Nov. 12 under incident MO1550821.
- Microsoft 365 remained partly offline for more than 13 hours.
- Downdetector recorded more than 130,000 Outlook problem reports at the peak.
- Within two hours, Microsoft expanded the incident beyond the Americas.
- Affected services included Teams, SharePoint Online, Copilot, Defender XDR, Intune, Power BI and Purview.
via cio.com (Source)
More from Amara Osei
Show full bio
Market editor covering technology and product news in marketing technology at Martech Beacon.
47 articles
Neighbouring fixes
- Microsoft 365 outage exposes security monitoring and recovery gaps
- Microsoft 365 services stabilize after global outage
- Microsoft 365 Outage Carries $16 Billion Productivity Estimate
- Microsoft 365 Outage Nov. 12-13 Exposed What CIOs Never Mapped
- iOS 27 Quietly Blocks LiveRamp, Permotive, Audigent Without Warning