Security checks / Check reference / Devices & compliance

Entra Device Not In Defender Coverage

Medium Severity Microsoft 365 security check in the Devices & compliance domain.

Entra-registered Windows device has no matching Microsoft Defender for Endpoint machine record, so the audit cannot determine per-CVE patch posture. The device is registered in Microsoft Entra ID but does not appear in the Defender for Endpoint machine list. Siemserva runs this check automatically across your tenant and maps every finding to the compliance frameworks below.

Medium SeverityDevices & compliance

Check summary

Severity
Medium
Domain
Devices & compliance
Rank in domain
3
Frameworks
6

What this check verifies

Entra-registered Windows device has no matching Microsoft Defender for Endpoint machine record, so the audit cannot determine per-CVE patch posture.

Why it matters

The device is registered in Microsoft Entra ID but does not appear in the Defender for Endpoint machine list. Without a Defender machine record, the audit has no per-CVE ground truth for this device and can only infer patch posture from the device's reported osVersion. EDR telemetry is also absent, so on-device threats would go undetected.

How to fix it

Onboard the device to Microsoft Defender for Endpoint using an Intune compliance policy, Group Policy, or the Defender onboarding script. After onboarding, re-run the scan to see per-CVE missing-patch findings backed by Defender ground truth.

Siemserva flags every tenant where this check fails and, with Senserva Trustworthy AI remediation, can propose a validated fix you approve before it applies.

Ask your own AI about this check

Copy this prompt into Claude, ChatGPT, or Copilot. The facts are included, sourced from this page.

Compliance framework mappings

Findings from this check serve as evidence for:

SCuBAMCSBNISTSOC2CISHIPAAMCSB ES-1MCSB ES-2MCSB ES-3

References

learn.microsoft.com/entra/identity/devices/overviewlearn.microsoft.com: /mem/intune/protect/device-compliance-get-started...learn.microsoft.com: /security/benchmark/azure/mcsb-identity-management...

Related Devices & compliance checks

Entra Device OS Version LagDevice ChangeDevice Compliance Expiration Date TimeDevice Endpoint Detection And ResponseDevice Has Outdated Android Operating SystemDevice Has Outdated IOS Operating SystemDevice Has Outdated Mac OS Operating SystemDevice Has Outdated Windows Operating System

Common questions

What does the Entra Device Not In Defender Coverage check verify?

Entra-registered Windows device has no matching Microsoft Defender for Endpoint machine record, so the audit cannot determine per-CVE patch posture. It is a Medium Severity check in the Devices & compliance domain, one of the 650+ checks Siemserva runs across Microsoft 365, Intune, Defender, and Entra ID.

How do I fix a Entra Device Not In Defender Coverage finding?

Onboard the device to Microsoft Defender for Endpoint using an Intune compliance policy, Group Policy, or the Defender onboarding script. After onboarding, re-run the scan to see per-CVE missing-patch findings backed by Defender ground truth. Siemserva ranks the finding by Severity and, with Senserva Trustworthy AI, can propose a validated, approve-before-apply configuration fix.

Which compliance frameworks does this check evidence?

Findings from this check map to SCuBA, MCSB, NIST, SOC2, CIS, HIPAA, and MCSB controls ES-1, ES-2, ES-3. That mapping is what turns a scan finding into audit evidence.

Can I ask my own AI about this check?

Yes. This page includes a free copy-paste AI prompt carrying the check's facts: what it verifies, the risk, the remediation, and the framework mappings. Paste it into Claude, ChatGPT, or Copilot; cite-worthy detail without giving an AI access to your tenant.

All 672 checks with severities and mappings: the Microsoft 365 security checks catalog.

Sponsored by Senserva

Siemserva by Senserva runs this check, Entra Device Not In Defender Coverage for example, across your own tenant: which tenants pass, which fail, ranked by Severity with the evidence attached.

  • 650+ Microsoft 365, Intune, Defender, and Entra ID checks in one scan
  • Findings mapped to SCuBA, CIS, NIST, HIPAA, SOC 2, and MCSB for audit-ready evidence
  • Senserva Trustworthy AI driven configuration remediation: validated, approve-before-apply fixes
  • Optional AI Enhanced Reporting: plain-language summaries and recommended next steps written into your reports
  • Multi-tenant and MSP practices, with bulk tenant audits and client-ready reporting
Compliance Status Report
Entra Device Not In Defender Coverage across 2 tenants, ranked by Severity
23
FAILING
87
PASSING
41
OTHER FINDINGS
CHECKSEVERITYSTATUSFINDINGS
Entra Device Not In Defender CoverageMediumFAILING23
MFA for all usersCritical-11
Legacy authentication blockedHigh-6
Estimated report, sample data for illustration
Get Going with Senserva Senserva compliance Built for IT admins, security teams, and auditors, with audit-ready evidence. Senserva is a Microsoft Intelligent Security Association member.
Microsoft 365 compliance and audit evidence
See this check's evidence trail, click to play

How findings become audit evidence, in two minutes. Watch page · All videos.

Reference: the compliance and audit guide, and the full checks catalog.
Data notice: check definitions describe what Siemserva verifies and are provided as is, for informational purposes only, without warranty of any kind. Framework mappings are informational and do not constitute compliance advice; confirm requirements with your assessor. All use of this data is subject to the Senserva EULA.