Log entry Nº 492 · the stack watch
Bearing S 180° · November 16, 2026 · 4 min read
S 180°Watch log
Microsoft 365 Outage Nov. 12-13 Exposed What CIOs Never Mapped
Microsoft's Nov. 12-13 outage hit Exchange Online and Outlook. Clients demanded full exit. Analyst David Linthicum says the real failure is enterprise dependency blindness, not Microsoft.
By James Calloway4 min read819 words

A latent defect in Microsoft's networking gateways, hit by increased load and reduced capacity, knocked out Exchange Online and Outlook for many Microsoft 365 customers on Nov. 12 and 13. Microsoft confirmed the cause in a preliminary post-incident report on Nov. 15. Automatic traffic redirection then spread the overload across servers rather than containing it — a textbook demonstration of blast radius.
Mailbox access and email delivery broke. Calendar invites failed to update. Some Exchange-dependent features in Teams, OneDrive, SharePoint and even Copilot faltered, though much of those services stayed up. Business processes that looked independent turned out to share Microsoft infrastructure.
Then came the reaction, and it was the unusual part. Analyst David Linthicum, formerly managing director and chief cloud strategy officer at Deloitte Consulting, said his phone rang with two kinds of calls: reporters wanting quotes, and clients asking how to remove Microsoft completely from their ecosystems. In 25 years of enterprise cloud work, he said, he had rarely seen that level of visceral anger.
His verdict on the exit talk is blunt. "That is not a strategy. It is a reflex." The same risks sit inside AWS, Google Cloud, Salesforce, ServiceNow and Oracle, he argues, because every provider has failure modes, every platform has dependencies and every architecture has a blast radius.
What actually failed?
Not just a service glitch. Microsoft's Nov. 15 report pinned the outage on a latent gateway defect that surfaced under load. The automation meant to help made it worse by redirecting traffic onto already-stressed servers. Nobody can reliably calculate the business cost — lost productivity, delayed decisions, stalled customer interactions, missed meetings. And nobody should expect compensation. As Linthicum puts it, Microsoft will not send "apology notes with bags of money." Most companies will absorb the loss.
The deeper failure, he argues, is visibility. Enterprises know the systems they buy directly. They rarely know the scaffolding underneath. A company can run Google for office automation while a critical SaaS platform quietly depends on Microsoft services — and discover that only when a workflow dies.
What should CIOs actually do?
Linthicum frames three lessons, and each carries a caveat.
Calculate real vendor risk. Every major system tied to a single cloud provider needs assessment for outages lasting 15 minutes, 1 hour, 8 hours or a full business day. Outlook, Exchange, Teams, Copilot, OneDrive, SharePoint and Azure belong on the map — but second- and third-order dependencies matter more. Which apps lean on Microsoft identity? Which vendors host on Azure? Which security tools, repositories and customer portals stop when Microsoft has a bad day? Most organizations find the blast radius larger than expected. Without that map, resilience planning is mostly guesswork.
He lists four questions CIOs should answer:
- Direct dependencies: which critical applications rely on the provider's infrastructure, identity, storage or APIs?
- Indirect dependencies: which vendors and connected services rely on that infrastructure?
- Business impact: what stops working after 15 minutes, one hour, eight hours or a full day?
- Accountability: who owns each affected process, its recovery plan and the decision to activate alternatives?
Build a plan to create the plan. That sounds bureaucratic. It isn't. Resilience planning needs people who understand applications, data, identity, integrations, networks, vendors, contracts and business priorities as a whole. Don't expect shortcuts here — Linthicum is explicit: "You are not going to AI your way through this one." AI can help with documentation and scenario planning. It cannot replace people who know how your systems actually work. The phases are discovery, then classification — some apps tolerate hours of downtime; others can't survive 10 minutes without financial or regulatory exposure — then targeted architecture. Not maximum redundancy everywhere. That becomes unaffordable and unmanageable.
Change operating practices. This is where organizations usually fail: meetings, a post-outage report, then drift back into old habits. Procurement should require disclosure of underlying cloud dependencies in every new SaaS purchase. Critical systems should not reach production without a resilience review. Communications planning needs an alternative outside the failed ecosystem — another platform, text trees, voice bridges, a separate status page — and it must be tested before the outage, not during. Identity planning needs break-glass access or secondary authentication paths, because centralized identity is a single point of enterprise failure. Backup planning needs realism: if your recovery plan and project files live in the same ecosystem that just went down, you don't have a recovery plan. In Linthicum's words, "You have a dependency problem wearing a recovery plan costume."
Will the lesson stick?
Probably not, if history holds. Unlike earlier technology shifts, cloud and AI can't run in silos, and unintended consequences travel across connected systems. Assume this outage repeats. Do the groundwork and install guardrails across all systems — or the next outage exposes the same blind spots. That's the warning. The industry's track record on post-incident discipline gives little reason for confidence.
Plot points
- A Microsoft 365 outage on Nov. 12-13 disrupted Exchange Online mailbox access and email delivery, with knock-on effects in Teams, OneDrive, SharePoint and Copilot.
- Microsoft's preliminary post-incident report, published Nov. 15, traced the failure to a latent defect in networking gateways under increased load and reduced capacity.
- Automatic traffic redirection spread the overload across servers instead of containing it.
- Analyst David Linthicum, formerly chief cloud strategy officer at Deloitte, reported clients calling to remove Microsoft entirely from their ecosystems — a first in his 25 years working with enterprise cloud.
- Linthicum recommends CIOs map direct and indirect dependencies and test impact at 15 minutes, 1 hour, 8 hours and a full business day.
via techtarget.com (Source)
More from James Calloway
Show full bio
Correspondent covering people, launches and day-to-day practice in marketing technology at Martech Beacon.
31 articles
Neighbouring fixes
- Microsoft 365 Outage Carries $16 Billion Productivity Estimate
- Microsoft 365 outage passes 13 hours amid 130,000 Outlook reports
- Microsoft 365 outage exposes security monitoring and recovery gaps
- Microsoft 365 services stabilize after global outage
- AI Assistants' Rogue Acts Are Chilling Consumer Adoption