Microsoft Threat Actor Naming
Doc updateThe Emerald Sleet entry now links to a Microsoft Security blog, and the Storm-1516 entry was removed from the table.
Daily Defender NewsThe period's strongest addition is documentation for the SyntheticMediaDetectionEvents advanced-hunting table, covering Microsoft Teams synthetic-media detections and investigation fields. Endpoint's AI Agent Runtime Protection guidance is more operationally specific: it separates agent-native and network inspection, defines support-matrix requirements, and maps both settings to 0 (Disabled), 1 (Block), and 2 (Audit). Identity migration wording also removes a domain-controller-only limitation statement, while threat-actor naming entries were revised.
The new Defender XDR advanced-hunting table covers Microsoft Teams synthetic-media detection events and exposes severity, confidence, maliciousness, source, user, and detection-provider details. Results require Defender for Office 365 and an approved detection engine.
The configuration guidance states that both settings use 0 for Disabled, 1 for Block, and 2 for Audit.
The demonstration guide now uses a support matrix covering inspection methods, agent modes, and minimum versions. It distinguishes agent-native inspection (AiAgentProtection) from network inspection (AiAgentNetworkInspection), removes Beta Channel update-configuration steps, and adds known-issues guidance.
The table adds or revises aliases, affiliations, origins, and references, including new associations for Citrine Sleet, Midnight Blizzard, and Storm-2603; an entry for Storm-2195; and updated classifications for Storm-1249, Storm-2227, and Storm-3069.
Troubleshooting wording now refers to Defender for Endpoint sensor onboarding and removes the statement that in-place migration is supported only for domain controllers. Two ontology links were also updated.
This period briefing was generated by AI from the tracked Microsoft Learn and Message Center changes.
The Emerald Sleet entry now links to a Microsoft Security blog, and the Storm-1516 entry was removed from the table.
The table adds or revises aliases, affiliations, origins, and references for multiple actors, including new associations for Citrine Sleet, Midnight Blizzard, and Storm-2603, plus entries for Storm-2195 and updated classifications for Storm-1249, Storm-2227, and Storm-3069.
Microsoft added documentation for the SyntheticMediaDetectionEvents table, which provides Microsoft Teams synthetic media detection events, including severity, confidence, maliciousness, source, user, and detection provider details.
Microsoft Defender for Identity will retire two classic alerts—Remote code execution attempt and pass-the-hash—by late November 2026. Users should create custom detection rules for RCE and rely on Defender for Endpoint for pass-the-hash monitoring. No compliance issues are identified.
The demonstration guide now uses a support matrix for inspection methods, agent modes, and minimum versions. It distinguishes agent-native inspection (`AiAgentProtection`) from network inspection (`AiAgentNetworkInspection`), removes Beta Channel update configuration steps, and adds known-issues guidance.
The matrix now lists Droid CLI, Factory App, Kimi Work, and Replit Agent, and identifies Alibaba Cloud as the provider for Qwen Code Desktop. The page date was also updated.
The documentation now specifies that both settings use 0 for Disabled, 1 for Block, and 2 for Audit.
The November 2026 update documents the SyntheticMediaDetectionEvents table in Microsoft Defender XDR advanced hunting, containing details about synthetic media detected in Microsoft Teams.
The documentation adds guidance for hunting deepfake detections in Microsoft Teams with the SyntheticMediaDetectionEvents advanced hunting table.
The page updates troubleshooting wording to refer to Defender for Endpoint sensor onboarding and removes the statement that in-place migration is supported only for domain controllers. Two ontology links were also updated.