Skip to content

Defender Antivirus Health

The question it answers: Which Windows devices have Defender Antivirus off, real-time or tamper protection disabled, outdated signatures or a pending reboot?

Windows devices whose Microsoft Defender Antivirus is off, has real-time or tamper protection disabled, runs on outdated signatures, or needs a reboot to finish remediation - as reported to Intune. A device with protection off is the first place ransomware lands.

Where in the appIntune › Endpoint Security & Readiness › Defender Antivirus Health
WorkloadIntune
KindTable · dashboard tile
DataA scan: it runs only when someone presses Run scan (or calls the API’s scan action) and can take minutes. The last result is kept until the next scan.
LicenceMicrosoft Intune (Windows devices with Microsoft Defender Antivirus).
Report id (API and MCP)intune.endpoint.defender-health
ColumnKeyType
DeviceDeviceNameLink
UserUserPrincipalNameText
FindingsFindingsStatus
StateDeviceStateText
SignaturesSignatureVersionText
Last reportedLastReportedDateTimeDate
FilterKey (API)On when the page opens
Only devices with a findingfindingsYes

Licence: Microsoft Intune (Windows devices with Microsoft Defender Antivirus).

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

PermissionAPIWhat it allowsNote
DeviceManagementManagedDevices.Read.AllMicrosoft GraphRead Microsoft Intune devices
Data sources it reads
  • GET /beta/deviceManagement/managedDevices
  • GET /v1.0/deviceManagement/managedDevices/{id}/windowsProtectionState (scan)
GET /ir-api/v1/reports/intune.endpoint.defender-health?size=100
GET /ir-api/v1/reports/intune.endpoint.defender-health?filter=findings
POST /ir-api/v1/reports/intune.endpoint.defender-health/scan

An AI assistant reads it with the MCP tool get_report and the id intune.endpoint.defender-health. The client needs the Run scan grant for Intune. See Using the API.