Security checks / Check reference / Intune configuration
Intune Policy Autopatch Updatable Asset Group Not Enrolled
High Severity Microsoft 365 security check in the Intune configuration domain.
Entra security group is registered as a Windows Autopatch updatable asset but its devices are not enrolled with the deployment service. Registering an Entra group as an updatableAssetGroup creates a reference but does not auto-sync the group's device members into the deployment service. Siemserva runs this check automatically across your tenant and maps every finding to the compliance frameworks below.
Check summary
What this check verifies
Entra security group is registered as a Windows Autopatch updatable asset but its devices are not enrolled with the deployment service.
Why it matters
Registering an Entra group as an updatableAssetGroup creates a reference but does not auto-sync the group's device members into the deployment service. Each device has to be explicitly enrolled via the Autopatch enrollment action. When the group has more devices in Entra than enrolled with the deployment service, any deployment targeting the group reaches fewer endpoints than the operator expects. With zero enrolled devices the deployment is functionally a no-op while the admin UI shows it as healthy. This is the most common cause of 'Autopatch is configured but nothing happens' tenant complaints.
How to fix it
Open the Intune admin center (Devices -> Windows -> Windows updates -> Enrollment) and run the enroll-devices flow against the affected group, or call POST /admin/windows/updates/updatableAssets/microsoft.graph.windowsUpdates.enrollAssetsById passing the group's member device ids. After enrollment, the group's deployment service members count should match the Entra group size.
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 Intune configuration checks
Common questions
What does the Intune Policy Autopatch Updatable Asset Group Not Enrolled check verify?
Entra security group is registered as a Windows Autopatch updatable asset but its devices are not enrolled with the deployment service. It is a High Severity check in the Intune configuration domain, one of the 650+ checks Siemserva runs across Microsoft 365, Intune, Defender, and Entra ID.
How do I fix a Intune Policy Autopatch Updatable Asset Group Not Enrolled finding?
Open the Intune admin center (Devices -> Windows -> Windows updates -> Enrollment) and run the enroll-devices flow against the affected group, or call POST /admin/windows/updates/updatableAssets/microsoft.graph.windowsUpdates.enrollAssetsById passing the group's member device ids. After enrollment, the group's deployment service members count should match the Entra group size. 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-3, PV-6. 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.