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.
Senserva provides Three Free Unlimited Audits, including all tenants and full Claude MCP.Start my Audit
Check summary
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.
Find this in your own Microsoft 365
This page is the public reference for one check. Siemserva by Senserva runs it, and 650+ others, against your own tenant: it shows exactly where Entra Device Not In Defender Coverage is failing across your environment, ranks it against everything else by real risk, maps it to the frameworks your auditors ask about, and attaches a validated fix you approve before it applies.
Your Three Free Unlimited Audits cover all of it, free with registration: 1 scan to find, 2 to review your fixes.
Built for the people who own this outcome: security and IT teams closing gaps, auditors and compliance teams gathering evidence, and MSPs and MSSPs running it across every client tenant.
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:
References
Related Devices & compliance checks
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.