'%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 Intune Devices Not Receiving Configuration Profiles
Question details
User needs to resolve an issue where devices in Microsoft Intune fail to receive assigned configuration profiles or report hardware and application data.
- Product
- Microsoft Intune
- Device & OS
- not provided
- Scenario
- An administrator is managing Azure AD joined devices and attempting to deploy configuration profiles via Microsoft Endpoint Manager.
- Observed behavior
- Devices successfully appear in the Intune portal but do not receive the assigned configuration profiles, and fail to report application or hardware information back to the service.
Ensure you have administrative access to the Microsoft Endpoint Manager admin center and that the affected devices are powered on with an active internet connection to synchronize policies.
Verify Device Enrollment and Assignment Scope
Check the core enrollment details in the Intune portal to ensure the device is fully managed by MDM and correctly targeted by the configuration profile.
A common reason devices fail to receive profiles is that they are only Azure AD registered rather than fully enrolled in Intune MDM, or they fall outside the profile's assignment scope.
Log into the Microsoft Endpoint Manager admin center. Navigate to Devices > All devices. Locate the affected device and verify that the 'Managed by' column displays 'Intune'.
Ensure the device is fully enrolled in Mobile Device Management (MDM). Devices that are solely 'Azure AD registered' without MDM enrollment cannot process Intune configuration profiles.
Go to Devices > Configuration profiles and select the profile that is failing to apply. Click on the 'Assignments' tab and ensure the specific user or device is part of the Included groups and not listed in Excluded groups.
Check the profile properties to ensure the target platform (e.g., Windows 10 and later) matches the operating system of the affected device.
Force a Manual Device Sync and Review Logs
Manually trigger a synchronization to force the device to check in with Intune, then review diagnostic logs if the profile still fails to apply.
Consult the Microsoft Intune Community Hub
If enrollment and assignment settings are correct but the issue persists, post your details to the official Intune community for specialized administrative support.
Simplify Your Workflow with WPS Office
While managing enterprise device configurations via Microsoft Intune can be highly complex, choosing the right office software doesn't have to be. WPS Office is a lightweight, free alternative to Microsoft Office that offers seamless compatibility and a familiar interface without heavy administrative deployment overhead.
- 1. Download the software: Visit the official WPS Office website to download the free installer directly to your device.
- 2. Install on your device: Run the installer. WPS Office installs quickly without requiring complex MDM enrollment or configuration policies.
- 3. Start editing: Open WPS Office and instantly view, edit, or create Microsoft Office-compatible documents without signing into complex enterprise portals.
Frequently Asked Questions
Why does my Intune configuration profile status show as 'Not Evaluated'?
This typically occurs if the device hasn't checked in or synced with Intune recently, the profile contains settings not supported by the device's OS version, or the device is only Azure AD registered instead of fully MDM enrolled.
Can a device receive Intune configuration profiles if it is only Azure AD Registered?
No. Azure AD registration only registers the device's identity with Azure for conditional access. To receive configuration profiles, applications, and policies, the device must be formally enrolled in Microsoft Intune Mobile Device Management (MDM).
How long does it take for a newly assigned Intune configuration profile to apply?
Newly assigned profiles typically apply within 15 to 30 minutes if the targeted device is online and active. However, depending on the platform and the device's standard synchronization schedule, it can take up to 8 hours for a profile to apply automatically.
Where can I find the Intune Management Extension logs on a Windows device for further troubleshooting?
On a Windows 10 or Windows 11 device, you can locate the Intune Management Extension logs in the directory C:\ProgramData\Microsoft\IntuneManagementExtension\Logs. These files are highly useful for diagnosing app deployments and policy failures.
