Troubleshooting Windows Autopilot Enrollment Error 801C03ED

Windows Autopilot device enrollment failing with error code 801C03ED (sometimes written 0x801C03ED)? It shows up during the out-of-box experience (OOBE) or right after a user signs in, with a message like “Something went wrong, confirm you are using the correct sign-in information and that your organization uses this feature.” Here are the two most common causes and how to fix each one.

Fix 1: Allow users to join devices to Microsoft Entra ID

This is the most common cause, and it hits specifically in user-driven Microsoft Entra join and pre-provisioned Microsoft Entra join Autopilot scenarios (it doesn’t apply to hybrid Entra join or self-deployment mode, since those don’t need a signed-in user). If the “Users may join devices to Microsoft Entra” setting is set to None, the join silently fails right after sign-in with exactly this error.

To check and fix it:

• Open the Microsoft Entra admin center
• Go to Identity > Devices > Device settings
• Under “Users may join devices to Microsoft Entra”, make sure it’s set to All, or to a group that includes the users provisioning devices

Fix 2: Reactivate or re-import the device object

If the device’s object in Microsoft Entra ID was deactivated or deleted, enrollment fails the same way - that object is Autopilot’s anchor for group membership and targeting.

If it’s just deactivated, search for the device by serial number and re-enable it:

• In the Intune admin center: Devices > Enroll devices > Devices
• Search and select the device (by serial number)
• Open the Microsoft Entra ID device
• Click “Enable”

If the object was deleted (not just deactivated), re-import the device’s hardware hash - deleting and re-importing it recreates the associated object in Microsoft Entra ID.

Avoid deleting the device object as a first troubleshooting step: it’s easy to do by accident and it’s what causes this error in the first place.

Still stuck? Check the Autopilot diagnostics logs

If neither fix above resolves it, check Event Viewer for the specific event behind the failure:

• Application and Services Logs >
• Microsoft >
• Windows >
• ModernDeployment-Diagnostics-Provider >
• Autopilot

Also worth checking: if you see “Something went wrong and Can’t connect to the URL of your organization’s MDM terms of use. Try again” during OOBE, that’s a separate, licensing-related error - not 801C03ED.

Also verify the device actually has a valid Autopilot profile assigned before digging further; profile assignment can lag or fail to apply depending on your Windows client release.