Skip to content

Defender for Identity Sensor Health

The question it answers: Are the Defender for Identity sensors running, and which health issues are open?

Defender for Identity watches domain controllers for Kerberoasting, DCSync, pass-the-hash and similar attacks - but only while its sensors run, its directory service account works and auditing is configured. Open health issues mean attacks on Active Directory may go undetected.

Where in the appTenant › Defender & Security Operations › Defender for Identity Health
WorkloadSecurity
KindFindings list · dashboard tile
DataRead from Microsoft 365 when someone first opens it, then kept for the report cache lifetime (Settings > Data & cache, 1 hour unless changed).
LicenceMicrosoft Defender for Identity (or Microsoft 365 E5 Security).
Report id (API and MCP)tenant.secops.mdi-health
ColumnKeyType
SeveritySeverityStatus
Issue typeCategoryText
IssueSubjectLink
CheckSettingText
Severity / statusValueText
RecommendationFindingText
Sensors / domainsDetailText
UpdatedWhenDate
CountNumberNumber

A findings list hides columns that no row fills. Severity is Critical, Serious, Warning, OK or Info; rows rated Critical, Serious or Warning need attention (Working with findings).

Licence: Microsoft Defender for Identity (or Microsoft 365 E5 Security).

Application permissions on the IntensiveReports app registration (all permissions):

PermissionAPIWhat it allowsNote
SecurityIdentitiesHealth.Read.AllMicrosoft GraphRead all identity security health issues
Data sources it reads
  • GET /v1.0/security/identities/healthIssues
GET /ir-api/v1/reports/tenant.secops.mdi-health?size=100

An AI assistant reads it with the MCP tool get_report and the id tenant.secops.mdi-health. The client needs the Read grant for Security. See Using the API.