Daily Intune News
Aboutmerill.net
Windows Autopilot
Device enrollment

Create Device Groups for Windows Autopilot | Microsoft Learn

30 October 2026Doc update+43 / −39 lines

In brief

The page received updated metadata, wording, formatting, terminology, and links to related device-group tutorials. Instructions for assigning users and creating dynamic groups were clarified.

What Intune admins need to know

Administrators can use the refreshed guidance and linked resources; no action is required.

This summary was assembled from the tracked documentation change. Verify important details in the full Microsoft Learn article.

Documentation change

View full page diffView on Microsoft Learn

The comparison below shows only the changed extract. Use the full-page view for complete context.

Create device groupsDevice Groups for Windows Autopilot | Microsoft Learn

Note

    - To create a group that includes all of the Windows Autopilot devices, enter: `(device.devicePhysicalIDs -any (_ -startsWith "[ZTDid]"))`.
    - Intune's group tag field maps to the `OrderID` attribute on Microsoft Entra devices. To create a group that includes all Windows Autopilot devices with a specific group tag (the Microsoft Entra device `OrderID`), enter: `(device.devicePhysicalIds -any (_ -eq "[OrderID]:179887111881"))`.
    - To create a group that includes all the Windows Autopilot devices with a specific Purchase Order ID, enter: `(device.devicePhysicalIds -any (_ -eq "[PurchaseOrderId]:76222342342"))`**

    **Save** the expressions.
  1. Select Create.

For a detailed tutorial on creating a device group for each of the Windows Autopilot scenarios using Intune, see the following links:resources:

Add devices

The dynamic device group that includes Windows Autopilot devices automatically adds existing Windows Autopilot devices to the device group. To manually add new devices as Windows Autopilot devices by using a CSV file so that they become part of the device group, see Manually register devices with Windows Autopilot.

Assign a user to a specific Windows Autopilot device

AYou can assign a licensed Intune user can be assigned to a specific Windows Autopilot device. For supported OEMs,manufacturers, this assignment will:assignment:

  • Pre-populatePrepopulates the Microsoft Entra user Principal Name (UPN) under the pre-provisioning landing page and Microsoft Entra sign-in page.
  • AllowsEnables setting of a custom greeting name.

For more informationinformation, including a list of supported OEMs,manufacturers, see Return of key functionality for Windows Autopilot sign-in and deployment experience.

Note

Assigning a licensed user to a specific Windows Autopilot device only affects pre-populatingprepopulating the UPN and setting of a custom greeting name. It doesn't affect assigned policies and applications that are deployed to the device or to the user. The assigned policies and applications are still deployed regardless of the OEM. For more information, see Windows Autopilot for pre-provisioned deployment.

Important

Assigning a user to a specific Windows Autopilot device doesn't work if you're using Active Directory Federation Services (ADFS).

  1. Sign in to the Microsoft Intune admin center.
  2. In the Home screen, select Devicesin the left hand pane.pane, select Devices.
  3. In the Devices | Overview screen,, under By platform, select Windows.
  4. In the Windows | Windows devices screen,, under Device onboarding, select Enrollment.
  5. In the Windows | Windows enrollment screen,, under Windows Autopilot, select Devices.
  6. In the Windows Autopilot devices screen,, select a device, and then in the toolbar select Assign user.
  7. Select a Microsoft Entra ID user licensed to use Intune and select Select.
  8. In the User Friendly Name box,, enter a friendly name or just accept the default.
  9. Select Save.

For a detailed tutorial on assigning a user for each of the Windows Autopilot scenarios viaby using Intune, see the following articles:

Using Windows Autopilot in other portals

If there isnyou't interestre not interested in mobile device management (MDM), you can use Windows Autopilot can be used in other portals. While using other portals is an option, Microsoft recommends only usinguse Intune to manage Windows Autopilot deployments. When you use Intune is used with another portal, Intune isncan't able to:t:

  • Display changes to profiles createdthat you create in Intune,Intune but editededit in another portal.
  • Synchronize profiles createdthat you create in another portal.
  • Display changes to profile assignments donethat you make in another portal.
  • Synchronize profile assignments donethat you make in another portal.
  • Display changes to the device list that were madeyou make in another portal.

Windows Autopilot for existing devices

When enrollingyou enroll Windows devices viathrough Windows Autopilot for existing devices, use a correlator ID can be used to group the Windows devices. The correlator ID is a parameter of the Windows Autopilot configuration file. The Microsoft Entra device attribute enrollmentProfileName is automatically setsets to equal OfflineAutopilotprofile-<correlator ID>. ArbitraryYou can create arbitrary Microsoft Entra dynamic groups can be created when usingyou use the correlator ID from the enrollmentprofileName attribute.

Warning

Because the correlator ID isn't pre-listedprelisted in Intune, the device mightcan report any correlator ID they want.it wants. If the user createsyou create a correlator ID matchingthat matches a Windows Autopilot or Apple ADE profile name, the device is added to any dynamic Microsoft Entra device group based offon the enrollmentProfileName attribute. To avoid this conflict:

  • Always create dynamic group rules matchingthat match against the entireenrollmentProfileName value.
  • Never name Windows Autopilot or Apple ADE profiles beginning with OfflineAutopilotprofile-.

If you want all devices in the groups shouldto automatically register to Windows Autopilot, set the Convert all targeted devices to Autopilot setting to Yes in any Windows Autopilot profiles assigned to the groups, set the setting Convert all targeted devices to Autopilot to Yes.groups. All non-Windows Autopilot devices in assigned groups register with the Windows Autopilot deployment service. Allow 48 hours for the registration to be processed.

When you unenroll and reset the device is unenrolled and reset,device, Windows Autopilot enrolls it again. After you register a device is registered in this way, disabling this setting or removing the profile assignment wondoesn't remove the device from the Windows Autopilot deployment service. TheYou must remove the device must be removed by deregistering the device from Windows Autopilot. For more information onabout how to properly deregister a device, see Deregister a device.

For a full tutorial on Windows Autopilot for existing devices, see the following article:

Daily Intune.Admin.News

Get daily email updates

Get a concise summary of the latest Microsoft Intune updates delivered straight to your inbox.

Loading the secure signup form…