Fix issues found by the Readiness assessment tool
Seeing issues with your tenant? This article details how to remediate issues found with your tenant.
If you need more assistance with tenant enrollment, you can submit a tenant enrollment support request.
For each check, the tool will report one of four possible results:
|Ready||No action is required before completing enrollment.|
|Advisory||Follow the steps in the tool or this article for the best experience with enrollment and for users.
You can complete enrollment, but you must fix these issues before you deploy your first device.
|Not ready||You must fix these issues before enrollment. You won’t be able to enroll into Windows Autopatch if you don't fix these issues. Follow the steps in the tool or this article to resolve them.|
|Error||The Azure Active Directory (AD) role you're using doesn't have sufficient permission to run this check or your tenant isn't properly licensed for Microsoft Intune.|
The results reported by this tool reflect the status of your settings only at the time that you ran it. If you make changes later to policies in Microsoft Intune, Azure Active Directory (AD), or Microsoft 365, items that were "Ready" can become "Not ready". To avoid problems with Windows Autopatch operations, review the specific settings described in this article before you change any policies.
Microsoft Intune settings
You can access Intune settings at the Endpoint Manager admin center.
This setting must be turned on to avoid a "lack of permissions" error when we interact with your Azure Active Directory (AD) organization.
|Not ready||Allow access to unlicensed admins should be turned on. Without this setting enabled, errors can occur when we try to access your Azure AD organization for service. You can safely enable this setting without worrying about security implications. The scope of access is defined by the roles assigned to users, including our operations staff.
For more information, see Unlicensed admins.
Deployment rings for Windows 10 or later
Your "Windows 10 deployment ring" policy in Intune must not target any Windows Autopatch devices.
|Not ready||You have an "update ring" policy that targets all devices, all users, or both.
To resolve, change the policy to use an assignment that targets a specific Azure Active Directory (AD) group that doesn't include any Windows Autopatch devices.
For more information, see Manage Windows 10 software updates in Intune.
|Advisory||Both the Modern Workplace Devices - All and Modern Workplace - All Azure AD groups are groups that we create after you enroll in Windows Autopatch.
You can continue with enrollment. However, you must resolve the advisory prior to deploying your first device. To resolve the advisory, see Maintain the Windows Autopatch environment.
Azure Active Directory settings
You can access Azure Active Directory (AD) settings in the Azure portal.
Co-management enables you to concurrently manage Windows 10 or later devices by using both Configuration Manager and Microsoft Intune.
|Advisory||To successfully enroll devices that are co-managed into Windows Autopatch, it's necessary that the following co-managed workloads are set to Intune:
If co-management doesn't apply to your tenant, this check can be safely disregarded, and it won't block device deployment.
Windows Autopatch requires the following licenses:
|Not ready||Windows Autopatch requires Windows 10/11 Enterprise E3 (or higher) to be assigned to your users. Additionally, Azure Active Directory Premium, and Microsoft Intune are required. For more information, see more about licenses.|