Intune Enrollment Error 80180014? Fix It on Autopilot Fast

By Ahmet Tolga KAYA 7 min read
Intune Enrollment Error 80180014? Fix It on Autopilot Fast

Intune enrollment error 80180014 usually shows up at the worst moment: a freshly reset laptop sits at the “Something went wrong” page during Autopilot, and the message says the feature is not supported. The device is not broken, and your tenant is not misconfigured beyond repair. Microsoft documents two specific causes, and each one has a short fix in the Intune admin center.

What Intune Enrollment Error 80180014 Means

According to Microsoft’s Windows Autopilot troubleshooting FAQ, error code 0x80180014 occurs in one of two scenarios. Either Intune changed the self-deployment and pre-provisioning experience so that a device record created by Intune must be cleared before the device can be reused, or Windows MDM enrollment is disabled in the tenant.

The first scenario behind Intune enrollment error 80180014 hits Autopilot self-deploying mode and Autopilot pre-provisioning when you reuse, reset or redeploy a device. The second one hits any Windows enrollment and also produces Intune enrollment error 80180014 for ordinary users when the Windows (MDM) platform is set to Block in an enrollment restriction. Microsoft notes that in both cases the ETW logs may also contain this line:

MDM Enroll: Server Returned Fault/Code/Subcode/Value=(DeviceNotSupported)
Fault/Reason/Text=(Enrollment blocked for AP device by SDM One Time Limit Check)
Intune enrollment error 80180014 on the Something went wrong screen (illustration)

The same page ties error 0x80180014 to those two causes only, so you do not need to touch licensing or hardware hashes first. That saves time, because the generic advice for Intune enrollment error 80180014 on the web often sends people through unrelated checks.

Intune Enrollment Error 80180014: How to Tell Which Cause You Have

Answer two questions before you change anything:

  • Was this exact device enrolled with Autopilot self-deploying or pre-provisioning before, and has it been wiped or reused? That points to the one-time device limit check behind Intune enrollment error 80180014, and you need to unblock the device.
  • Is it a brand-new device, or does enrollment fail on many devices at once? That points to a blocked Windows (MDM) platform in an enrollment restriction.
  • Does Event Viewer show Autopilot profile events? Open Application and Services Logs > Microsoft > Windows > ModernDeployment-Diagnostics-Provider > Autopilot. Event ID 807 means the device is not registered, and 815 means no profile is assigned. Those are different problems from 80180014.

You can also read what profile the device received. On the device, press Shift+F10 during OOBE to get a command prompt, or run this in PowerShell on a running machine:

Get-ItemProperty "HKLM:\SOFTWARE\Microsoft\Provisioning\Diagnostics\Autopilot"Code language: JavaScript (javascript)

Microsoft says CloudAssignedTenantDomain shows the tenant the device is registered with, and IsAutopilotDisabled set to 1 means the device is not registered or could not download its profile. If the values look right, the profile is fine and Intune enrollment error 80180014 comes from one of the two causes above.

Fix 1: Unblock the Autopilot Device in Intune

This is the fix for a reused, reset or redeployed device. In the Intune admin center, follow the path Microsoft documents:

  • Go to Devices > Windows.
  • Under Device onboarding, select Enrollment.
  • Under Windows Autopilot, select Devices.
  • Select the device that shows the error and choose Unblock device in the toolbar.
  • Redeploy the Autopilot deployment profile.

Microsoft adds that a success message may not appear after you select Unblock device, but the device is ready to be used again. Do not assume the click failed or that Intune enrollment error 80180014 is still unresolved. Restart the device, or use shutdown.exe /r /t 0 from the Shift+F10 prompt, so it requests a fresh profile, then start the enrollment again.

Intune enrollment error 80180014 fix steps: unblock the device, allow Windows MDM, redeploy

Resist the urge to delete the Microsoft Entra device object to “clean up”. Microsoft warns that the Entra device created on import is the anchor for Autopilot group membership and profile targeting, and deleting it can cause join errors. If it is already gone, delete the Autopilot record and import the device again so the object is recreated.

Fix 2: Allow Windows (MDM) in the Enrollment Restrictions

If Windows MDM enrollment is blocked, every user hits Intune enrollment error 80180014, not just one reused laptop. Check the restriction like this:

  • In the Intune admin center, open Devices > Windows > Enrollment.
  • Under Enrollment options, select Device platform restriction.
  • Under Device type restrictions, select All Users, then Properties.
  • Next to Platform settings, select Edit.
  • Find Windows (MDM) and make sure it is set to Allow. If it says Block, change it.
  • Select Review + save, then Save.

Repeat the check for every other restriction in the list that applies to the Windows platform. Microsoft points out that some restrictions are assigned only to certain groups, so a block may be valid for one group and the device may simply be a member of it. In that case, either move the user or change the setting for that restriction.

Two details from the enrollment restrictions overview save a lot of confusion. First, restrictions are only applied to user-driven enrollments. Autopilot self-deploying mode, pre-provisioning and co-managed enrollments are enforced against the default policy, so look at the default restriction first. Second, assignments use Entra groups and filters that can take up to 15 minutes to update, so wait before you retest.

If you block personally owned Windows devices, Autopilot enrollment is still treated as corporate. Many guides, including this one from Prajwal Desai, tell you to allow personally owned devices to fix this error. That works for the manual join case, but only do it if your organization really accepts personal devices.

Intune Enrollment Error 80180014 vs Similar Errors

Do not confuse Intune enrollment error 80180014 with 80180018, which has a different cause. Microsoft says 80180018 usually comes from missing licenses or a user hitting the device limit, and points to its Windows enrollment error guide for that. Also remember that Entra join has its own default limit of 50 devices per user, which can be configured in Microsoft Entra ID.

If the real symptom is a policy that never lands after a successful enrollment, that is a different troubleshooting path. Read more: Intune Policy Shows Succeeded, But the Windows Setting Isn’t Applied

Verify the Fix and Prevent a Repeat

After you unblock the device or allow Windows (MDM), redeploy the profile and run enrollment again. A successful run shows the device joined to Entra ID and managed by Intune. On the device you can confirm the join state:

dsregcmd /status | Select-String "AzureAdJoined|TenantName"Code language: JavaScript (javascript)
Intune enrollment error 80180014 resolved: Autopilot registry values and Entra join check (illustration)

Intune enrollment error 80180014 should be gone at this point. Then confirm the device appears in Devices > All devices in Intune. To avoid hitting Intune enrollment error 80180014 again, build the unblock step into your reuse process: whenever a self-deploying or pre-provisioned device is wiped for a new user, unblock it before you redeploy. Also keep a note of which restriction owns Windows MDM, so nobody flips it to Block during a tidy-up.

Read more: Upgrade Microsoft Entra Connect Best Way

Read more: Microsoft 365 Licenses: 5 Warning Signs on Disabled Accounts

What does Intune enrollment error 80180014 mean?

Microsoft documents two causes: a reused Autopilot self-deploying or pre-provisioned device that must be unblocked in Intune, or Windows MDM enrollment being blocked in an enrollment restriction.

How do I fix error 0x80180014 on a reused Autopilot device?

In the Intune admin center go to Devices > Windows > Enrollment > Windows Autopilot > Devices, select the device, choose Unblock device, and redeploy the Autopilot deployment profile.

Where do I allow Windows (MDM) enrollment in Intune?

Open Devices > Windows > Enrollment > Device platform restriction, select the restriction under Device type restrictions, edit Platform settings and set Windows (MDM) to Allow, then save.

Should I delete the Microsoft Entra device object?

No. Microsoft says the Entra object created on import anchors Autopilot group membership and profile targeting. If it was deleted, delete and reimport the device as an Autopilot device.

Is error 80180014 the same as 80180018?

No. Microsoft links 80180018 to common issues such as missing licenses or too many enrolled devices, while 80180014 is tied to the device block or a disabled Windows MDM platform.

References

Microsoft Learn: Windows Autopilot Troubleshooting FAQ

Microsoft Learn: Overview of enrollment restrictions in Microsoft Intune

Microsoft Learn: Troubleshooting Windows device enrollment errors in Intune

Prajwal Desai: Intune enrollment error 80180014

Ahmet Tolga KAYA

Systems Engineer and Technical Writer focused on Windows, Microsoft technologies, infrastructure, cybersecurity, automation, and platform reliability.