Log entry Nº 465 · the stack watch
Bearing NE 045° · November 14, 2026 · 3 min read
NE 045°Watch log
Microsoft 365 services stabilize after global outage
Microsoft blamed an earlier network capacity upgrade for a global Microsoft 365 outage lasting more than 24 hours, and gave no full-recovery ETA on Nov. 13.
By Tom Whitfield3 min read549 words

Microsoft 365 services showed broad recovery and stability by 6 p.m. UTC (1 p.m. ET) on Friday, Nov. 13, but Microsoft still reported degradation in services that interact with Exchange Online.
The cause: a network capacity upgrade
Microsoft ruled out both a cyberattack and AI as the cause of the global disruption, which lasted more than 24 hours and affected businesses worldwide. The company attributed the incident to a technical issue introduced by an earlier network capacity upgrade, which surfaced after a recent network change. It restored services gradually, validating stability at each stage. Microsoft said the slower process helped ensure a stable restoration.
What does this change for Microsoft 365 administrators?
In a service health dashboard update at 8 p.m. UTC (3 p.m. ET), Microsoft said: “As infrastructure stabilizes, we’re still draining queued messages and rebalancing traffic, so customers may see improved sign-in/access while delivery and processing continue to catch up. We do not have an ETA for full recovery yet. Service access can recover before mail flow fully normalizes.”
For practitioners, that gap between sign-in and mail flow sets the operating priority: treat improved access as partial recovery, keep delivery and processing under observation, and distinguish a working application from a completed message queue.
Where disruption persists
Email may still arrive late or remain inaccessible. Microsoft 365 components that do not rely on Exchange Online interactions continued to work, but the company listed a wide set of affected services across administration, endpoint management, collaboration and content.
- Some Microsoft 365 Admin Center pages may fail to load; Cloud Update, Cloud Policy and Inventory in Microsoft 365 Apps Admin Center are affected.
- Copilot 365 Chat may fail to load or return no response in either the web version or the app.
- Microsoft reported intermittent impact to Intune device enrollment, device check-in and device compliance policies.
- A wide range of functions in Microsoft Purview and Microsoft Teams remain impacted.
- Windows 365 customers who configure their tenant and Cloud PCs to use Microsoft Purview Customer Key for Windows 365 Cloud PCs may have users unable to connect.
- Microsoft 365 apps, including Word and Excel, may fail to display recently used files.
The affected-service list spans Cloud PCs, Intune enrollment, Purview functions and Office file access, so “email is back” is not a sufficient status test.
Why recovery creates security risk
Matt Hull, vice president of cyber intelligence and response at NCC Group, warned: “cyber criminals will be moving quickly to exploit the uncertainty, disruption and frustration that events like this create. Organizations should remind colleagues to be particularly vigilant, verify any unexpected contact through established channels before acting, and report anything suspicious without delay.”
Hull said attackers may impersonate Microsoft or internal IT teams to persuade employees to reset passwords, approve multi-factor authentication requests or grant remote access to their devices. His warning applies during recovery, when delayed email and failed access requests coincide with a period of uncertainty.
What comes next
Microsoft has promised a full post-incident report once its review is complete. The company said it was deeply sorry for the disruption and took its responsibility for customers’ trust seriously. Until the report arrives, administrators still face an open recovery window and a heightened social-engineering risk.
Plot points
- Microsoft reported broad recovery and stability at 6 p.m. UTC on Friday, Nov. 13, with Exchange Online-linked degradation continuing.
- The global outage lasted more than 24 hours and followed an earlier network capacity upgrade plus a recent network change.
- At 8 p.m. UTC on Nov. 13, Microsoft said it had no ETA for full recovery and that mail flow could lag behind service access.
- Microsoft ruled out both a cyberattack and AI as the cause.
- Affected products included Copilot 365 Chat, Intune, Purview, Teams, Windows 365 Cloud PCs, Word and Excel.
via cio.com (Source)
More from Tom Whitfield
Show full bio
News editor covering money, funding and market shifts around marketing technology at Martech Beacon.
34 articles
Neighbouring fixes
- Microsoft 365 outage passes 13 hours amid 130,000 Outlook reports
- Microsoft 365 outage exposes security monitoring and recovery gaps
- 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