Enroll Windows devices in Intune by using the Windows Autopilot

The Windows Autopilot simplifies enrolling devices in Intune. Building and maintaining customized operating system images is a time-consuming process. You might also spend time applying these custom operating system images to new devices to prepare them for use before giving them to your end users. With Microsoft Intune and Autopilot, you can give new devices to your end users without the need to build, maintain, and apply custom operating system images to the devices. When you use Intune to manage Autopilot devices, you can manage policies, profiles, apps, and more after they're enrolled. For an overview of benefits, scenarios, and prerequisites, see Overview of Windows Autopilot.

There are four types of Autopilot deployment:

Prerequisites

How to get the CSV for Import in Intune

For more information, see the understanding powershell cmdlet.

Add devices

You can add Windows Autopilot devices by importing a CSV file with their information.

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

    Screenshot of Windows Autopilot devices

  2. Under Add Windows Autopilot devices, browse to a CSV file listing the devices that you want to add. The CSV file should list the serial numbers, Windows product IDs, hardware hashes, optional group tags, and optional assigned user. You can have up to 500 rows in the list. Use the header and line format shown below:

    Device Serial Number,Windows Product ID,Hardware Hash,Group Tag,Assigned User
    <serialNumber>,<ProductID>,<hardwareHash>,<optionalGroupTag>,<optionalAssignedUser>

    Screenshot of Adding Windows Autopilot devices

    Important

    When you use CSV upload to assign a user, make sure that you assign valid UPNs. If you assign an invalid UPN (incorrect username), your device may be inaccessible until you remove the invalid assignment. During CSV upload the only validation we perform on the Assigned User column is to check that the domain name is valid. We're unable to perform individual UPN validation to ensure that you're assigning an existing or correct user.

  3. Choose Import to start importing the device information. Importing can take several minutes.

  4. After import is complete, choose Device enrollment > Windows enrollment > Windows Autopilot > Devices > Sync. A message displays that the synchronization is in progress. The process might take a few minutes to complete, depending on how many devices are being synchronized.

  5. Refresh the view to see the new devices.

Create an Autopilot device group

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

  2. In the Group blade:

    1. For Group type, choose Security.
    2. Type a Group name and Group description.
    3. For Membership type, choose either Assigned or Dynamic Device.
  3. 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.

  4. If you chose Dynamic Devices for Membership type above, then in the Group blade, choose Dynamic device members and type any of the following code in the Advanced rule box. Only Autopilot devices are gathered by these rules, because they target attributes that are only possessed by Autopilot devices.

    • If you want to create a group that includes all of your Autopilot devices, type: (device.devicePhysicalIDs -any _ -contains "[ZTDId]")
    • Intune's group tag field maps to the OrderID attribute on Azure AD devices. If you want to create a group that includes all of your Autopilot devices with a specific group tag (the Azure AD device OrderID), you must type: (device.devicePhysicalIds -any _ -eq "[OrderID]:179887111881")
    • If you want to create a group that includes all of your Autopilot devices with a specific Purchase Order ID, type: (device.devicePhysicalIds -any _ -eq "[PurchaseOrderId]:76222342342")

    After adding the Advanced rule code, choose Save.

  5. Choose Create.

Create an Autopilot deployment profile

Autopilot deployment profiles are used to configure the Autopilot devices.

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

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

    Screenshot of Basics page

  3. If you want all devices in the assigned groups to automatically convert to Autopilot, set Convert all targeted devices to Autopilot to Yes. All non-Autopilot devices in assigned groups will register with the Autopilot deployment service. Allow 48 hours for the registration to be processed. When the device is unenrolled and reset, Autopilot will enroll it. After a device is registered in this way, disabling this option or removing the profile assignment won't remove the device from the Autopilot deployment service. You must instead remove the device directly.

  4. Select Next.

  5. On the Out-of-box experience (OOBE) page, for Deployment mode, choose one of these two options:

    • User-driven: Devices with this profile are associated with the user enrolling the device. User credentials are required to enroll the device.
    • Self-deploying (preview): (requires Windows 10, version 1809 or later) Devices with this profile aren't associated with the user enrolling the device. User credentials aren't required to enroll the device. When a device has no user associated with it, user-based compliance policies don't apply to it. When using self-deploying mode, only compliance policies targeting the device will be applied.

    Screenshot of OOBE page

  6. In the Join to Azure AD as box, choose Azure AD joined.

  7. Configure the following options:

    • End-user license agreement (EULA): (Windows 10, version 1709 or later) Choose if you want to show the EULA to users.
    • Privacy settings: Choose if you want to show privacy settings to users.

    Important

    The default value for the Diagnostic Data setting varies between Windows versions. For devices running Windows 10, version 1903, the default value is set to Full during the out-of-box experience. For more information, see Windows Diagnostics Data

    • Hide change account options (requires Windows 10, version 1809 or later): Choose Hide to prevent change account options from displaying on the company sign-in and domain error pages. This option requires company branding to be configured in Azure Active Directory.
    • User account type: Choose the user's account type (Administrator or Standard user).
    • Allow White Glove OOBE (requires Windows 10, version 1903 or later; additional physical requirements): Choose Yes to allow white glove support.
    • Apply device name template (requires Windows 10, version 1809 or later): Choose Yes to create a template to use when naming a device during enrollment. Names must be 15 characters or less, and can have letters, numbers, and hyphens. Names can't be all numbers. Use the %SERIAL% macro to add a hardware-specific serial number. Or, use the %RAND:x% macro to add a random string of numbers, where x equals the number of digits to add.
    • Language (Region)*: Choose the language to use for the device. This option is only available if you chose Self-deploying for Deployment mode.
    • Automatically configure keyboard*: If a Language (Region) is selected, choose Yes to skip the keyboard selection page. This option is only available if you chose Self-deploying for Deployment mode.
  8. Select Next.

  9. On the Scope tags page, optionally add the scope tags you want to apply to this profile. For more information about scope tags, see Use role-based access control and scope tags for distributed IT.

  10. Select Next.

  11. On the Assignments page, choose Selected groups for Assign to.

    Screenshot of Assignments page

  12. Choose Select groups to include, and choose the groups you want to include in this profile.

  13. If you want to exclude any groups, choose Select groups to exclude, and choose the groups you want to exclude.

  14. Select Next.

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

    Screenshot of Review page

Note

Intune will periodically check for new devices in the assigned groups, and then begin the process of assigning profiles to those devices. This process can take several minutes to complete. Before deploying a device, ensure that this process has completed. You can check under Device enrollment > Windows enrollment > Devices where you should see the profile status change from "Unassigned" to "Assigning" and finally to "Assigned."

Edit an Autopilot deployment profile

After you've created an Autopilot deployment profile, you can edit certain parts of the deployment profile.

  1. In Intune in the Azure portal, choose Device enrollment.
  2. Under Windows enrollment, in the Windows Autopilot section, choose Deployment Profiles.
  3. Select the profile you would like to edit.
  4. Click Properties on the left to change the name or description of the deployment profile. Click Save after you make changes.
  5. Click Settings to make changes to the OOBE settings. Click Save after you make changes.

Note

Changes to the profile are applied to devices assigned to that profile. However, the updated profile won't be applied to a device that has already enrolled in Intune until after the device is reset and reenrolled.

Alerts for Windows Autopilot unassigned devices

Alerts will show how many Autopilot program devices don't have Autopilot deployment profiles. Use the information in the alert to create profiles and assign them to the unassigned devices. When you click the alert, you see a full list of Windows Autopilot devices and detailed information about them.

To see alerts for unassigned devices, in Intune in the Azure portal, choose Device enrollment > Overview > Unassigned devices.

Assign a user to a specific Autopilot device

You can assign a user to a specific Autopilot device. This assignment pre-fills a user from Azure Active Directory in the company-branded sign-in page during Windows setup. It also lets you set a custom greeting name. It doesn't pre-fill or modify Windows sign-in. Only licensed Intune users can be assigned in this manner.

Prerequisites: Azure Active Directory Company Portal has been configured and Windows 10, version 1809 or later.

  1. In the Intune in the Azure portal, choose Device enrollment > Windows enrollment > Devices > choose the device > Assign user.

    Screenshot of Assign user

  2. Choose an Azure user licensed to use Intune and choose Select.

    Screenshot of select user

  3. In the User Friendly Name box, type a friendly name or just accept the default. This string is the friendly name that displays when the user signs in during Windows setup.

    Screenshot of friendly name

  4. Choose Ok.

Delete Autopilot devices

You can delete Windows Autopilot devices that aren't enrolled into Intune:

  • Delete the devices from Windows Autopilot at Device enrollment > Windows enrollment > Devices. Choose the devices you want to delete, then choose Delete. Windows Autopilot device deletion can take a few minutes to complete.

Completely removing a device from your tenant requires you to delete the Intune device, the Azure Active Directory device, and the Windows Autopilot device records. This can all be done from Intune:

  1. If the devices are enrolled in Intune, you must first delete them from the Intune All devices blade.

  2. Delete the devices in Azure Active Directory devices at Devices > Azure AD devices.

  3. Delete the devices from Windows Autopilot at Device enrollment > Windows enrollment > Devices. Choose the devices you want to delete, then choose Delete. Windows Autopilot device deletion can take a few minutes to complete.

Using Autopilot in other portals

If you aren't interested in mobile device management, you can use Autopilot in other portals. While using other portals is an option, we recommend you only use Intune to manage your Autopilot deployments. When you use Intune and another portal, Intune isn't able to:

  • Display changes to profiles created in Intune, but edited in another portal
  • Synchronize profiles created in another portal
  • Display changes to profile assignments done in another portal
  • Synchronize profile assignments done in another portal
  • Display changes to the device list that were made in another portal

Windows Autopilot for existing devices

You can group Windows devices by a correlator ID when enrolling using Autopilot for existing devices through Configuration Manager. The correlator ID is a parameter of the Autopilot configuration file. The Azure AD device attribute enrollmentProfileName is automatically set to equal "OfflineAutopilotprofile-<correlator ID>". This allows arbitrary Azure AD dynamic groups to be created based off correlator ID by using the enrollmentprofileName attribute.

Warning

Because the correlator ID is not pre-listed in Intune, the device may report any correlator ID they want. If the user creates a correlator ID matching an Autopilot or Apple DEP profile name, the device will be added to any dynamic Azure AD device group based off the enrollmentProfileName attribute. To avoid this conflict:

  • Always create dynamic group rules matching against the entire enrollmentProfileName value
  • Never name Autopilot or Apple DEP profiles beginning with "OfflineAutopilotprofile-".

Next steps

After you configure Windows Autopilot for registered Windows 10 devices, learn how to manage those devices. For more information, see What is Microsoft Intune device management?