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 NewsMost of the 77 entries were documentation maintenance involving terminology, links, screenshots, and navigation. The consequential exceptions were a December 2026 Defender for Office 365 policy-matching change, the late-November retirement of two Defender for Identity alerts, Sentinel playbook and collector migration guidance, and a new Defender for Endpoint control for staged public preview features.
Beginning in December 2026, threat protection policies with multiple recipient types will use Match any (OR) instead of Match all (AND). Existing policies are not automatically converted, but modifying them can expand their scope, so review recipient conditions before making changes.
The Remote code execution attempt and pass-the-hash classic alerts are scheduled for retirement by late November 2026. Microsoft directs administrators to create custom detection rules for RCE and use Defender for Endpoint for pass-the-hash monitoring.
Alert-trigger playbooks and their Microsoft Sentinel Alert triggers remain supported, but direct invocation from analytics rules is deprecated. Configure automation rules for alerts from one or multiple analytics rules when playbooks must run automatically.
The data connector reference marks on-premises and online Exchange Security Insights collectors for migration to Azure Monitor and requires updating from the Azure Log Analytics HTTP Data Collector API to the Log Monitor API. Collector version 8.0.0.0 or later is advised.
A new portal page lets administrators enable or disable selected public preview features tenant-wide or by safe deployment channel. Features are off by default unless the tenant participated in the private preview, and the existing Preview features setting must be enabled to access the page.
Review recipient-scoped threat protection policies before modifying them after the December rollout. Replace the retiring Defender for Identity alert coverage by late November, migrate affected Sentinel playbooks and Exchange collectors, and enable the existing Defender for Endpoint Preview features setting before using individual preview controls.
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 Defender for Office 365 will localize the default "Mark and notify" email template based on users' Outlook language settings, improving clarity in user-reported message notifications. Rollout starts June 2026 globally, with no changes to message classification or custom templates. No action is required.
The page now refers to identity remediation actions and identity risk in Microsoft Defender instead of Microsoft Defender for Identity, with corresponding link text and metadata updates.
The documentation now states that a custom status cannot be deleted while assigned to cases.
Microsoft Defender for Office 365 will change recipient inclusion logic in threat protection policies from Match all (AND) to Match any (OR) when multiple recipient types are specified. This update, rolling out in December 2026, expands policy scope upon modification but does not auto-convert existing policies.
The permissions page now documents Read and Manage permissions for automation rules, playbooks, and integrations, plus permissions for executing and approving query, soft, and hard actions.
The documentation now states that selecting an entire service source applies the rule to all detection sources under it, including custom detections.
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.
The overview’s title, headings, setup instructions, RBAC label, and retention references now use “Microsoft Defender” instead of “Microsoft Defender XDR.” Metadata and ontology links were also updated.
The page now refers to Microsoft Defender instead of Microsoft Defender XDR, corrects a Microsoft Entra ID spelling error, and updates metadata and ontology links.
The page title, heading, and introductory text now refer to the Microsoft Defender advanced hunting schema instead of the Microsoft Defender XDR advanced hunting schema. Metadata was also refreshed.
The page metadata and ontology links were refreshed, and the schema-reference guidance now points to Microsoft Defender instead of Microsoft Defender XDR.
The page removes Copilot Studio real-time protection setup instructions, Power Platform onboarding details, App ID guidance, and related screenshots. It retains the note that alerts and incidents do not appear when the Microsoft 365 connector is disconnected.
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.
A new Defender portal page lets administrators enable or disable selected public preview features tenant-wide or by safe deployment channel. Features are off by default unless the tenant participated in the private preview.
The documentation describes generating a deployment tool with a Defender portal offboarding key, configurable expiration, and support for interactive or quiet command-line offboarding. The existing .offboarding-file method remains available.
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 page now documents inaccurate blocked-alert titles in Audit mode and a Claude Code limitation where tool responses may continue after a Block-mode alert.
The documentation now notes that Audit mode may incorrectly report a prompt injection block, and Claude Code may continue processing a tool response after a reported block in Block mode.
The documentation now states that portal downloads use a cloud-backed copy, not the device’s local quarantine. Cloud backup applies to files up to 100 MiB; larger files remain quarantined but cannot be downloaded from the portal. Collect file retrieves the current device path and may fail if quarantine removed the original.
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 routing guidance now notes that messages quarantined by the Common Attachments Filter may be quarantined again after release because of the return mail-flow path. It also clarifies that submissions to Microsoft should use the initial message version.
The guidance now states that malware and high-confidence phishing messages quarantined when MX points to Microsoft 365 cannot bypass their verdict when released.
The Configuration Analyzer guidance now specifies that both the Defender for Office 365 and Exchange Online permissions toggles under Email & collaboration must be Active. Two authoring links were also updated.
The page now states that the Defender for Office 365 and Exchange Online permissions toggles must both be active for the documented Unified RBAC applicability. Two ontology links were also updated.
The documentation now states that the guidance applies when both the Defender for Office 365 and Exchange Online permissions toggles under Email & collaboration are Active.
The documented requirement now says both the Defender for Office 365 and Exchange Online permissions toggles under Email & collaboration must be Active. The guidance applies only to the Microsoft Defender portal.
The documentation now states that both the Defender for Office 365 and Exchange Online permissions toggles under Email & collaboration must be active for Microsoft Defender XDR Unified RBAC to apply in the Defender portal.
The documentation now says both the Defender for Office 365 and Exchange Online permissions toggles under Email & collaboration must be Active. It previously referenced only the Defender for Office 365 toggle.
The documentation now says unified RBAC applies when both the Defender for Office 365 and Exchange Online permissions toggles are active under Email & collaboration, replacing the previous Defender for Office 365-only wording.
The documentation now says Unified RBAC applies when both the Defender for Office 365 and Exchange Online permissions toggles under Email & collaboration are Active.
The documentation now states that the Defender for Office 365 and Exchange Online permissions toggles under Email & collaboration must both be active for the unified RBAC configuration to apply.
The documentation now states that Microsoft Defender XDR Unified RBAC applies when both the Defender for Office 365 and Exchange Online permissions toggles under Email & collaboration are active.
The Safe Links policy documentation now states that unified RBAC applies when both the Defender for Office 365 and Exchange Online permissions toggles under Email & collaboration are active.
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.
The page title, description, and introductory guidance now refer to identity security capabilities in Microsoft Defender rather than only Defender for Identity. Two ontology links were also added.
The page title, description, introduction, and metadata links now refer to identity security in Microsoft Defender rather than Microsoft Defender for Identity. The guidance still describes custom unified RBAC roles that limit visibility to Active Directory domains or organizational units.
The page now states that identity remediation actions are performed in the Defender portal, updates ontology links, and uses shorter links to the required-permissions section for Disable, Enable, Revoke session, and Force password change.
The documented Microsoft Defender portal path now goes through Settings > Identities > General > Manage action accounts, with updated formatting for the Create new account button.
The documentation now states that Configuration partition SACL auditing applies to environments that currently have or previously had Microsoft Exchange.
The page title, description, and introductory text were revised to refer to identity account correlation rules in Microsoft Defender.
The page now describes remediating compromised identities in Microsoft Defender instead of compromised users in Defender for Identity. References to identity remediation actions, automatic attack disruption, and Response (manage) permissions were updated accordingly.
The page title, description, headings, and references were revised from “Microsoft Defender for Identity” to “Microsoft Defender.” Metadata and ontology links were also refreshed.
The Identity Inventory page now links to “Investigate users in Microsoft Defender” instead of “Microsoft Defender XDR.” Authoring, publication date, and AI-usage metadata were also updated.
The article title, description, headings, and introductory text now refer to SaaS security capabilities in Microsoft Defender rather than only Defender for Cloud Apps.
The article now refers to Microsoft Defender instead of Microsoft Defender XDR, clarifies that alerts and incidents are accessed in the Microsoft Defender portal, removes internal authoring links, and updates the screenshot description.
The documentation now states that App/instance admin, User group admin, Cloud Discovery global admin, and Cloud Discovery report admin assignments cannot be used in new configurations. Existing configurations remain supported.
The documentation now lists Microsoft Cloud Security Benchmark, security policies, exemptions, and regulatory compliance assessments as available in preview for Azure environments in the Defender portal.
The page now has clearer section headings, adds links for Security policies, Regulatory compliance, and Exemptions, and updates wording about CSPM capabilities being unified into Microsoft Security Exposure Management.
The page now covers the Microsoft Defender portal experience and adds screenshots for permissions, policy details, scope selection, rule selection, rule management, and Azure-to-Defender navigation.
The page now includes an Important notice, a link to Azure preview terms, and screenshots covering the Exemptions tab, unified RBAC permissions, exemption creation, and management actions.
The page now notes that the feature is available in the Microsoft Defender portal and links to the Supplemental Terms of Use for Microsoft Azure Previews.
The documentation marks the on-premises and online Exchange Security Insights collectors for migration to Azure Monitor and requires updating from the Azure Log Analytics HTTP Data Collector API to the Log Monitor API.
The documentation reorganizes the ASIM parser tables, adds links to parser definitions, distinguishes query-time and ingestion-time parsers, and clarifies that `pack=true` retains unmapped fields in `AdditionalFields`. It also adds native normalized entries and additional data sources.
The connector reference now marks the older Exchange Security Insights entries as deprecated and adds Azure Monitor entries. It also adds Menlo, Miro, QCrypton, and RedRays mappings and changes Cisco SD-WAN support flags to Yes.
The documentation now lists additional data lake-supported regions, including Canada East, Brazil, East Asia, Japan West, Korea, UAE Central, France South, Norway, Switzerland West, UK West, and more Australian regions.
The documentation now states that workspaces must be in a supported region to use data lake retention.
The data management overview now links to Data lake retention availability for supported-region information.
The article now covers Microsoft Defender SOC Logic Apps and generated playbooks, distinguishes them from Sentinel connector Logic Apps, and documents the required Defender unified RBAC, Azure RBAC, and investigation-page access.
The article now documents a unified Defender portal experience for connector and table management, transformations, and ingestion-health monitoring, with Overview, Connectors, and Tables tabs.
The Sentinel documentation now describes custom analytics on data lake and external tables using KQL, notebooks, and custom graphs. References to running Fabric pipelines with Lookup or KQL activities were removed.
The prerequisites page now directs administrators to search SAP Notes and KBAs using the exact error, SAP_BASIS release, and support package, and to confirm corrections with SAP before applying them.
The documentation now states that SAPConnectorOverview reports row counts only for legacy containerized-agent tables and excludes tables collected by the agentless data connector.
The normalized email schema now lists `EmailInteraction` alongside `EmailDelivery` and `EmailInspection` as allowed `EventType` values.
The documentation now explains how to use the Defender portal’s Data & connectors Overview tab to review connector counts, ingestion volume and growth, errors, table fluctuations, and ingestion latency, with links to connector and table details.
The documentation now explains that full user master ingestion is spread across the configured cycle, describes offset-in-seconds as a look-back buffer, and adds the force-utc parameter to use UTC when troubleshooting missing audit logs.
The article now states that alert-trigger playbooks and their Microsoft Sentinel Alert triggers remain supported, but direct invocation from analytics rules is deprecated. It updates the guidance to configure automation rules for alerts from one or multiple analytics rules.
The article now includes troubleshooting paths by symptom, diagnostic information to collect, an ABAPAuditLog query, and guidance on SAP releases, audit-log performance, delayed ingestion, user-data ingestion cycles, and time-zone offsets.
The exposure management documentation now recommends MAI Cyber (Preview) as the scan configuration for MDASH.
The page adds guidance on tailoring posture evaluations with policies and exemptions, including the Microsoft-managed MDC Baseline Policy, custom policies, exemption governance, and supported cloud-resource scope.
The page title and heading now include “(preview),” its custom metadata changed, and an embedded screenshot was removed.
The page title and heading now include “(preview),” its authoring metadata changed, and the environment-management screenshot was removed.
The fixed-inaccuracies report adds November 2026 entries, including MDVM support for six products and corrections to detection logic, vulnerability recommendations, tags, and product attribution.