Skip to main content
Systems Engineering

Part 3: Create a Windows Autopilot Deployment Profile and Dynamic Device Group in Intune

Build a dynamic device group on the AP-Pilot group tag, assign a user-driven Microsoft Entra join profile with a standard user account and a name template, and wait for Assigned before deploying.

Focused shot of a laptop displaying code, suitable for tech and coding themes.

Advertising disclosure: this article includes partner links. KBY may earn a commission if you sign up or buy through one, at no extra cost to you. How we make money.

Continue the series

You are reading Part 3 of 6

Windows Autopilot with Intune, Step by Step

View all parts

#What this part does

To give registered devices a Windows Autopilot deployment profile automatically, create a dynamic device group whose rule matches a Windows Autopilot device attribute, then assign a deployment profile to that group in the Intune admin centre. The key constraint is timing: group membership and profile assignment are both background processes, and you must not start a deployment until the device’s Profile status reads Assigned and its Date assigned is filled in. A device that starts the out-of-box experience (OOBE) before then may not get your Autopilot settings.

By the end of this part, the pilot laptop from Part 2 is in a dynamic group called SG-Autopilot-Devices-Pilot, and that group has a user-driven, Microsoft Entra join profile assigned. The laptop stays switched off throughout.

#What Parts 1 and 2 set up

Part 1 licensed the pilot users in SG-Autopilot-Pilot, scoped automatic MDM enrolment to them, configured company branding and chose classic Windows Autopilot with user-driven Microsoft Entra join. Part 2 registered one laptop by importing its hardware hash with the group tag AP-Pilot. Registration created the laptop’s Microsoft Entra device object, which stores that tag as OrderID. This part uses that attribute, and leaves the object itself alone.

You need Intune Administrator, or an account that can create security groups in Microsoft Entra ID as well as manage Autopilot profiles in Intune. Intune Administrator can create and manage all security groups, including their dynamic membership rules. Dynamic groups are a Microsoft Entra ID P1 feature, which the pilot licences from Part 1 include. A group whose members are only devices needs no extra licence.

#Step 1: Pick the rule that finds the right devices

Microsoft says to build Autopilot device groups only from Autopilot device attributes, which only registered devices carry. A rule on any other attribute does not guarantee the device is a member before provisioning, which can leave it with the wrong configuration during OOBE. Two attributes matter here:

Dynamic membership rules for Windows Autopilot device groups
RuleMatchesUse it for
(device.devicePhysicalIDs -any (_ -startsWith "[ZTDid]"))Every registered Windows Autopilot device in the tenantSettings every Autopilot device should get
(device.devicePhysicalIds -any (_ -eq "[OrderID]:AP-Pilot"))Only Autopilot devices with the group tag AP-PilotThe pilot, and later any set of devices that needs its own profile

This series uses the group tag rule. A profile assigned to an all-devices group reaches every laptop your supplier ever registers to the tenant, which is not what a pilot is for. Microsoft also says that if you deploy different Autopilot scenarios to different devices, each scenario needs its own device group; a tag per scenario keeps that tidy.

Paste each rule exactly as shown rather than retyping it. String comparisons in a rule are not case sensitive, so AP-Pilot and ap-pilot match the same devices, but everything after [OrderID]: must otherwise be the tag exactly as you set it in Part 2.

#Step 2: Create the dynamic device group

  1. In the Microsoft Intune admin centre, select Groups > All groups > New group.
  2. Set Group type to Security and Group name to SG-Autopilot-Devices-Pilot. Add a description that says what the tag is, for example “Autopilot devices with group tag AP-Pilot”.
  3. Set Microsoft Entra roles can be assigned to the group to No.
  4. Set Membership type to Dynamic Device. Add yourself as an owner if your organisation requires one.
  5. Select Add dynamic query. Under Rule syntax, select Edit, paste the rule below, select OK, then Save.
  6. Select Create.
1(device.devicePhysicalIds -any (_ -eq "[OrderID]:AP-Pilot"))

Although you created it in Intune, this is a Microsoft Entra group. Membership is evaluated in the background, not on demand. In a small tenant the laptop usually appears within a few minutes, while large directories can take 30 minutes or longer. Microsoft’s troubleshooting guidance allows up to 24 hours for a new group, or a changed rule, to populate for the first time. Open the group’s Overview page: the dynamic rule processing status should reach Update complete, and the laptop should then be listed under Members. Do not continue until it is.

#Step 3: Create the deployment profile

  1. Go to Devices > Windows. Under Device onboarding, select Enrollment, then under Windows Autopilot select Deployment profiles.
  2. Select Create profile > Windows PC.
  3. On Basics, name it Autopilot Pilot User-driven Entra join. Leave Convert all targeted devices to Autopilot at No. That setting registers unregistered corporate devices in the assigned groups with the Autopilot service, and turning it off later does not remove them. Your group only contains devices that are already registered, so it would do nothing here except surprise you later if someone widened the group.
  4. On Out-of-box experience (OOBE), use the settings in the table below.
  5. On Assignments, under Included groups, select Add groups and choose SG-Autopilot-Devices-Pilot. Check that it landed under included, not excluded: a group in Excluded groups never receives the profile.
  6. On Review + create, check the settings and select Create.
OOBE settings for the pilot profile
SettingValueWhy
Deployment modeUser-drivenThe device is associated with the user who enrols it, and needs their credentials. Self-deploying mode is out of scope for this series
Join to Microsoft Entra ID asMicrosoft Entra joinedThe join type chosen in Part 1; hybrid join is out of scope
Microsoft Software License TermsHideRemoves a page the user does not need to act on
Privacy settingsShow, unless you set them by policyDiagnostic data defaults to Full during OOBE, and hiding privacy settings switches location services off by default. Microsoft notes that some regions might require privacy settings to be shown
Hide change account optionsHideNeeds the company branding set in Part 1
User account typeStandard userAdministrator adds the user to the device’s local Administrators group; pilot users do not need that
Allow pre-provisioned deploymentNoPre-provisioning is a separate scenario
Language (Region)Operating system defaultOr pick your organisation’s language
Automatically configure keyboardYesSkips the keyboard page, but only on a wired connection
Apply device name templateYes: PILOT-%RAND:5%Names pilot laptops consistently

The name template has firm rules: at most 15 characters, letters, numbers and hyphens only, and not all numbers. %SERIAL% inserts the hardware serial number and %RAND:x% inserts x random digits. PILOT-%RAND:5% produces an 11-character name such as PILOT-48213. A prefix plus a long manufacturer serial number can run past 15 characters, so check a real serial before choosing %SERIAL%.

The language and keyboard settings need a wired connection. Over Wi-Fi the user still sees those pages, because Windows needs a language and keyboard before it can join a wireless network. If the pilot laptop has no Ethernet port, expect them in Part 5.

#Step 4: Avoid a profile you did not mean to apply

When a device’s groups are assigned more than one deployment profile, Intune gives it the oldest one. A profile assigned to all devices is only the fallback: the device gets it when no other profile applies. Before you continue, open Deployment profiles and check whether an older profile is assigned to another group that also contains the pilot laptop. If one is, the laptop gets that profile instead of yours. Fix it now, by narrowing that profile’s assignment, rather than during OOBE.

Microsoft also warns against using exclusions with an All devices assignment, which can cause assignment problems that need the hashes uploading again. Targeting named groups, as here, avoids that.

Later changes to this profile apply to every device assigned to it, but a device that has already enrolled only picks them up after it is reset and enrols again. That is one more reason to get the settings right before the laptop’s first deployment.

#Confirm the laptop shows Assigned

  1. Go to Devices > Windows > Enrollment > Windows Autopilot > Devices and search for the laptop’s serial number.
  2. Watch the Profile status column. It moves from Not assigned to Assigning to Assigned. Select Sync and Refresh to update the list. Microsoft gives no fixed time, because assignment depends on group processing, the Intune and Autopilot services and the device’s hash.
  3. When it reads Assigned, select the device. In its pane, Assigned profile should read Autopilot Pilot User-driven Entra join and Date assigned should have a value. If Date assigned is empty, wait.

All three must be true before any deployment. When an internet-connected device starts, it downloads its Autopilot profile straight away and again after each restart. That is why the laptop stays off: switched on early, it could start OOBE without your profile. If it was switched on, restart it once the profile shows Assigned to make it download the profile again.

#When the profile does not arrive

Common group and profile assignment problems
What you seeLikely causeWhat to do
The group has no members after processing completesThe tag in the rule differs from the device’s group tag, or the rule was retyped with a mistakeCompare the rule with the Group tag on the device in Windows Autopilot devices, and paste the rule again from Step 2
The group’s processing status shows Processing errorThe rule could not be evaluatedMembership stops updating until it is fixed; correct the rule from the alert on the group’s Overview page
Profile status stays Not assignedThe group is still processing, or it was added under Excluded groupsConfirm the laptop is a member, then check the profile’s Assignments
The device shows a different profileAn older profile is assigned to another group the device is inNarrow the other profile’s assignment as in Step 4
Profile status shows Fix pending or Attention requiredIntune detected a hardware change on the deviceFix pending clears itself if Intune can register the new hardware. Attention required means the device cannot receive a profile until it is reset and registers again: follow Microsoft’s hardware change guidance, and do not delete the device anywhere to force it

#What Part 4 adds before the first deployment

The pilot laptop is now a member of SG-Autopilot-Devices-Pilot through its AP-Pilot group tag. That group has the user-driven, Microsoft Entra join profile Autopilot Pilot User-driven Entra join assigned, and the laptop’s profile status reads Assigned with a date. Users will join as standard users, and devices will be named PILOT- plus five digits.

Keep the laptop switched off. Without an Enrollment Status Page that waits for the right apps, a user could reach the desktop before their apps and policies are installed. Part 4 creates a custom Enrollment Status Page, assigns it to SG-Autopilot-Devices-Pilot, and chooses which apps block the desktop and how long to wait for them. Part 5 then runs the first deployment.

About this page

Credited to

Dates

Published

Sources

This page lists no external sources.

Corrections

No corrections are listed for this page. Some review sweeps corrected pages without naming each one; those are in the corrections log.

Series navigation
Part 3 of 6 in Windows Autopilot with Intune, Step by Step
View full series
Reader Interaction

Comments

Add a thoughtful note on Part 3: Create a Windows Autopilot Deployment Profile and Dynamic Device Group in Intune. Comments are checked for spam and held for moderation before appearing.

Loading comments...

Discover more

Was this useful?

Reports go to the site owner and are used to correct pages. Corrections are listed at /corrections.

Engineering insights, direct to you.

Receive the latest Systems Engineering tutorials, production guides, Engineering Labs and operational best practices.