Log entry Nº 458 · the stack watch

Bearing E 090° · November 18, 2026 · 4 min read

E 090°Watch log

Microsoft 365 outage: phones filled the gap, but CIOs see a dependency problem

The Nov. 12 Microsoft 365 outage grounded Exchange, Teams, SharePoint, Copilot and Defender XDR for over a day. Phones filled the gap. CIOs found the bigger lesson in unexamined vendor dependencies.

By Rebecca Stone4 min read761 words

When Microsoft went down, the phone picked up the slack
Fix Nº 458When Microsoft went down, the phone picked up the slack — Letiha / pixabay

The Microsoft 365 outage that began Nov. 12 lasted more than a day and knocked out Exchange Online, Teams, SharePoint Online, Copilot and Defender XDR for users worldwide. Microsoft's preliminary findings traced the failure to a latent networking-gateway defect exposed by traffic shifts and reduced capacity. Requests queued until affected servers ran out of processing capacity. Microsoft confirmed the incident was technical, not a cyberattack and not caused by AI agents.

For many practitioners, the immediate workaround was the oldest tool in the drawer: the telephone.

Who picked up the phone, and why

Brian Greenberg, CIO and CTO, senior partner and strategic adviser at Fortium Partners, said his organization avoided direct damage. "Fortunately, we're not a Microsoft shop so we did not lose email nor group collaboration capability," he said. "However, many clients and partners were affected."

His team called affected contacts and made other arrangements. Some turned to LinkedIn, text messages, Zoom or Slack. Greenberg noticed a pattern. "The interesting thing I noticed is the general reluctance to pick up the phone for many," he said.

At DigiCert, Slack kept internal operations running. Eric Porter, senior vice president of finance and IT, said the harder problem was external. "We shifted to phone calls and text messages to keep those conversations moving until service was restored," Porter said.

Sharad Kumar, CEO and co-founder of FluidCloud, moved time-sensitive work to phone channels after Teams channels and shared calendars went quiet. His takeaway: "You can be fully up and still be stuck waiting on someone who's down."

What does the outage change for continuity planning?

Dion Hinchcliffe, chief research officer at Frontier Research, said the surprise was not the outage itself. "It was how difficult recovery became as a shared infrastructure failure cascaded across services," he said. Beyond email, the affected list grew to include Intune, Microsoft Graph and Windows 365, with scope varying by product and feature.

Nora Jones, vice president of product development at PagerDuty and founder of Jeli, flagged a structural risk: many incident-response tools sit on the same failed platform. "If you coordinate a response in Teams, keep your runbooks in SharePoint and get your security alerts from Defender, all three were on Microsoft's affected list," Jones said. AI workflows took a hit too. "A lot of people were working with AI that day and lost it at the same moment they lost their email," she said.

Jones pushed back on the standard framing. "Every big outage gets called a wake-up call, and then everyone goes back to sleep, because the takeaway becomes review vendor risk, which you could write after any outage," she said. "Nobody was asleep at the wheel."

Where to draw the line on redundancy

Full duplication of Microsoft 365 is not a realistic answer. "Duplicating Microsoft 365 wholesale would be enormously expensive, operationally complex, and probably counterproductive for most enterprises," Hinchcliffe said. He once priced a full backup of essential systems for a financial services firm and called the result "ruinously expensive." The narrower target: "The goal isn't zero downtime. It's zero catastrophic downtime."

Greenberg recommended a business impact analysis, run with the rest of the leadership team, to weigh the cost of losing each function. Faster recovery costs more, and chasing minute-level redundancy can be a poor investment when a brief outage does little harm. He added one mitigating factor: when a major SaaS platform fails, everyone shares the pain. "We're all in the same boat, more-or-less," Greenberg said. "So there's greater understanding to the situation."

Joe Locandro, CIO at Rimini Street, named the blind spot directly: "The dependency most companies overlook is the vendor layer they don't control." Kumar noted many firms inventory their applications but never map what those applications depend on.

What can CIOs do now?

  • Review your own day. "People were wide awake and improvising, and what they improvised is the part worth studying," Jones said.
  • Set up independent channels. Microsoft's continuity guidance recommends alternative communications. Locandro suggested paging tools with acknowledgment requirements and escalation paths.
  • Watch the identity layer. A backup channel using the same identity provider "isn't really a backup," Kumar said. "It's a second door into the same locked room."
  • Keep files and contacts reachable. Offline copies and external contact lists carry the day when the platform does not.
  • Run the drill. Porter's test: lose the collaboration suite mid-decision and ask, "Can people reach one another, access the information they need, and communicate with customers?"

Plot points

  1. The Microsoft 365 outage began Nov. 12 and lasted more than a day
  2. Affected services included Exchange Online, Teams, SharePoint Online, Copilot and Defender XDR
  3. Microsoft attributed the failure to a latent networking-gateway defect, not a cyberattack
  4. PagerDuty's Nora Jones: incident-response tools on the affected list included Teams, SharePoint and Defender
  5. Full Microsoft 365 duplication was described as 'ruinously expensive' in one financial services pricing exercise

via techtarget.com (Source)

Filed under

  • microsoft-365
  • business-continuity
  • disaster-recovery
  • saas-resilience
  • vendor-dependency
Share this article:

More from Rebecca Stone

Rebecca Stone

Show full bio

Staff writer covering companies, deals and strategy in marketing technology at Martech Beacon.

41 articles

Neighbouring fixes

‹ Previous article