Advanced Hunting Identityinfo Table
Doc updateThe documentation now lists IdentityId, SourceProvider, RiskScore, RiskScoreUpdateTime, and TimeGenerated, and updates descriptions or data types for Timestamp, State, and UserAccountControl.
Daily Defender NewsEvery tracked change across Microsoft Defender documentation, in plain English. Browse the archive from 1 January 2026 → About this project →
Administrators using the existing AI agent onboarding experience must complete the documented steps by December 23, 2026, because blocking settings will not migrate when that experience ends on December 2. Runtime-protection guidance also warns that alert prompt snippets are unredacted and may contain conversations, sensitive data, and secrets. Separately, Defender for Cloud Apps is preparing App Governance permission changes for selected Entra roles in December 2026; Defender for Containers guidance requires Linux kernel 5.15 or later for the latest sensor capabilities; and Defender for Identity v3.x activation without Defender for Endpoint is now allowed in government clouds. The remaining updates are mainly hunting-schema, coverage-label, terminology, and integration-prerequisite clarifications, including Azure region and Azure OpenAI Responses API requirements for AI Code Security.
Administrators using the existing onboarding experience must complete the documented steps by December 23, 2026. The experience ends December 2, and its blocking settings will not migrate; completing the steps preserves real-time protection.
Configuration guidance now warns that prompt snippets shown in alerts are not redacted and may contain conversations, sensitive data, and secrets. Administrators should account for that exposure when reviewing or sharing alerts.
The December 2026 Defender for Cloud Apps rollout adds policy-management rights to Cloud App Security Administrators and removes some permissions from Compliance Administrators and Compliance Data Administrators with Unified RBAC support. Review and update role assignments accordingly.
The support matrix states that the latest Defender sensor capabilities require Linux Kernel 5.15 or later. Kernel 5.4 or later supports limited functionality, so clusters on 5.4 through 5.14 may not receive the latest capabilities.
Updated guidance resolves the previous limitation on activating Defender for Identity Sensor v3.x without Defender for Endpoint in government cloud environments.
This period briefing was generated by AI from the tracked Microsoft Learn and Message Center changes.
The documentation now lists IdentityId, SourceProvider, RiskScore, RiskScoreUpdateTime, and TimeGenerated, and updates descriptions or data types for Timestamp, State, and UserAccountControl.
The table now removes two Defender risk fields, adds SourceProviderRiskLevelDetails, SourceSystem, and TimeGenerated, corrects field names, and changes SourceProviderRiskLevel from dynamic to string.
The documentation no longer names specific third-party detection engines. It now states only that data is available when using an approved Microsoft or third-party engine.
The documentation now states that administrators using the existing onboarding experience must act by December 23, 2026 because their blocking settings will not migrate when that experience ends on December 2.
Microsoft Defender for Cloud Apps is updating App Governance permissions for select Microsoft Entra roles with Unified RBAC support, rolling out December 2026. Cloud App Security Administrators gain policy management rights; Compliance Administrators and Compliance Data Administrators lose some permissions. Admins should review and update role assignments accordingly.
The documentation now describes the coverage as “High-severity cloud alerts, including containers (Preview)” and updates the page metadata.
The page now states that sensitive data and secrets may appear unredacted in prompt snippets shown in alerts. It also links to current Prompt Evidence Collection details and notes that Intune template help text is being finalized during preview.
The documentation now states that prompt snippets in alerts are not redacted and may contain conversations, sensitive data, and secrets.
The previous limitation has been resolved, allowing Defender for Identity Sensor v3.x activation without Defender for Endpoint in government cloud environments.
The troubleshooting page no longer includes the note that activating Defender for Identity v3.x sensors without Defender for Endpoint was temporarily unsupported in government cloud environments. The page date and authoring metadata were also updated.
The page now explains that the Defender for Cloud extension updates integration information, applies Azure Arc proxy settings, retains onboarding and tenant association, and preserves existing settings. Windows installations remain unchanged; Linux installations can upgrade when automatic updates are enabled.
The support matrix states that the latest Defender sensor capabilities require Linux Kernel 5.15 or later, while Kernel 5.4 or later supports limited functionality.
The page now lists Azure region identifiers, notes that Microsoft Foundry integration requires Azure OpenAI Responses API support, and identifies UAE as CLI-only. It also documents optional MAI Cyber model integration and its available Foundry regions.