Autopilot Profiles

Windows Autopilot deployment profiles configure the out-of-box experience (OOBE) for new Windows devices. Assign profiles to devices to automate enrollment and setup.

Deployment Scenarios

User-Driven

End user powers on the device and completes setup. Azure AD join and Intune enrollment happen automatically. Best for standard user devices.

Self-Deploying

Device provisions itself without user interaction. Requires TPM 2.0. Best for shared devices or kiosks.

Pre-Provisioning (White Glove)

IT pre-provisions the device before handing to the user. Best for complex configurations.

Autopilot Reset

Reset an existing device to business-ready state without reimaging.

Profile Settings

OOBE Customization

Device Settings

• Azure AD Join Type — Azure AD joined or Hybrid Azure AD joined
• Device Name Template — Auto-name devices (e.g., CONTOSO-%SERIAL%)
• Language/Region — Pre-configure or let user choose

Enrollment Status Page

• Show app and profile installation progress
• Block device use until required apps are installed
• Configurable timeout and error handling
• Allow users to collect logs on error

Device Registration

• Hardware Hash — Upload CSV with device hardware hashes
• OEM Registration — Manufacturer registers at purchase
• Partner Registration — MSP registers on behalf of customer

Group Tags

Use group tags to organize Autopilot devices and auto-assign profiles. Create dynamic Azure AD groups based on tags.

Troubleshooting

• Profile not applying — Verify device registered and in assigned group
• ESP timeout — Increase timeout or review required apps
• Hybrid join failure — Check Intune Connector and AD connectivity

API Reference

• GET /api/devices/autopilot/profiles — List profiles
• POST /api/devices/autopilot/profiles — Create profile
• GET /api/devices/autopilot/devices — List registered devices
• POST /api/devices/autopilot/devices/register — Register device