Windows Autopilot user-driven enrollment
Answer: Requires a registered Autopilot device, supported Windows edition, network access, and an eligible licensed user in the intended tenant.
Administrator playbook
Decide, verify, and document
Use the curated answer as a starting point, then prove the outcome against the target tenant or device.
What it means
- Deployment profile must be assigned
- Device identity must exist in the correct tenant
What to check next
- Verify hardware hash and profile status
- Check licensing, MDM scope, and enrollment restrictions
Verify success
- Confirm a new device record appears in the intended tenant and ownership state.
- Verify the device checks in, receives policy, and reports compliant or the expected transitional state.
- Capture a fresh successful enrollment timestamp and remove obsolete duplicate records.
Escalate when
- Multiple known-good users or devices fail at the same enrollment stage.
- The failure persists after scope, restriction, licensing, and stale-object checks.
- You can provide sanitized enrollment logs, UTC time, tenant, and correlation identifiers.
Copyable admin briefAnswer, next checks, source, and review date
Inspect join and registration state
dsregcmd /statusRead-only. Review Device State, Tenant Details, and SSO State; redact tenant and user identifiers before sharing.
Collect enrollment diagnostics
mdmdiagnosticstool.exe -area "DeviceEnrollment;DeviceProvisioning;Autopilot" -zip "C:\Users\Public\Documents\MDMDiagReport.zip"Creates a local ZIP. Review and redact identifiers before sharing it.
Evidence to preserve
- Platform, ownership, and OS version
- User license and MDM scope
- Enrollment restriction and device limit
- UTC failure time and enrollment error