Microsoft Defender XDR
General

Investigate Users

In brief

The page now refers to identity remediation actions and identity risk in Microsoft Defender instead of Microsoft Defender for Identity, with corresponding link text and metadata updates.

What Defender admins need to know

Administrators should use the updated Microsoft Defender remediation-actions link and terminology when consulting this guidance.

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.

From the Overview page, use the Actions menu to trigger remediation actions on the identity. Actions apply to the accounts associated with the identity and depend on which connectors are enabled, spanning on-premises Active Directory, Microsoft Entra ID, identity and access management (IAM) systems, and SaaS apps. Available actions can include disabling or enabling accounts, revoking sessions, forcing a password change, and marking the user as compromised. You can also view the identity's account settings.

For the full list of remediation actions and the identity providers and connected apps that support them, see Identity remediation actions in Microsoft Defender.

Screenshot of the identity page with the identity actions menu showing.

| Risk Trend | A line chart that shows how the risk score changed over a configurable time period (for example, 30 days). Select Go to timeline to view the full activity timeline. | | Likelihood of Compromise Details | A bar chart that shows alert distribution across MITRE ATT&CK categories, with a filterable alert table. Use the Active alerts only toggle to focus on unresolved alerts. Filter by account set, status, or kill chain stage. |

The Confirm safe action now includes Reset risk for both the identity risk score and the Microsoft Entra risk level. For more information, see Identity remediation actions in Microsoft Defender.

Note

Identity risk in Microsoft Defender for Identity uses automated decay logic to allow SOC prioritization. If no new risk factors are detected, the identity risk score decreases over time. Microsoft Entra ID maintains its own risk level independently and doesn't apply decay. As a result, you might see an Entra risk level with no corresponding identity risk score when the Entra risk update time is older than 30 days.

Timeline tab