'%3e%3cpath%20d='M8%200C12.4183%200%2016%203.58172%2016%208C16%2012.4183%2012.4183%2016%208%2016C3.58172%2016%200%2012.4183%200%208C0%203.58172%203.58172%200%208%200ZM11.6162%204.38379C11.2257%203.99337%2010.5927%203.99338%2010.2021%204.38379L8%206.58594L5.79785%204.38379C5.40732%203.99334%204.77429%203.99329%204.38379%204.38379C3.99331%204.77429%203.99335%205.40733%204.38379%205.79785L6.58594%208L4.38379%2010.2021C3.99348%2010.5927%203.99341%2011.2257%204.38379%2011.6162C4.77426%2012.0066%205.40734%2012.0065%205.79785%2011.6162L8%209.41406L10.2021%2011.6162C10.5927%2012.0066%2011.2257%2012.0067%2011.6162%2011.6162C12.0067%2011.2257%2012.0066%2010.5927%2011.6162%2010.2021L9.41406%208L11.6162%205.79785C12.0066%205.40735%2012.0066%204.77429%2011.6162%204.38379Z'%20fill='%23080E17'%20fill-opacity='0.46'/%3e%3c/g%3e%3cdefs%3e%3cclipPath%20id='clip0_3761_713'%3e%3crect%20width='16'%20height='16'%20fill='white'/%3e%3c/clipPath%3e%3c/defs%3e%3c/svg%3e)
How to Fix Android 14 Intune Compliance Policies Not Assigned
Question details
Users managing Android 14 devices via Microsoft Intune are experiencing an issue where compliance policies are reported as 'not assigned', despite being properly targeted to users or devices.
- Product
- Microsoft Intune
- Device & OS
- Android 14
- Scenario
- Enrolling Android 14 devices and pushing compliance policies in Microsoft Intune.
- Observed behavior
- Devices report that compliance policies have not been assigned, and configurations are not pushed to randomly selected devices after enrollment.
Ensure you have administrative access to the Microsoft Intune admin center and verify that your tenant is updated to the latest service release.
Apply the Intune 2504 Service Release Update
Microsoft identified a bug causing this assignment failure and deployed a fix starting from the 2504 service release.
Microsoft acknowledged an issue where policies and configurations fail to push to randomly selected Android 14 devices post-enrollment. The official fix is included in the 2504 service release.
Log in to the Microsoft Intune admin center. Navigate to Tenant administration > Tenant status to verify your current service release version.
If your tenant is not yet on release 2504, monitor the tenant status. Microsoft rolls out updates globally, so it may take a few days to reach your region.
Once updated, go to Devices > Compliance policies and check the assignment status of your Android 14 devices to see if the policies are now successfully pushed.
Escalate to Microsoft Support for Persistent Issues
If the issue continues after the 2504 update, you may need to open a support ticket as some users reported the problem persisting.
Manage Your Documents Effectively with WPS Office
While you troubleshoot device management issues, ensure your team stays productive with WPS Office. It's a free, lightweight, and highly compatible alternative to Microsoft Office, perfect for creating, editing, and sharing documents across all mobile and desktop platforms.
Frequently Asked Questions
Why does Microsoft Intune say compliance policies are not assigned on Android 14?
This can occur due to a known bug in Intune where policies and configurations fail to push to randomly selected devices after enrollment. Microsoft addressed this specific issue in the 2504 service release.
How can I check my Microsoft Intune service release version?
You can check your tenant's version by logging into the Microsoft Intune admin center and navigating to 'Tenant administration' followed by 'Tenant status'.
What should I do if the 2504 release doesn't fix the policy issue?
Some users have reported that the issue persists even after the update. In this case, collect device logs and contact Microsoft Support directly through the admin center to investigate further.
