Joined Devices Not Showing Up in Intune [Fix]
If you’re managing devices in a modern workplace, there’s a good chance you rely on Microsoft Intune to keep everything organized, secure, and compliant. But one of the most frustrating issues you can run into is when a joined device simply doesn’t show up in Intune. You’ve enrolled it, everything seems fine locally, yet the device never appears in the admin portal.
This problem can slow down deployments, break compliance policies, and make troubleshooting harder than it should be. This issue is usually tied to a handful of common causes, such as Azure AD join problems, enrollment failures, sync issues, or licensing gaps.
In this guide, I’ll walk you through exactly how to fix the problem step by step and also explain how to properly enroll your device in Microsoft’s InTune!
Joined Devices (Computer) Not Showing Up in Intune [Fix]
If a joined device is not showing up in Intune, verify that the device is properly Azure AD joined or hybrid joined, confirm the user has a valid Intune license, ensure automatic enrollment is enabled, check the MDM authority settings, and manually sync the device. Also, review logs and confirm network connectivity to Microsoft endpoints.
Step 1: Verify the Device is Properly Joined to Azure AD
The first thing you want to confirm is whether the device is actually connected to Microsoft Entra ID, formerly known as Azure Active Directory.
On the affected computer, open Settings, go to Accounts, and then select Access work or school. Here, you should see the account connected with a status indicating that the device is either Azure AD joined or Hybrid Azure AD joined.
If the device is not joined correctly, it will never appear in Intune. A local account or a simple work account connection is not enough. The device must be fully joined.
To double-check, open Command Prompt and run the command dsregcmd slash status. Look for AzureAdJoined set to Yes. If it says No, the device isn’t properly joined, and that’s your root problem.
If needed, disconnect the account and rejoin the device using proper organizational credentials.
Step 2: Confirm Automatic MDM Enrollment is Enabled
Even if the device is joined to Azure AD, it still needs to be enrolled in Intune through MDM enrollment.
Go to the Microsoft Intune admin center and check the enrollment settings. Make sure that automatic enrollment is enabled for your users or groups. This setting is critical because it tells Azure AD to automatically push devices into Intune after they join.
If automatic enrollment is not enabled, the device will join Azure AD successfully but never show up in Intune.
Also, confirm that the MDM user scope is set correctly. If it is set to None or limited to a group that doesn’t include your user, enrollment won’t happen.
After adjusting the settings, have the user sign out and sign back in to trigger enrollment again.
Step 3: Check Intune Licensing for the User
This one gets overlooked more often than you’d expect. If the user doesn’t have a valid Intune license, the device will not appear in the portal.
Go to the Microsoft 365 admin center and verify that the user is assigned a license that includes Intune, such as Microsoft 365 Business Premium or Enterprise Mobility plus Security.
Without a license, enrollment silently fails in most cases, which makes it tricky to spot.
Once the license is assigned, ask the user to restart the device and sign in again. This helps trigger the enrollment process properly.
Step 4: Force a Manual Sync from the Device
Sometimes the device is properly configured, but it simply hasn’t synced yet.
On the Windows device, go to Settings, then Accounts, then Access work or school. Select the connected account, click Info, and scroll down to find the Sync button.
Click Sync and wait a few minutes. This forces the device to communicate with Intune and update its status.
You can also run a sync using PowerShell or through the Company Portal app if it’s installed.
If the device appears after a manual sync, the issue was likely just a delay in communication rather than a configuration problem.
Step 5: Verify MDM Authority is Set to Intune
Your tenant must have the correct MDM authority configured. If this isn’t set to Intune, device enrollment won’t work properly.
In the Intune admin center, check that the MDM authority is set to Microsoft Intune. If it’s not configured or is pointing somewhere else, devices won’t show up even if everything else looks correct.
This is typically a one-time setup, but it’s worth verifying if you’re troubleshooting enrollment issues.
Step 6: Check Device Enrollment Restrictions
Intune allows administrators to define device enrollment restrictions. These can block certain devices from enrolling based on platform, ownership type, or OS version.
If your device falls into a restricted category, it won’t appear in Intune.
Review the enrollment restriction policies and make sure the device type is allowed. For example, confirm that Windows devices are permitted and not blocked by a custom policy.
Adjust the policy if necessary and retry enrollment.
Step 7: Review Event Logs and Diagnostic Data
When things aren’t working as expected, logs can tell you exactly what’s going wrong.
On the device, open Event Viewer and navigate to Applications and Services Logs, then Microsoft, then Windows, then DeviceManagement Enterprise Diagnostics Provider.
Look for errors related to MDM enrollment or device registration.
These logs often reveal issues like authentication failures, connectivity problems, or policy conflicts.
You can also export a diagnostic report using the Windows settings under Access work or school. This report can help you pinpoint the issue faster.
Step 8: Ensure Network Connectivity to Microsoft Services
The device must be able to communicate with Microsoft services for enrollment and sync to work.
Check that there are no firewall rules or proxy settings blocking access to Intune or Azure endpoints.
Corporate networks sometimes restrict traffic in ways that break enrollment without obvious errors.
If possible, test enrollment on a different network, such as a mobile hotspot. If it works there, your issue is likely network-related.
Step 9: Re-enroll the Device in Intune
If nothing else works, a clean re-enrollment can often fix the issue.
Start by disconnecting the device from Access work or school. Then restart the device and join it again using the correct account.
Make sure automatic enrollment is enabled before you do this, so the process completes properly.
This step resets the entire connection between the device and Intune, which can resolve hidden configuration issues.
How to Enroll a Device in Intune?
Here is a process to enroll your device in Microsoft’s InTune!
Step 1: Open Work or School Account Settings
On the Windows computer, open Settings, go to Accounts, and click Access work or school. This is where you connect your device to your organization.
Step 2: Connect to Your Organization
Click Connect and enter your work or school email account. Follow the prompts to sign in.
During this process, the device will join Microsoft Entra ID and prepare for enrollment.
Step 3: Allow Device Management Enrollment
After signing in, you will be asked to allow your organization to manage the device. Accept this prompt.
This step is critical because it enables MDM enrollment into Intune. Without accepting, the device will not appear in Intune.
Step 4: Complete Setup and Sign In
Finish the setup process and sign in with your work account. The device will now complete the enrollment process in the background.
This typically takes a few minutes.
Step 5: Verify Enrollment in Intune
Go back to Access work or school, select your account, and click Info. You should see management details and sync options.
You can also log into the Intune admin center and confirm that the device appears under managed devices.
Faqs
Why is my device Azure AD joined but not showing in Intune?
This usually happens when automatic MDM enrollment is not enabled, or the user does not have an Intune license assigned.
How long does it take for a device to appear in Intune?
In most cases, it should appear within a few minutes after enrollment. However, delays can happen if the device hasn’t synced yet.
Can a device be in Azure AD but not in Intune?
Yes, a device can be joined to Azure AD without being enrolled in Intune if MDM enrollment is not configured.
Does restarting the device help with Intune sync issues?
Yes, restarting can trigger enrollment and sync processes, especially after making configuration changes.
What command checks Azure AD join status?
You can use dsregcmd/status in Command Prompt to verify whether the device is properly joined.