Autopilot & Enrollmentdecimal -2145910746
Fix Intune Error 0x80180026: MDM enrollment was blocked because another management agent is present: automatic MDM enrollment collides with the legacy Intune PC client.
Open the log below first. It is the quickest way to confirm which of the causes applies before you change anything.
Microsoft-Windows-DeviceManagement-Enterprise-Diagnostics-Provider%4Admin.evtx
Folder: C:\Windows\System32\winevt\Logs\
Also check: Microsoft-Windows-User Device Registration%4Admin.evtx
Root causes
- MDM automatic enrollment is turned on for the user and the legacy Intune PC software client (the old agent) is installed on the device.
- The device is still under another management authority that blocks MDM enrollment.
Step-by-step remediation
- On the device, check Programs and Features for the legacy Intune client. Uninstall it if it is present.
- Run dsregcmd /status and confirm the join state and tenant are what you expect.
- Review the DeviceManagement-Enterprise-Diagnostics-Provider Admin log for the enrollment event and error.
- Only if the old client cannot be removed, change Entra ID > Mobility (MDM and MAM) > Microsoft Intune > MDM user scope for the affected users, and put it back afterwards.
- Retry the Entra join or automatic enrollment.
For the full diagnosis around this error, read Company Portal enrolment stuck.
Tighten the rollout around it
Enrollment and compliance errors usually trace back to rollout design and device permissions. See how the endpoint privilege management tools compare, and plan the next ring with a tested runbook.
Compare Intune endpoint privilege management toolsRelated Error Codes in This Category
Other Autopilot & Enrollment errors with their own runbooks.
- 0x80180014The MDM service refused enrollment: Windows (MDM) is blocked by an enrollment restriction, or the reused Autopilot device record is blocked.
- 0x80180013The user has reached the Intune device limit (15 by default), so enrollment of another device is refused.
- 0x8018002BGroup Policy based automatic MDM enrollment failed, normally because the UPN is non-routable or the MDM user scope is None.
- 0x800705B4A timeout (ERROR_TIMEOUT). In Autopilot it is typically TPM 2.0 attestation failing during self-deploying mode, or the ESP device phase timing out.
- 0x801C03EATPM attestation failed, so the device could not get a device token and failed to join Microsoft Entra ID.