Error 80180014 (also shown as 0x80180014) means Intune refused to enroll the device. Windows reached the enrollment service, but a policy or an existing record told it no. The usual triggers are users adding personal laptops and Autopilot devices being re-provisioned. Depending on how the enrollment was started, the message looks like one of these:
"Something went wrong. Your organization does not support this version of Windows. (0x80180014)"
"Your organization doesn't allow you to enroll this device. (Error 80180014)"

Applies to: Windows 10 / 11 enrollment in Microsoft Intune: Settings → Access work or school, Entra join during setup (OOBE), and Windows Autopilot.
The three causes, and how to tell which one you have
| Situation | Most likely cause |
|---|---|
| User adds a personal device through Access work or school, or joins it during setup | Personally owned Windows devices are blocked in enrollment restrictions |
| Autopilot pre-provisioning or re-deployment of a device that was enrolled before | An old Intune device record for that hardware still exists |
| Enrollment from Windows Home, or an OS version outside your allowed range | Unsupported edition or version in platform restrictions |
Cause 1: Personal devices are blocked (most common)
When an admin blocks personally owned Windows devices, Intune only accepts enrollments it can recognise as corporate. Corporate methods include:
- Windows Autopilot
- Group Policy auto-enrollment for hybrid-joined devices
- Co-management with Configuration Manager
- Bulk enrollment with a provisioning package
- A device enrollment manager (DEM) account
- Devices matching your corporate device identifiers
A user enrolling their own laptop through Settings → Accounts → Access work or school doesn't match any of these, so they get 80180014.
Option A: Make the device corporate (recommended)
Keep personal devices blocked and register the device properly:
- Autopilot: upload the hardware hash in Intune admin center → Devices → Enrollment → Windows Autopilot → Devices, or ask the reseller to register it.
- Corporate device identifiers: add the manufacturer, model and serial number under Devices → Enrollment → Corporate device identifiers.
Option B: Allow personal devices
If your organisation does want personal Windows devices in Intune:
- Open the Intune admin center (intune.microsoft.com).
- Go to Devices → Enrollment → Device platform restriction → Windows restrictions.
- Open the policy that applies to the user (the All Users default or a higher-priority custom policy) → Properties → Platform settings → Edit.
- Set Personally owned to Allow for Windows (MDM), then Review + save.

Custom restriction policies are applied by priority, so check that no higher-priority policy assigned to the user still blocks personal devices.
Cause 2: An old Intune record blocks Autopilot re-enrollment
In Autopilot, 80180014 typically shows up during pre-provisioning (technician flow) or a re-deployment, when the device was enrolled before. The old Intune device object still exists and blocks the new enrollment.
Fix:
- In the Intune admin center, search Devices → All devices for the serial number.
- Delete the old device record. Don't delete the Autopilot registration under Windows Autopilot → Devices, which is a separate record that you need to keep.
- Wait a few minutes, then restart the Autopilot deployment.
If you also see a stale object in Entra ID → Devices for the same hardware, delete that too. But don't delete the Entra object Autopilot uses: it's the one showing the Autopilot icon and a ZTDID in its device IDs.
Cause 3: Unsupported Windows edition or version
- Windows Home can't be fully enrolled in Intune. Upgrade to Pro, Enterprise or Education. This is the case behind searches like "this feature is not supported 80180014".
- In the same Windows restrictions policy, check the minimum and maximum OS version. A device outside that range is blocked.
For end users
If you're not the Intune admin, you can't fix this yourself. Send your IT team:
- the full error message and code,
- whether the device is personal or company-owned,
- the device serial number (run
wmic bios get serialnumber, or check Settings → System → About).
That gives them what they need to either register the device as corporate or allow it.
Related enrollment errors
| Code | Meaning |
|---|---|
80180002 |
Authentication problem during enrollment. Usually licensing or the MDM user scope in Entra ID |
80180003 |
User isn't authorised to enroll (MDM user scope, or the user lacks an Intune licence) |
801c0003 |
User has reached the Entra ID device limit |
Summary
- 80180014 = Intune actively refused the enrollment.
- For personal devices: allow personally owned Windows enrollments, or (better) register the device as corporate through Autopilot or corporate identifiers.
- For Autopilot re-deployments: delete the stale Intune device record, not the Autopilot registration.
- For Windows Home or out-of-range OS versions: upgrade the edition, or adjust the version range in the restriction.
Related: Intune multi-admin approval to prevent mass device wipes · Find stale devices in Microsoft Intune · Create a custom role in Intune · Microsoft's Autopilot known issues