Introducing Windows Autopilot RRS feed

  • General discussion

  • Many of us may not know what windows autopilot is and may feel that this is a very new technology. In fact, it was first released in 2017 with the Windows 10 Fall Creator update and is constantly improving. Although there are few cases about autopilot in our TechNet forum, we can still learn more about the windows autopilot function.

    From the Microsoft docs Overview of Windows Autopilot

    As we have known that Windows Autopilot is a kind of technology which can be used to pre-configure new devices, get them ready for productive use, reset and recover devices.

    It can simplify the out-of-box experience (OOBE) for new desktop users in an organization. All users in the enterprise can start by pressing the power button of the new Windows 10 device, no need to make cumbersome settings.

    Below, I will show how to deploy windows autopilot.

    Note: Devices need to meet these requirements:

    • Windows 10, version 1703 or later.
    • New devices that have not been through Windows out-of-box experience.


    Create a Dynamic Device Group that all devices registered with Autopilot will be added to 

    1. In Intune in the Azure portal, choose Groups > New group.

    1. In the Group blade:

    For Group type, choose Security.

    For Group name, type Autopilot Device

    For Group description, type All Windows 10 Autopilot Devices.

    For Membership type, choose either Assigned or Dynamic Device.

    If you chose Assigned for Membership type in the previous step, then in the Group blade, choose Members and add Autopilot devices to the group. Autopilot devices that aren't yet enrolled are devices where the name equals the serial number of the device.

    If you chose Dynamic Devices for Membership type above, then in the Group blade, choose Dynamic device members and type the following code in the Advanced rule box.

    (device.devicePhysicalIDs -any _ -contains "[ZTDId]")

        (This code is to create a group that includes all of your Autopilot devices)

    After adding the Advanced rule code, choose Save.

    1. Choose Create.

    We will see Group “Autopilot Device” has been created.

    Create and assign a Windows Autopilot deployment profile

    1. In Intune in the Azure portal, choose Device enrollment > Windows enrollment > Deployment Profiles > Create Profile.

    1. On the Basics page, type a Name and optional Description.

    1. On the Out-of-box experience (OOBE) page, for Deployment mode, choose as follows:

    1. On the Scope tags page, optionally add the scope tags you want to apply to this profile.
    1. Select Next.
    2. On the Assignments page, choose Selected groups for Assign to.
    3. Choose Select groups to include, and choose the groups you want to include in this profile.


    1. On the Review + Create page, choose Create to create the profile.

    Capture the hardware ID

    On the client machine, open PowerShell and enter the following commands:

    md c:\HWID

    Set-Location c:\HWID

    Set-ExecutionPolicy -Scope Process -ExecutionPolicy Unrestricted -Force

    Install-Script -Name Get-WindowsAutopilotInfo -Force

    $env:Path += ";C:\Program Files\WindowsPowerShell\Scripts"

    Get-WindowsAutopilotInfo.ps1 -OutputFile AutopilotHWID.csv

    Then we will get the client Hardware ID which is an AutopilotHWID.csv file in the c:\HWID directory.

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact

    Monday, June 10, 2019 7:26 AM

All replies

  • Register your client

    1. In Intune in the Azure portal, choose Device enrollment > Windows enrollment > Devices > Import.

    2.Under Add Windows Autopilot devices in the far right pane, browse to the AutopilotHWID.csv file you previously copied to your local computer. 

    3.Click Import 

    1. Click Sync to sync the device you just registered.

    We also could assign specific user to the device. (Here we will assign user to the device)


    After importing successfully, we should see the profile status as assigned.


    Reset the client back to Out-Of-Box-Experience (OOBE)

    On the client, go to Settings > Update & Security > Recovery and click on Get started under Reset this PC. Select Remove everything and Just remove my files. Finally, click on Reset.

    After the client is restarted, it will enter autopilot OOBE.

    Here the end user can type his password, then the device will reach the desktop.

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact

    Monday, June 10, 2019 7:30 AM