A cyberattack disrupts cloud services in a control room, while a government security office stands in the background.
The firing of the US National Cyber Director, a post that coordinates federal cybersecurity policy, landed in the middle of a run of outages that included a major Microsoft 365 failure. The wording matters here. The White House confirmed that Sean Cairncross is leaving. The reporting also says he was fired, and it does not tie that firing to the outages.

A cyberattack disrupts cloud services in a control room, while a government security office stands in the background. What was confirmed on November 19​

A White House official told CBS News that Cairncross will leave, and multiple sources told CBS he was fired. The CBS account says White House chief of staff Stephen Miller had long wanted him out and doubted his expertise. Those claims come from anonymous sources, not from a public White House explanation.

Reuters separately quoted a person close to the White House who said Cairncross was "fired." That source said Trump fully supported the move. Reuters called it the administration's first major personnel move since the outages.

Some early coverage called it a resignation. The better-supported description is that the White House confirmed his departure while sources describe a dismissal.

The successor is Kirsten Davies, the Pentagon's chief information officer. Reuters' source said she would take the role temporarily. A permanent director would need Senate confirmation, and Reuters notes the Senate turns Democratic-controlled in January. CBS makes the same point: any nominee has only a narrow window.

Cairncross called the job "the honor of a lifetime." He had held it since August 2025.

Why the post matters to IT and security teams​

CBS describes the National Cyber Director as a Senate-confirmed adviser to the president. The role coordinates cyber strategy across the federal government and was created in 2021. Cairncross's office oversaw the administration's seven-page cyber strategy, released in March. According to CBS, it promised to confront adversaries, harden critical infrastructure, keep a US edge in AI and modernize federal systems.

None of the reporting says how the leadership change will affect that strategy. A temporary head and a closing Senate window make the near-term direction unclear. Treat that as an inference, not a reported finding.

The outages: close together, not shown to be connected​

The disruptions ran from roughly November 12 to 17. They covered Microsoft 365, a nationwide FAA ground stop on November 13, and problems at JPMorgan Chase, United, Apple services and the NSA's internal network. Primetimer's account of the Chase, United, Apple and NSA details is not independently confirmed in the reporting reviewed here.

Officials have pushed back on the idea of a single cause:

  • Homeland Security Secretary Markwayne Mullin told lawmakers that investigators had "seen nothing that would indicate that they are related."
  • Mullin said he was "98% confident" the outages were not malicious foreign activity.
  • Reuters reports that the top US intelligence official described separate service outages tied to maintenance and technical changes, not a coordinated or state-sponsored attack.
  • Reuters also reports that cybersecurity experts attribute the wave to companies rushing to patch newly discovered vulnerabilities, a task AI tools are making easier to expose. That is expert opinion, not a confirmed cause for any specific outage.

"No evidence of a coordinated attack" is not the same as "every incident is proven benign." The reporting supports the first statement only.

What Microsoft says happened​

Microsoft 365 is the part of this story with the most detail. Several Microsoft 365 services came to a standstill on Thursday, November 12. Exchange Online and Outlook were the primary services affected, and disruptions extended to Teams, Microsoft 365 Copilot, SharePoint Online, Intune and Defender for Office 365, among others.

Charles Lamanna, Microsoft's EVP for Copilot, Agents, and Platform, attributed the incident to three main factors affecting the networking systems Microsoft 365 relies on. His abridged root cause, posted on X on November 16, runs as follows:

  • The first factor was a latent defect from an update that began rolling out in July. It made servers unresponsive under certain load conditions.
  • The defect came from a fix prepared specifically for Microsoft 365 networking gateway servers. Lamanna said neither the defect nor the fix applies to broader Windows deployments. That is relevant for Windows administrators worried about their own estates.
  • Roughly fifteen hours before the outage, Teams failed over from the alternative gateway to the primary gateway that also supports Exchange Online.
  • IT Pro reports that around 14% of gateway server capacity was out of service because of an unrelated issue from the previous day. Taken together, Lamanna said, the load and reduced capacity triggered the July bug.
  • Systems redirected users to working servers, but the extra traffic triggered the same defect there, producing a cascade of failures.
  • "At its lowest, more than 80% of servers were unresponsive," Lamanna wrote.
  • Because the defect dated from months earlier, Microsoft's normal rollback, flighting and feature flags could not quickly revert it. After engineers confirmed the cause, they built an update that returned the code path to a previously known good state.

IT Pro reports that customers were still waiting on a full post-mortem. Lamanna pointed customers to the Microsoft 365 Admin Center for the detailed root cause. Admins should treat the X post as an abridged, preliminary account.

Primetimer's shorthand of "a software bug and network capacity overload" is directionally right. It leaves out the failover, the unrelated capacity loss and the failed rollback path, and those details are the ones that matter for resilience planning.

Microsoft's apology​

IT Pro reports that Satya Nadella opened Microsoft Ignite on November 17 with an apology. He called digital infrastructure the "dial tone for the world" and acknowledged that Microsoft has work to do on resilience. IT Pro also notes this was the second major Microsoft 365 incident in about three months, after one on August 31.

Practical takeaways for admins​

This is general industry guidance, not something stated in the sources:

  1. Check the Microsoft 365 Admin Center service health history. Microsoft says the full root-cause detail sits there.
  2. Review your business-continuity plan for mail and collaboration. Lamanna's account says Teams chats and meetings largely kept working because they could fail over. Exchange Online could not.
  3. Don't assume Windows endpoints were affected. Microsoft says the defect is specific to the Microsoft 365 gateway servers.
  4. Be wary of "coordinated attack" claims. Axios reported that suspected bots accounted for roughly 30% of posts promoting outage conspiracy theories, per PeakMetrics. That is a finding about online discussion, not about who or what caused the outages.

Bottom line​

The firing and the outages are close in time, but no reporting establishes that one caused the other. For Microsoft-centric IT teams, the more useful story is the Microsoft 365 failure: a months-old latent defect, a failover that shifted load, and lost capacity combined to produce an outage with a slow recovery. The leadership vacuum at the federal cyber office will matter mainly through who is nominated and confirmed before the Senate changes hands.

 

References

  1. Trump’s National Cyber Director Sean Cairncross steps down amid major tech outages across the US - primetimer.com primetimer.com 2026-11-20T02:21:00+00:00
  2. White House national cyber director leaving his post - CBS News cbsnews.com
  3. Months-Old Bug Triggered Microsoft 365 Outage tech.yahoo.com