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.

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
#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:
| Rule | Matches | Use it for |
|---|---|---|
(device.devicePhysicalIDs -any (_ -startsWith "[ZTDid]")) | Every registered Windows Autopilot device in the tenant | Settings every Autopilot device should get |
(device.devicePhysicalIds -any (_ -eq "[OrderID]:AP-Pilot")) | Only Autopilot devices with the group tag AP-Pilot | The 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
- In the Microsoft Intune admin centre, select Groups > All groups > New group.
- 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”. - Set Microsoft Entra roles can be assigned to the group to No.
- Set Membership type to Dynamic Device. Add yourself as an owner if your organisation requires one.
- Select Add dynamic query. Under Rule syntax, select Edit, paste the rule below, select OK, then Save.
- 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
- Go to Devices > Windows. Under Device onboarding, select Enrollment, then under Windows Autopilot select Deployment profiles.
- Select Create profile > Windows PC.
- 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. - On Out-of-box experience (OOBE), use the settings in the table below.
- 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. - On Review + create, check the settings and select Create.
| Setting | Value | Why |
|---|---|---|
| Deployment mode | User-driven | The 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 as | Microsoft Entra joined | The join type chosen in Part 1; hybrid join is out of scope |
| Microsoft Software License Terms | Hide | Removes a page the user does not need to act on |
| Privacy settings | Show, unless you set them by policy | Diagnostic 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 options | Hide | Needs the company branding set in Part 1 |
| User account type | Standard user | Administrator adds the user to the device’s local Administrators group; pilot users do not need that |
| Allow pre-provisioned deployment | No | Pre-provisioning is a separate scenario |
| Language (Region) | Operating system default | Or pick your organisation’s language |
| Automatically configure keyboard | Yes | Skips the keyboard page, but only on a wired connection |
| Apply device name template | Yes: 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
- Go to Devices > Windows > Enrollment > Windows Autopilot > Devices and search for the laptop’s serial number.
- 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.
- When it reads Assigned, select the device. In its pane, Assigned profile should read
Autopilot Pilot User-driven Entra joinand 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
| What you see | Likely cause | What to do |
|---|---|---|
| The group has no members after processing completes | The tag in the rule differs from the device’s group tag, or the rule was retyped with a mistake | Compare 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 error | The rule could not be evaluated | Membership stops updating until it is fixed; correct the rule from the alert on the group’s Overview page |
| Profile status stays Not assigned | The group is still processing, or it was added under Excluded groups | Confirm the laptop is a member, then check the profile’s Assignments |
| The device shows a different profile | An older profile is assigned to another group the device is in | Narrow the other profile’s assignment as in Step 4 |
| Profile status shows Fix pending or Attention required | Intune detected a hardware change on the device | Fix 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
Corrections
No corrections are listed for this page. Some review sweeps corrected pages without naming each one; those are in the corrections log.
Related labs
Calculators and what-if tools that go with this article.
- Intune AssignmentsCheck whether a user and device receive an Intune app or policy: group include and exclude rules, assignment filters in include or exclude mode, and app intent conflicts.Open the lab
- Port LookupSearch ports and protocols for common infrastructure services, plus the network requirements for Intune, Autopilot, Apple push notifications and Entra Connect, with copy-ready firewall rules.Open the lab
- Apple Update DatesWork out when an iOS or macOS update becomes visible under a Declarative Device Management or legacy deferral, and when a DDM enforcement deadline forces the install.Open the lab
Related articles
Enterprise IT Management
Part 2: Register Devices in Windows Autopilot: Import Hardware Hashes into Intune
Capture a pilot laptop's hardware hash with Get-WindowsAutopilotInfo, tag it AP-Pilot, import the CSV into Intune, and leave the Entra device object that registration creates alone.
ReadEnterprise IT Management
Set a Microsoft 365 Group Naming Policy in Graph PowerShell Without Overwriting Other Group Settings
Add group name prefixes, suffixes and blocked words in Microsoft 365 with Graph PowerShell, keeping group creation and guest settings intact, with checks and rollback.
ReadEnterprise IT Management
Block Automatic External Email Forwarding in Exchange Online With an Approved-Sender Exception
Turn off automatic external email forwarding in Exchange Online, keep it for an approved group, test for 5.7.520 and roll back safely.
ReadEnterprise IT Management
Scope Microsoft Graph Mail Access to Specific Mailboxes with Exchange Online RBAC for Applications
Scope an app's Graph mail access to specific mailboxes with RBAC for Applications in Exchange Online, test it, remove the unscoped Entra grant and keep a tested rollback.
ReadDiscover more
Graduate Learning
Ops Playbook
- PlaybookSet Up Windows Autopilot Device Preparation With Enrollment Time Grouping in Intune
- PlaybookConfigure the Autopilot Enrollment Status Page to Block Desktop Use Until Required Apps Install
- PlaybookRun Intune Remediations On Demand to Fix One Windows Device Without Waiting
- PlaybookRoute Windows Autopilot Profiles With Group Tags and Dynamic Device Groups
Lexicon Definitions
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.
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.