Security checks / Check reference / Devices & compliance
Entra Device OS Version Lag
Medium Severity Microsoft 365 security check in the Devices & compliance domain.
Entra-registered Windows device is on a build that is no longer supported by Windows Update, so it cannot receive new security patches. The device is visible in Microsoft Entra ID but is not managed by Intune, and its reported osVersion is not among the currently supported Windows client or server builds. Siemserva runs this check automatically across your tenant and maps every finding to the compliance frameworks below.
Check summary
What this check verifies
Entra-registered Windows device is on a build that is no longer supported by Windows Update, so it cannot receive new security patches.
Why it matters
The device is visible in Microsoft Entra ID but is not managed by Intune, and its reported osVersion is not among the currently supported Windows client or server builds. Unsupported builds stop receiving cumulative security updates from Windows Update, leaving any new CVE on the device permanently unpatched.
How to fix it
Enroll the device in Intune (or another patch-management tool), then apply a Windows feature update to bring it onto a supported build. If the device is intentionally retired or out-of-scope, remove its Entra registration so it no longer appears in the directory.
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:
References
Related Devices & compliance checks
Common questions
What does the Entra Device OS Version Lag check verify?
Entra-registered Windows device is on a build that is no longer supported by Windows Update, so it cannot receive new security patches. 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 OS Version Lag finding?
Enroll the device in Intune (or another patch-management tool), then apply a Windows feature update to bring it onto a supported build. If the device is intentionally retired or out-of-scope, remove its Entra registration so it no longer appears in the directory. 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.