'%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 Troubleshoot Intune Device Registration Issues in Microsoft 365
Question details
A Microsoft 365 administrator needs to resolve an issue where devices appear in Entra ID but fail to register in Intune, causing compliance errors.
- Product
- Microsoft 365 (Intune and Entra ID)
- Device & OS
- not provided
- Scenario
- Managing cross-domain device registration and compliance synchronization for corporate users.
- Observed behavior
- Entra ID successfully displays the devices, but Intune either shows no registered devices or returns an error when attempting to retrieve device information.
Verify that your Microsoft 365 subscription includes the necessary Intune licenses and that these licenses are actively assigned to the affected users.
Verify Intune Licensing and Assignment
Ensure users have the correct Intune licenses, as missing licenses prevent successful device registration and synchronization.
One of the most common reasons a device appears in Entra ID but not in Intune is a missing or unassigned license. Without a valid Intune license, the device cannot complete the Mobile Device Management (MDM) enrollment process.
Log in to the Microsoft 365 admin center using your administrator credentials.
Go to Users > Active users in the left-hand navigation pane and locate the affected user.
Select the user, click on the 'Licenses and apps' tab, and verify that a Microsoft Intune license is checked and applied.
Investigate Device Registration and MDM Scope Settings
Check directory synchronization, compliance policies, and MDM scope to ensure devices are allowed to communicate with Intune.
Submit a Support Request via Microsoft 365 Admin Center
If local troubleshooting fails, escalate the issue to Microsoft Support with detailed logs and policy configurations.
Equip Your Teams with WPS Office
While resolving Intune device registration and endpoint compliance requires Microsoft 365 Admin tools, you can still deploy a lightweight, high-performance office suite for your organization. WPS Office provides exceptional document handling and seamless compatibility without the heavy deployment overhead.
Frequently Asked Questions
Why are devices showing in Entra ID but not in Intune?
This typically occurs if the MDM user scope is misconfigured in Entra ID, the user lacks a valid Intune license, or there are synchronization delays preventing the MDM enrollment phase from completing.
How do I check if my Microsoft 365 users have the correct Intune license?
Navigate to the Microsoft 365 admin center, select Users > Active users, choose the affected user, and verify under the 'Licenses and apps' tab that an Intune or Enterprise Mobility + Security license is applied.
What information should I gather before opening a Microsoft Support request for Intune?
You should collect the specific Intune error codes, affected device states (registered vs. joined), compliance policy details, and device registration logs to help the support team diagnose the issue faster.
