Incident sheet · /infrastructure
- System
- Infrastructure & Cloud
- Filed
- Read
- 4 min · 895 words
- Severity
- Routine
Microsoft 365 Outage Lasted Over a Day; Phones Carried the Load
The Nov. 12 Microsoft 365 outage ran over a day, hit Exchange Online, Teams, Copilot and Defender XDR, and pushed enterprises back to phones, texts and Slack.

Event log
- The Microsoft 365 outage began Nov. 12 and lasted more than a day.
- Exchange Online, Teams, SharePoint Online, Copilot, Defender XDR, Intune, Microsoft Graph and Windows 365 features were affected.
- Microsoft attributed the failure to a latent networking-gateway defect, not a cyberattack.
- CIOs at Fortium Partners, DigiCert and FluidCloud shifted to phone calls and texts during the outage.
The Microsoft 365 outage that began Nov. 12 ran more than a day and disrupted enterprises worldwide, forcing CIOs back to telephone calls, texts and rival platforms. Microsoft's service health updates reported users unable to connect to Exchange Online mailboxes, with related failures in features of Teams, SharePoint Online, Copilot and Defender XDR. 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 exhausted processing capacity. Microsoft stated the incident was a technical issue, not a cyberattack and not the work of AI agents.
What did organizations actually do?
The most common fallback was the telephone. Brian Greenberg, CIO and CTO, senior partner and strategic adviser at Fortium Partners, said his firm avoided direct damage but not indirect damage.
"Fortunately, we're not a Microsoft shop so we did not lose email nor group collaboration capability," Greenberg said. "However, many clients and partners were affected."
His organization reconnected with affected contacts by phone and made other arrangements. Some staff also used LinkedIn, text messages, Zoom or Slack. Greenberg noted a cultural obstacle: "The interesting thing I noticed is the general reluctance to pick up the phone for many."
At DigiCert, Eric Porter, senior vice president of finance and IT, said Slack kept internal communication running. "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 and other channels after Teams channels and shared calendars went quiet.
"You can be fully up and still be stuck waiting on someone who's down," Kumar said.
How far did the cascade reach?
The blast radius exceeded email. Beyond Exchange Online, some features in Teams, SharePoint Online, Copilot, Defender XDR, Intune, Microsoft Graph and Windows 365 were affected, though scope varied by product and feature.
Dion Hinchcliffe, chief research officer at Frontier Research, said the failure mode, not the outage, surprised observers.
"The surprise wasn't that Microsoft went down," Hinchcliffe said. "It was how difficult recovery became as a shared infrastructure failure cascaded across services."
Nora Jones, vice president of product development at PagerDuty and founder of Jeli, flagged a structural problem: the affected list included tools many organizations use to manage incidents. "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-dependent workflows added another failure point. Agents that triage tickets or draft replies through Microsoft 365 services stopped when the underlying systems failed. "A lot of people were working with AI that day and lost it at the same moment they lost their email," Jones said.
She rejected the standard framing of such incidents. "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," Jones said. "And nobody was asleep at the wheel."
Where should CIOs draw the line on downtime?
Full duplication of Microsoft 365 is not a practical 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 goal isn't zero downtime," Hinchcliffe said. "It's zero catastrophic downtime."
Greenberg recommended a business impact analysis weighing the risk and cost of losing each function, conducted with the rest of the leadership team. Faster recovery costs more, and chasing sub-second or minute-level redundancy is a poor investment when a brief outage does little business harm. He added that a simultaneous, widely shared outage meets greater tolerance: "We're all in the same boat, more-or-less."
Joe Locandro, CIO at Rimini Street, named the core gap: "The dependency most companies overlook is the vendor layer they don't control." Kumar said many companies hold an application inventory but lack a map of what those applications depend on.
What can CIOs do now?
- Review your own day. Jones said teams should study what staff improvised during the outage: "People were wide awake and improvising, and what they improvised is the part worth studying."
- Set up channels outside the platform. Microsoft's continuity guidance recommends testing alternative channels. Locandro said paging tools can create text and email groups requiring acknowledgment on personal phones, with escalation to a second-in-command. Porter cautioned: "The key question is whether your backup options depend on the same services as your primary tools."
- Check identity dependencies. Kumar said identity failures cut off file access, single sign-on and AI assistants, so a backup channel using the same identity provider "isn't really a backup. It's a second door into the same locked room."
- Keep files and contacts reachable. Locandro noted some organizations download email and files for offline access, though such approaches are costly. Porter said essential contacts must be accessible off-platform.
- Run the drill. Porter said a realistic test removes the collaboration suite mid-decision: "Can people reach one another, access the information they need, and communicate with customers?"
The outage was not the first to disrupt enterprise IT. It will not be the last.
via techtarget.com (Source)
More from Rebecca Stone
Show full bio
Senior reporter covering money, funding and market shifts around enterprise information technology and the leaders who run at CIO Monitor.
199 articles
The newsroom digest
One email a day with the stories that matter. No noise.
Cross-references
- Microsoft Outage Puts the Economics of Prevention to the Test
- Microsoft 365 outage passes five hours after first fix fails
- Microsoft 365 limps back: Exchange Online still degraded after 24-hour outage
- Microsoft 365 Outage Exceeds 12 Hours as Recovery Fails
- Microsoft 365 outage hits Outlook, Teams and Copilot worldwide