What is involved in setting up Windows Autopilot?

Key facts

• Autopilot turns a factory-fresh or reset PC into a managed, ready-to-use device over the internet.
• Classic Autopilot uses registered hardware hashes; Autopilot device preparation targets devices without pre-registration.
• Entra join is the recommended target; hybrid join through Autopilot adds complexity and is discouraged for new deployments.
• Keep the day-one app list short so setup finishes quickly; install the rest after sign-in.
• Resellers and OEMs can register devices at purchase so they ship straight to users.

Prerequisites

• Intune licensing for users, such as Microsoft 365 Business Premium or E3, and automatic MDM enrollment enabled in Entra ID.
• Entra ID settings that allow users or a defined group to join devices.
• Company branding in Entra ID so the sign-in screen looks familiar.
• Windows editions that support Autopilot, typically Pro or Enterprise.
• Network access to the required Microsoft endpoints, including from home networks.
• A decision on local admin rights, usually standard user with Windows LAPS for the local admin account.

Classic Autopilot or Autopilot device preparation

Microsoft is developing Autopilot device preparation as the newer experience. Classic profiles remain important where you need pre-provisioning, self-deploying devices or hybrid join. Many organizations use both for different device types.

Building the day-one experience

Decide what must be on the device before the user reaches the desktop, and what can arrive afterward. Required items typically include security policies, BitLocker, Defender settings, Wi-Fi and VPN profiles, Microsoft 365 Apps and the company's critical line-of-business app.

Everything else, such as optional tools and department apps, should install after sign-in or be offered in the Company Portal. Long blocking app lists are the most common reason Autopilot setup is slow or fails.

Rollout plan

• Build policies, apps and the Autopilot or device preparation profile in a pilot group.
• Test with each hardware model you buy, on home and office networks.
• Pilot with IT, then with a friendly department, and capture setup times and issues.
• Arrange device registration with your reseller or OEM so new purchases ship directly to users.
• For existing PCs, upload hardware hashes or target them by group, then reset them on a schedule.
• Write a one-page user guide and a help desk runbook for failed setups.

Common issues

• Win32 apps that need a reboot or user context during setup.
• Conflicting policies between Group Policy and Intune on hybrid devices.
• Devices still registered to a previous tenant, which blocks enrollment until deregistered.
• Hybrid join timeouts waiting for domain controller connectivity, a main reason to choose Entra join.

How Accred Consulting approaches it

Accred Consulting begins with discovery of your device models, purchase channel, apps, current join state and Intune setup. The proposal sets the Autopilot approach, the day-one app list, rollout waves, a fixed price and a timeline. Our US-based specialists configure enrollment, profiles or device preparation policies, apps and security settings, test on each hardware model, and run pilots and waves with check-ins. At handover you get documentation, a help desk runbook and reseller registration steps, with optional support for ongoing device changes.

Track record: 475+ client projects, 2,000+ migration workstreams and 210,000+ users migrated by a US-based team. Company facts · Case studies

Related questions