Microsoft Defender for Identity
Identity protection

Identity security health issues in Microsoft Defender - Microsoft Defender for Identity | Microsoft Learn

In brief

The page title, description, and body now refer to identity security health issues and deployments in Microsoft Defender instead of Microsoft Defender for Identity. The existing sensor and domain-related alert guidance remains, with the page metadata date updated.

What Defender admins need to know

No administrator action is required.

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.

Identity security health issues in Microsoft Defender for Identity health issues - Microsoft Defender for Identity | Microsoft Learn

The Health issues page in Microsoft Defender for Identity Health Issues page lists issues affecting your Defender for Identityidentity security deployment and sensors. It alerts you to detected problems that might result from configuration or environmental factors.

For v3.x sensors, configure automatic Windows event auditing to help prevent issues related to Windows event collection. Before following a remediation procedure, check the health issue table for the applicable sensor version.

Health issues page

The Microsoft Defender for Identity Health issues page lets you know when there's a problem with yourin Microsoft Defender for Identity workspace, by raising a health issue. You can seeraises health issues for bothproblems affecting your general Defender for Identityidentity security environment andor specific sensors.

Defender for Identity supports the following types of health alerts:

  • Closed: A health issue is automatically marked as Closed when Microsoft Defender for Identity detects that the underlying issue is resolved. If you have the Azure ATP (workspace name) Administrator role, you can also manually close a health issue.
  • Suppressed: If you have Azure ATP (workspace name) Administrators permissions, you can suppress the health alert for seven days. Suppress a health alert if you're aware of an expected temporary known issue, for example, taking down a machine for maintenance.

For example, if a domain controller is taken offline for maintenance, a "Sensor stopped communicating" alert might be triggered. You can use the API to change the alert status from Open to Suppressed. After the domain controller is back online, revert the status to Open and let Microsoft Defender for Identity close the alert automatically when the issue is resolved.

Review health issue details

Note

In some v3 sensor environments, health alerts about Windows event auditing might persist even when Windows auditing is correctly configured. This primarily occurs with manual auditing configuration, such as using Group Policy or PowerShell. The sensor remains healthy and detections aren't affected. To resolve, enable Automatic Windows auditing configuration in the Microsoft Defender for Identity portal under Settings > Identities > Advanced features.

The tables in this section list all health issues by component, with causes and resolution steps.