Microsoft 365 outage ran over a day, and HR's tools went with it
The Nov. 12 Microsoft 365 outage lasted more than a day, hitting Exchange, Teams, SharePoint and Copilot. Firms fell back on phone calls as continuity gaps surfaced.

Olivia Hart
· 4 min read
The Microsoft 365 outage that began Nov. 12 lasted more than a day and cut off Exchange Online mailboxes worldwide, with knock-on failures in 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, and the company confirmed the incident was technical, not a cyberattack or the result of AI agents.
For employers, the lesson lands on people-process decisions: incident response, workforce communications and vendor-risk review. Because Microsoft's suite is so widespread, even organizations whose own systems kept running struggled to reach customers and partners who depended on Microsoft. Nora Jones, vice president of product development at PagerDuty and founder of Jeli, said the outage exposed dependencies that continuity plans routinely miss.
What actually broke?
Requests queued until affected servers exhausted processing capacity. Beyond email, some features in Teams, SharePoint Online, Copilot, Defender XDR, Intune, Microsoft Graph and Windows 365 were affected, though scope differed across products and not every service went fully dark.
Jones pointed to a compounding problem: many firms run their incident response on the very tools that failed. "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," she 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 noted.
What did companies do instead?
The most resilient fallback turned out to be the telephone. "Fortunately, we're not a Microsoft shop so we did not lose email nor group collaboration capability," said Brian Greenberg, CIO and CTO, senior partner and strategic adviser at Fortium Partners. "However, many clients and partners were affected." His team used phone calls to reconnect with affected contacts, alongside LinkedIn, text messages, Zoom or Slack.
"The interesting thing I noticed is the general reluctance to pick up the phone for many," Greenberg said. "I don't mean texting, which is also another method that works, I mean picking up the phone and calling and speaking with the person to discuss in real time, live, synchronously."
At DigiCert, Eric Porter, senior vice president of finance and IT, kept internal work moving on Slack. The harder problem was external partners on Microsoft 365. "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 off quiet Teams channels and shared calendars. "You can be fully up and still be stuck waiting on someone who's down," he said.
How should leaders redraw continuity plans?
Full duplication is rarely the answer. "Duplicating Microsoft 365 wholesale would be enormously expensive, operationally complex, and probably counterproductive for most enterprises," said Dion Hinchcliffe, chief research officer at Frontier Research, who once priced a full backup for a financial services firm and called the result "ruinously expensive." His narrower goal: "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, that weighs the cost of losing each function and determines where redundancy pays off. Chasing sub-second recovery can be a poor investment when a brief outage does little harm — and, as he noted, when everyone is hit at once, there is greater understanding of the situation.
Practical steps from the incident:
- Review your own day. "People were wide awake and improvising, and what they improvised is the part worth studying," Jones said. "So review your own day, even though the outage was Microsoft's."
- Set up channels outside the platform. Microsoft's own business continuity guidance recommends establishing and testing alternative channels. Rimini Street CIO Joe Locandro pointed to paging tools that create text and email groups on personal phones, with escalation to a second-in-command if no one responds. "The key question is whether your backup options depend on the same services as your primary tools," Porter said.
- Check the identity layer. "When the identity layer has problems, it's not just email," Kumar said. "It's file access, single sign-on into other apps, and now AI assistants that sit on the same data." A backup channel signing in through the same identity provider "isn't really a backup. It's a second door into the same locked room."
- Keep files and contacts reachable. Some organizations continuously download email and files or copy them elsewhere, though Locandro cautioned such approaches are costly and hard to manage.
- Run the drill. Porter's test standard: lose the collaboration suite mid-decision and ask, "Can people reach one another, access the information they need, and communicate with customers?"
"The dependency most companies overlook is the vendor layer they don't control," Locandro said. With AI agents now layered on the same infrastructure, HR and IT leaders should expect the next outage to reach deeper into daily workflows than email alone.
Source: techtarget.com
More from Olivia Hart
Show full bio
Correspondent covering companies, deals and strategy in Recruiting and talent acquisition, learning and development at HR Briefing.
314 articles