Map Defender-format identity alert names by stable alert ID

Treat this document as a focused evidence review: Map Defender-format identity alert names by stable alert ID. Only the official source and traced locations below supply facts. Confirm applicability before acting.

Source fact:

The official Microsoft Defender for Identity alerts in Microsoft Defender format from Microsoft supports the following bounded statements:

• Classic and Defender formats use the same underlying Defender for Identity sensor detections but differ in structure, naming, and categorization. The research record locates this support at Opening format comparison.
• Alert names differ in the XDR structure while alert IDs remain consistent between the two formats. The research record locates this support at Alert ID note.

Only the traced statements above are asserted as source facts. Apply the review to identity detections, contributing events, entities, alert logic, tuning, exclusions, investigation, and response decisions after confirming that the source and deployed context match.

What the source does not establish

A stable ID supports mapping; it does not guarantee unchanged evidence, severity, detection logic, or response guidance over time. 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 format comparison, which observable configuration, record, or test can confirm applicability here?
• For source statement 2 at Alert ID note, 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. Begin by recording scope and current state before deciding whether a change is warranted. 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.

An implementation decision needs an owner, approved window, prechecks, observable outcome, stop authority, and rollback path. Validate Active Directory, Windows DNS, sensor health, time, network visibility, cloud analytics, endpoint evidence, and security operations before and after the test, and store only sanitized operational evidence.

Verification and evidence

A reviewer should be able to retrace the decision from Opening format comparison; Alert ID note through sanitized alerts, source events, entity timelines, tuning conditions, exclusion scope, analyst findings, and response outcomes. Record what was collected, where, when, by whom, and which system or role it represents.

Retain the starting state, authorization, execution record, outcome, deviation, and final state as one review package. Move disruptive checks to an approved test path. Reopen the decision when versions, design, dependencies, ownership, or official guidance changes.

Official references

• Microsoft Defender for Identity alerts in Microsoft Defender format — Microsoft