# Use Defender for Identity alerts for detections, not complete audit history > Use Security alerts in Microsoft Defender for Identity to review this narrow operational decision without extending the source beyond its stated scope. - Canonical URL: https://update.dsesecurity.com/updates/use-identity-alerts-for-detections-not-complete-audit-history/ - Publisher: Detection Systems & Engineering (DSE Security) - Author: DSE Security Editorial Team - Published: 2026-08-27T12:13:01+00:00 - Modified: 2026-08-27T13:04:09+00:00 - Last reviewed by DSE: 2026-08-26 - Resource type: Playbook - DSE priority: Advisory - Topics: Cybersecurity, IT, Microsoft 365 & Identity - Reading time: 3 minutes ## What you need to know Use Security alerts in Microsoft Defender for Identity to review this narrow operational decision without extending the source beyond its stated scope. ## Potentially affected Teams, systems, services, or facilities within the stated scope of Security alerts in Microsoft Defender for Identity ## DSE recommendation Compare the observed state with the cited official source, document applicability and exceptions, and test any approved change with rollback safeguards. ## Article Keep this document to one review outcome: Use Defender for Identity alerts for detections, not complete audit history. Only the official source and traced locations below supply facts. Confirm applicability before acting. ## Source fact: The official [Security alerts in Microsoft Defender for Identity](https://learn.microsoft.com/en-us/defender-for-identity/alerts-overview) from Microsoft supports the following bounded statements: - Defender for Identity alerts describe suspicious activities and identify involved actors and computers with direct evidence links. The research record locates this support at Opening overview. - Microsoft explicitly says Defender for Identity is not an auditing or logging solution for every server operation and captures only data needed for detections and recommendations. The research record locates this support at Audit-boundary paragraph. These statements are the factual basis for this document. Do not extend them into a broader assurance. Review identity detections, contributing events, entities, alert logic, tuning, exclusions, investigation, and response decisions only where the source and recorded environment align. ## What the source does not establish Preserve separate authoritative audit and log-retention controls; alert absence is not proof that an activity did not occur. The citation is not a substitute for observed state, authorization, compliance evidence, or dependency health. Examine Active Directory, Windows DNS, sensor health, time, network visibility, cloud analytics, endpoint evidence, and security operations before translating the source into an operational decision. ## Applicability questions - For source statement 1 at Opening overview, which observable configuration, record, or test can confirm applicability here? - For source statement 2 at Audit-boundary paragraph, which observable configuration, record, or test can confirm applicability here? - Which deployed instance of identity detections, contributing events, entities, alert logic, tuning, exclusions, investigation, and response decisions will be compared with the source, and why that instance? - How will the review distinguish a source mismatch from a failure in Active Directory, Windows DNS, sensor health, time, network visibility, cloud analytics, endpoint evidence, and security operations? - Who approves the conclusion, exception, test window, and rollback threshold? ## DSE recommendation: DSE recommends using the cited source as the evidence anchor for this decision. Start with applicability, then compare the observed state with the cited source. Record the source location, examined part of identity detections, contributing events, entities, alert logic, tuning, exclusions, investigation, and response decisions, observed and expected states, owner, and reason for deviation. If the review warrants change, use a bounded implementation with prerequisites, test population, monitoring, abort criteria, and a rehearsed reversal. Sequence checks for Active Directory, Windows DNS, sensor health, time, network visibility, cloud analytics, endpoint evidence, and security operations and sanitize protected material before retention. ## Verification and evidence Keep the source locations Opening overview; Audit-boundary paragraph adjacent to the sanitized artifacts used for comparison. Prefer sanitized alerts, source events, entity timelines, tuning conditions, exclusion scope, analyst findings, and response outcomes, with enough identity and timing data for an independent recheck. Close the review only when the evidence, exception handling, resulting action, and after-state are linked. Schedule a new review after material technical, organizational, incident, or source changes; today’s observation is not a continuing guarantee. ## Official references - [Security alerts in Microsoft Defender for Identity](https://learn.microsoft.com/en-us/defender-for-identity/alerts-overview) — Microsoft ## Primary reference - Name: Security alerts in Microsoft Defender for Identity - Authority: Microsoft Learn - URL: https://learn.microsoft.com/en-us/defender-for-identity/alerts-overview - Source publication date: 2026-07-01 ## Citation and use Preferred citation: “Use Defender for Identity alerts for detections, not complete audit history,” DSE Security, https://update.dsesecurity.com/updates/use-identity-alerts-for-detections-not-complete-audit-history/ Publishing principles: https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/ Usage and citation policy: https://update.dsesecurity.com/usage/ Copyright © 2026 Detection Systems & Engineering. All rights reserved.