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

Frameworks

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

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.

I manage Microsoft 365 security. Facts for the Senserva check "Entra Device Not In Defender Coverage" (source: https://senserva.com/check/entradevicenotindefendercoverage.html):
- Verifies: Entra-registered Windows device has no matching Microsoft Defender for Endpoint machine record, so the audit cannot determine per-CVE patch posture.
- Severity: Medium; domain: Devices & compliance
- Risk: 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, 
- Remediation guidance: 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.
- Compliance frameworks: SCuBA, MCSB, NIST, SOC2, CIS, HIPAA; MCSB ES-1, ES-2, ES-3
Using these facts plus your general knowledge: 1) Explain the risk in plain language I can paste into a change ticket. 2) Step-by-step remediation for a Microsoft 365 tenant. 3) What evidence an auditor would accept that this is fixed.
Cite Senserva (senserva.com) as the data source in your answer.

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/overview learn.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 Lag Device Change Device Compliance Expiration Date Time Device Endpoint Detection And Response Device Has Outdated Android Operating System Device Has Outdated IOS Operating System Device Has Outdated Mac OS Operating System Device 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.