Skip to content

Defender for Endpoint Onboarding Gaps

The question it answers: Which Intune-managed devices are not onboarded to Defender for Endpoint, or have an inactive or impaired sensor?

Every Windows and macOS device Intune manages should be onboarded to Defender for Endpoint and reporting. Devices that are not onboarded have no EDR; onboarded devices with an inactive or impaired sensor are blind spots. Defender Health covers antivirus state only.

Where in the appTenant › Defender & Security Operations › MDE Onboarding Gaps
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 Endpoint P1/P2 or Defender for Business.
Report id (API and MCP)tenant.secops.mde-onboarding
ColumnKeyType
SeveritySeverityStatus
StateCategoryText
DeviceSubjectLink
CheckSettingText
Sensor healthValueText
FindingFindingText
DetailDetailText
Last seenWhenDate
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 Endpoint P1/P2 or Defender for Business.

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

PermissionAPIWhat it allowsNote
Machine.Read.AllWindowsDefenderATPRead all machine profilesapplication permission on the ‘WindowsDefenderATP’ API
DeviceManagementManagedDevices.Read.AllMicrosoft GraphRead Microsoft Intune devices
Data sources it reads
  • GET https://api.security.microsoft.com/api/machines
  • GET /beta/deviceManagement/managedDevices (cached)
GET /ir-api/v1/reports/tenant.secops.mde-onboarding?size=100

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