Move Defender for Identity access to least-privileged unified RBAC roles

Frame this document as a source-led configuration and assurance check: Move Defender for Identity access to least-privileged unified RBAC roles. Only the official source and traced locations below supply facts. Confirm applicability before acting.

Source fact:

The official Microsoft Defender for Identity role groups from Microsoft supports the following bounded statements:

• Microsoft recommends role groups that segregate security-team responsibilities and grant only the access needed for each job. The research record locates this support at Opening least-privilege guidance.
• New Defender for Identity tenants from March 2, 2025 can configure permissions only through Microsoft Defender XDR Unified RBAC, while earlier role assignments are retained. The research record locates this support at Unified RBAC transition note.

Keep the evidence boundary at these traced claims. They support a review of identity detections, contributing events, entities, alert logic, tuning, exclusions, investigation, and response decisions; they do not support conclusions outside the source’s stated conditions.

What the source does not establish

Map current duties and emergency access before changing roles; inherited tenant roles and legacy assignments require explicit review. 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 least-privilege guidance, which observable configuration, record, or test can confirm applicability here?
• For source statement 2 at Unified RBAC transition 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. Anchor the review in the cited section and keep observation separate from interpretation. 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.

Do not move from citation to production in one step. Pilot the decision where practical, observe agreed signals, retain a reversal point, and verify Active Directory, Windows DNS, sensor health, time, network visibility, cloud analytics, endpoint evidence, and security operations. Handle credentials, keys, recovery data, and personal information through approved secure channels.

Verification and evidence

Tie each conclusion back to Opening least-privilege guidance; Unified RBAC transition note and to observable material such as sanitized alerts, source events, entity timelines, tuning conditions, exclusion scope, analyst findings, and response outcomes. Preserve provenance and stable identifiers without copying secrets into the evidence set.

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

• Microsoft Defender for Identity role groups — Microsoft