Essential Step by Step Preparation Guide for Autopilot Device V2

Here’s a clear step‑by‑step guide for Windows Autopilot Device Preparation (Autopilot v2): it simplifies provisioning by using the device serial number instead of hardware hashes, making deployment faster and easier.

🚀 Step‑by‑Step Autopilot v2 Device Preparation Guide

1. Understand Autopilot v2

• Autopilot v2 (Device Preparation) is the next evolution of Windows Autopilot.

• It removes the need to import hardware hashes; instead, it uses the device serial number to identify corporate devices.

• Devices must not already be registered with the Autopilot service; deregister them if needed.

  
  

2. Pre‑requisites

• Microsoft Intune tenant with proper licensing (Microsoft 365 E3/E5 or equivalent).

• Devices running Windows 11, ideally latest builds.

• Admin access to Intune portal.

• Ensure devices are not pre‑registered with Autopilot.

  
  

3. Create Device Preparation Policy

• In Intune portal → Devices → Windows → Windows enrollment → Device preparation (preview).

• Click + Create policy.

• Define:

  • Name & description.

  • Assigned group (Azure AD group containing target devices).

  • Deployment settings (user-driven or pre-provisioned).

  • Out-of-box experience (OOBE) customizations (language, region, privacy settings).

    
    

4. Configure Enrollment Settings

• Choose user-driven (end-user signs in during setup) or pre-provisioned (IT sets up before handoff).

• Configure Azure AD join type (Hybrid or Azure AD only).

• Assign Intune enrollment profile.

  
  

5. Assign Apps & Configurations

• Attach required Win32 apps, MS Store apps, or line-of-business apps.

• Apply configuration profiles (Wi-Fi, VPN, compliance policies).

• Add security baselines (Defender, BitLocker, etc.).

  
  

6. Deploy Policy to Devices

• Devices boot into OOBE.

• Serial number is matched against Intune policy.

• Device preparation applies automatically:

  • Enrollment into Intune.

  • Policy, app, and configuration deployment.

  • User sign-in completes setup.

    
    

7. Monitor Deployment

• Use Intune Enrollment Status Page (ESP) to track progress.

• Check logs in MDM Diagnostic Information if troubleshooting is needed.

• Intune portal shows device compliance and app installation status.

⚠️ Key Differences vs Classic Autopilot

Feature	Autopilot v1	Autopilot v2 (Device Preparation)
Identification	Hardware hash	Serial number
Registration	Required	Not required
Setup speed	Slower	Faster
Troubleshooting	Limited	Improved visibility

🔑 Risks & Considerations

• Device deregistration: If already registered in Autopilot v1, you must deregister before using v2.

• Preview status: Autopilot v2 is still evolving; expect changes in features and UI.

• Hybrid join complexity: Hybrid Azure AD join may introduce extra networking dependencies.