2.2.5. Troubleshooting Enrollment Failures
💡 First Principle: An enrollment is a chain of gates — license, MDM authority, scope, restriction, limit, platform prerequisites — and the error tells you which gate closed. Work from the tenant inward: confirm the tenant is ready, then that the user is entitled, then that the device is allowed, and only then suspect the device itself.
Microsoft's first step is to confirm Intune is set up at all: licenses, the MDM authority, and platform prerequisites such as the APNs certificate or the Managed Google Play binding. Then the Enrollment failures report under Devices shows per-user failures; a device blocked by a restriction appears with the reason Enrollment restriction not met.
The messages and codes cluster into a few root causes:
| Symptom or code | Root cause | Fix |
|---|---|---|
| "DeviceCapReached" or "Company Portal Temporarily Unavailable" | User exceeded the Intune device limit restriction (the second message can also mean an outdated or corrupt Company Portal) | Remove stale devices or raise the limit |
| "MDM authority not defined" / "Looks like your IT admin hasn't set an MDM authority" | Authority not set, or the user's credentials didn't sync to Entra ID | Set the MDM authority; check sync |
| "Your IT admin hasn't given you access to use this app" / "This account is not allowed on this phone" | Missing or wrong license | Assign an Intune license |
| "MDM Terms of Use endpoint is not correctly configured" | License coexistence issue, or a blank or wrong terms URL | Restore the default MDM URLs |
| 0x80180014 "Your organization does not support this version of Windows" | Windows blocked by a device platform restriction | Adjust the restriction |
| 8018000a "The device is already enrolled" | Another user already enrolled or joined it | Remove that work account |
| 0x8018002b (Event 76, GPO enrollment) | UPN with an unverified or non-routable suffix such as .local, or MDM user scope set to None | Fix the UPN suffix or the scope |
| 0x80180022 (Autopilot) | Device runs Windows Home | Upgrade to Pro or higher |
| 0x801C03EA | TPM supports 2.0 but hasn't been upgraded to it | Upgrade the TPM to 2.0 |
| 0x800705b4 (self-deploying) | No physical TPM 2.0 | Use supported hardware |
| Bulk enrollment package fails | Package account isn't allowed to join | Set Users may join devices to All or include it |
Apple and Android have their own signatures. If the default "All Users" device type restriction blocks iOS, automated device enrollment fails with "Invalid Profile" — block only personally owned iOS devices instead. An ADE device using Company Portal authentication that falls outside an OS version restriction shows "Couldn't map device record with a user". "Profile installation failed" on iOS or Android points to the license, another MDM, an existing management profile, or a default browser without cookies (Safari on iOS, Chrome on Android). For account-driven user enrollment, "Your Apple ID does not support the expected services" means the .well-known discovery file is wrong. After an MDM authority change, iOS enrollments and check-ins fail until the APNs certificate is uploaded again.
Easy-to-forget causes include special characters in the company name, a device clock more than 12 hours off for its time zone, and a Conditional Access policy applied to a device enrollment manager account's sign-in, which stops that account enrolling.
Two judgement calls round this out. First, decide which limit fired: DeviceCapReached means the Intune device limit restriction, but an Entra join that fails because the user already has 50 device identities is the Entra maximum — a different setting in a different portal. Second, remember the timing: group and filter assignments for restrictions typically process within 15 minutes, so a user added to an "allowed" group a moment ago may still be blocked; wait several minutes before retrying.
⚠️ Exam Trap: Error 0x80180014 isn't a license problem, even though the wording ("your organization does not support this version of Windows") sounds like one. It means Windows enrollment is blocked by a device platform restriction. A license problem shows up as "This account is not allowed on this phone" or "Your IT admin hasn't given you access to use this app".
Reflection Question: Three users report Windows enrollment failures on the same morning: one sees 0x80180014, one sees DeviceCapReached in the Company Portal, and one sees Event 76 with 0x8018002b on a hybrid joined PC. Which setting would you check for each, and which of the three fixes lives outside the Intune admin center?