intune error 0x80180014: device already enrolled with another organization
Resolves Intune error 0x80180014, device already enrolled with another organization: removing the old enrollment before joining the new tenant. Use when enrollment fails with this code on a reused device. Not for first-time enrollments or license problems.
TL;DR
The device still carries an enrollment from a previous organization and Intune will not stack a second one. Remove the old work account and MDM enrollment, verify it is gone, then enroll into the new tenant.
The query
intune error 0x80180014: device already enrolled with another organizationUse this when
- enrollment fails with 0x80180014
- the device was previously used at another company or in a demo tenant
- reimaged devices still report the old enrollment
Not for
- 0x801C0003 licensing or authority errors
- brand-new devices failing enrollment
- MDM profile issues on macOS
Steps
- On the device, open Accounts, Access work or school, and disconnect the old work or school account. Expected output: the old organizational account is removed.
- Confirm no MDM enrollment remains in the management settings. Expected output: the device shows as not managed.
- In the old tenant, if you still have access, retire or delete the device record so it cannot reattach. Expected output: the device record is removed from the old Intune.
- Reboot the device to clear cached enrollment state. Expected output: a clean boot with no management profile.
- Enroll into the new tenant. Expected output: enrollment succeeds and the device appears under the new organization.
Applies to
Microsoft Intune, Windows 10/11, Entra ID tenants. Same pattern applies to re-enrolling Android and iOS devices that changed organizations.
Variant phrasings
No access to the old tenant
Local removal still works; the old tenant record goes stale and the new enrollment succeeds.
Error persists after disconnecting the account
A factory reset clears stubborn enrollment state on most platforms.
Why it happens
MDM enrollment is one-to-one: a device trusts exactly one management authority. Leftover enrollment artifacts from the prior org block the new one until removed.
Edge cases
- Autopilot-registered devices may auto-enroll into the old tenant on reset; update the Autopilot registration.
- Demo or loaner devices should be wiped between users to avoid this entirely.
- On shared devices, use a dedicated enrollment account rather than personal accounts.
Provenance
Resolved from the public thread: https://vectle.com/posts/pst_CgSxwjNV5UVixBMT9zLBOA