sodcalculator

10 Tech How-To

Intune Enrollment Errors on Entra Devices: Fix

Guide 10-54167 · Updated · Step by step

This guide walks you through troubleshooting Intune enrollment errors that occur on Microsoft Entra (formerly Azure AD) registered devices. It covers the most common failure points—from licensing and network issues to certificate and policy problems—and gives you a clear, ordered path to identify and resolve them. You’ll need access to the Microsoft Intune admin center and, in most cases, local administrator rights on the affected device.

What You’ll Need

  • Access to the Microsoft Intune admin center (endpoint.microsoft.com) with an account that has the Intune Administrator or Global Administrator role.
  • Local administrator credentials on the device that is failing to enroll.
  • The device’s serial number or a way to identify it in Entra ID (if it already appears there).
  • Internet connectivity on the affected device, and the ability to reach Microsoft’s service endpoints (usually not blocked, but verify if you have a strict firewall).
  • A valid Intune license assigned to the user or device (Microsoft 365 E3/E5, or standalone Intune).

Step-by-Step

  1. Confirm the device is actually Entra registered. Go to Settings > Accounts > Access work or school on the device. If it shows a connected account, click it and select Info to see the registration status. If it says “Not registered,” the Intune error is a symptom of a failed Entra join—fix that first by signing out and back in with the work account.
  2. Check the user’s license. In the Intune admin center, go to Users > All users, select the affected user, and review their Licenses. They need an Intune license (standalone or as part of a suite). Without one, enrollment will fail with error 0x80072EE7 or a generic “device not allowed” message. Assign the license if missing, then wait 15–30 minutes before retrying.
  3. Verify the enrollment restrictions. In Intune, go to Devices > Enrollment > Enrollment device platform restrictions. Check both the Windows and the default restrictions. If the device platform is blocked, or if the user is not in the allowed group, enrollment will be rejected. Adjust the restrictions to allow the device, or add the user to the correct group.
  4. Check the enrollment status page (ESP) settings. If the device gets partway through enrollment and then fails, the ESP might be blocking it. Go to Devices > Enrollment > Windows enrollment > Enrollment status page. If a profile is assigned, temporarily set it to “Not configured” or remove the device from its assigned group to test if the ESP is the culprit.
  5. Look at the device’s MDM authority. In Intune, go to Tenant administration > MDM authority. It should show Microsoft Intune. If it shows “None” or “Microsoft Office 365,” enrollment will fail. Change it to Intune if needed (this only affects new enrollments).
  6. Review the device’s certificate state. On the device, open Certlm.msc (Local Machine certificates) and look under Personal > Certificates. There should be a certificate issued by “MS-Organization-Access” or similar. If it’s missing or expired, delete the device from Entra ID and Intune, then re-register it.
  7. Use the built-in diagnostics. On the device, go to Settings > Accounts > Access work or school, click the connected account, and select Diagnose. This runs a check for common issues (network, proxy, certificates) and gives you a specific error code to search for.
  8. Force a re-enrollment. If nothing else works, remove the device from Intune and Entra ID (in the admin centers), then on the device go to Settings > Accounts > Access work or school, disconnect the account, restart the device, and sign back in with the work account to trigger a fresh enrollment attempt.

Common Mistakes

  • Mixing up Entra registered and Entra joined. Intune enrollment works differently for “registered” (BYOD) vs “joined” (corporate) devices. If you’re trying to enroll a personal device as if it were corporate, you’ll hit policy conflicts. Verify which type you’re actually dealing with.
  • Ignoring the time sync. If the device’s clock is off by more than a few minutes, certificate validation fails. Check Settings > Time & Language > Date & time and ensure automatic time is on.
  • Not checking the proxy. If the device uses a proxy or VPN, it may block the enrollment endpoints. Temporarily disable the proxy or add the Microsoft endpoints to the allowlist to test.
  • Deleting the device from the wrong place. If you remove a device from Entra ID but not from Intune (or vice versa), you’ll get a “device already enrolled” error. Always remove from both portals.

Tips

  • Use the Enrollment Diagnostic tool. Microsoft provides a downloadable tool (from the Intune admin center under Devices > Enrollment) that collects logs and gives a detailed analysis. Run it before contacting support—it saves time.
  • Check the Event Viewer. On the device, look in Applications and Services Logs > Microsoft > Windows > DeviceManagement-Enterprise-Diagnostics-Provider > Admin. The event IDs here (e.g., 100, 300, 400) often contain the exact error string.
  • Test with a different user. If a specific user’s enrollment fails but others succeed, the problem is likely their account (license, group membership, or MFA settings). Create a test user with the same licenses to isolate the issue.
  • Keep the device fully updated. Older Windows builds have known enrollment bugs. Run Windows Update and retry—this resolves a surprising number of cases.

Troubleshooting

If the steps above don’t resolve the issue, work through these additional checks in order:

  • Error 0x801c0003 (device already enrolled): This means a stale record exists. Go to Entra ID > Devices > All devices, find the device, and delete it. Then delete it from Intune > Devices > All devices as well. Wait 10 minutes and retry enrollment.
  • Error 0x80072ee7 (cannot reach server): This is almost always a network/DNS issue. On the device, open a command prompt and run ping login.microsoftonline.com. If it fails, check your DNS settings and firewall rules. Try using a different network (e.g., mobile hotspot) to confirm it’s network-related.
  • Error 0x801c001a (user not licensed): The license is missing or not yet propagated. Assign the Intune license in the Microsoft 365 admin center and wait up to an hour. Also verify the user isn’t in a group that blocks enrollment.
  • Error 0x87d1fde8 (policy conflict): A configuration profile is conflicting with enrollment. Temporarily assign the device to a test group with no policies, and see if enrollment completes. If it does, narrow down which policy is the issue by adding them back one at a time.
  • If the device shows as “Pending” in Intune: This usually means the device registered with Entra but the Intune agent hasn’t checked in. Force a check-in by going to Settings > Accounts > Access work or school, clicking the account, and selecting Sync. If it stays pending for more than 24 hours, remove and re-enroll.
  • If all else fails: Collect the enrollment logs (using the diagnostic tool or the Event Viewer), note the exact error code, and open a support ticket with Microsoft. Provide the logs and the steps you’ve already tried—this speeds up the resolution significantly.

Frequently Asked Questions

What’s the difference between Entra registered and Entra joined for Intune?

Entra registered devices are typically personal (BYOD) and get limited management. Entra joined devices are corporate-owned and get full Intune management. Enrollment errors often happen when the wrong type is expected.

Why does my device say “Already enrolled” when it’s not showing in Intune?

This usually means there’s a stale record in Entra ID. Delete the device from both Entra ID and Intune, then retry. Also check if the device is registered under a different user’s account.

Can I enroll a device without a user license?

Yes, if you use device-based enrollment (like Autopilot or a device enrollment manager account). For standard user-driven enrollment, a user license is required.

How long does it take for a license to work after assigning it?

Usually 15–30 minutes, but it can take up to an hour in some cases. Wait at least that long before retrying enrollment.

Do I need to reset the device to fix enrollment errors?

No, in most cases you don’t. Try the diagnostic tool, remove the stale records, and re-register. A reset is only a last resort if the device’s certificate store is corrupted.

Can a VPN or proxy cause enrollment to fail?

Yes, if they block Microsoft’s endpoints. Temporarily disable them to test. If enrollment succeeds without them, add the Microsoft URLs to your allowlist.

Related

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →