INTELLIGENCEReference · public sources
← Incidents

Incident reportDisputed / suspected cyberattackReport version 1 · November 21, 2026

Microsoft 365 global outage

Suspected by some commentators to be part of a coordinated cyberattack during the mid-November outage wave; the organization gave a non-cyber cause. Stated cause: Microsoft's preliminary investigation points to a software defect. No source has reported evidence of a cyberattack.

DisputedAttribution: Not attributedReference data · public sources

01Executive assessment

  • DisputedStated cause: Microsoft's preliminary investigation points to a software defect. [1]
  • DisputedThe analysis found no evidence the outages were related. [1]

Implication: organizations in the affected sectors should confirm whether the access paths described in the sources apply to their own environment. A matching sector or technology is a reason to examine exposure, not evidence of compromise.

02What happened

Suspected by some commentators to be part of a coordinated cyberattack during the mid-November outage wave; the organization gave a non-cyber cause. Stated cause: Microsoft's preliminary investigation points to a software defect. No source has reported evidence of a cyberattack.

Incident type
Disputed / suspected cyberattack
Event period
November 12, 2026
Date precision
day
Evidence basis
Cyberattack suspected in public commentary; non-cyber cause stated by the organization
Sectors
Technology

As stated by the cited reporting. Current collection, November 2026.

03Evidence chronology

Publication dateDevelopmentTypeSource
November 18, 2026Analysis reviews the week's outages; only Optimizely confirmed as a cyberattack.Analysis[1]

Event dates, source publication dates and our observation time (November 21, 2026) are recorded separately. Observation time is when DarkFire first collected the record, not when the activity occurred.

04Targets and geography

TargetRoleLocationPrecision and basis
MicrosoftAffected organization (outage)Redmond, Washington, United Statescity · Organization headquarters, affected system location unspecified

Locations describe affected organizations or countries as stated by the sources. They never indicate where an attacker operates from.

05Attribution assessment

Attributed actor
Not attributed
Assessed by
No assessment
Confidence
unknown
Sources

DarkFire aggregates attribution published by the named assessing organization; it does not make its own attribution. Event evidence, actor attribution and location precision are separate judgments.

06Technical behavior

No incident-specific procedure evidence has been recorded yet.

Techniques listed here are the behaviors described for this incident, not the actor's full ATT&CK catalog.

EVIDENCEACTOR AND TECHNIQUESThe ConversationNovember 18, 2026Microsoft

07Software and indicators

No publicly shareable indicators are recorded for this incident.

08Business exposure and priorities

Organizations in technology should review whether they share the conditions described in the sources: the same technology, supplier relationships or access paths. Relevance is a reason to examine exposure, not a finding of compromise.

09Defensive actions

No actor-level defensive guidance is linked.

From the dossier. For each action, name a control owner, the supporting evidence and a completion criterion.

10Analytic gaps

  • Whether access persists at any affected organization is unknown unless newer evidence is published.

11Source notes and changes

  1. [1]Seven major tech incidents in a week: what's going onThe Conversation · published November 18, 2026 · collected November 21, 2026

Version 1, published November 21, 2026. No corrections recorded. Report an error to have it reviewed; corrections and retractions keep the previous version visible.