Microsoft Defender for Identity
Identity protection

Role groups for identity security in Microsoft Defender - Microsoft Defender for Identity | Microsoft Learn

In brief

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.

What Defender admins need to know

Administrators should use the updated terminology when applying the role-group and Microsoft 365 RBAC guidance. No action is specified.

Summaries are generated from the documentation change itself.

Documentation change

The comparison below shows only the changed extract. Use the full-page view for complete context.

Role groups for identity security in Microsoft Defender - Microsoft Defender for Identity | Microsoft Learn

Identity security capabilities in Microsoft Defender for Identity offersuse role-based security to safeguard data according to your organization's specific security and compliance needs. We recommend that you use role groups to manage access to Defender for Identity,identity security capabilities in Microsoft Defender, segregating responsibilities across your security team and granting only the amount of access that users need to do their jobs.

Unified role-based access control (RBAC)

Users that are already have the Security Administrators on your tenant's Microsoft Entra ID are also automatically Defender for Identity administrator. Microsoft Entra Security Administrators don't need extra permissions to access Defender for Identity.identity security capabilities in Microsoft Defender.

For other users, enable and use Microsoft 365 role-based access control (RBAC) to create custom roles and to support more Entra ID roles such as Security operator or Security Reader by default to manage access to Defender for Identity.identity security capabilities in Microsoft Defender.

Important