Set Up Windows Autopilot Device Preparation With Enrollment Time Grouping in Intune
Set up Windows Autopilot device preparation: assigned device group owned by Intune Provisioning Client, apps and scripts in System context, policy and rollback.

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.
To set up Windows Autopilot device preparation in Intune, create an assigned security device group owned by the Intune Provisioning Client service principal (AppId f1346770-5b25-470b-88bd-d5744ab7952c), assign the essential apps and platform scripts to that group in System context, then create a User Driven device preparation policy that names the device group and is assigned to a user group. When a user in that user group signs in during the out-of-box experience (OOBE), enrollment time grouping drops the device straight into the device group, and the apps and scripts you picked in the policy install before the desktop appears. The constraint that decides most pilots: the device must not run a classic Autopilot profile. If the device is registered in Windows Autopilot and not associated with your tenant, the Autopilot profile wins and device preparation never starts. Device preparation needs Windows 11 (24H2, or 23H2 or 22H2 with KB5035942 or later) and supports Microsoft Entra join only.
#How new Windows devices are handled today
In most Intune tenants, new Windows devices are registered in classic Windows Autopilot, picked up by a dynamic device group, and given a deployment profile plus an Enrollment Status Page (ESP). That works, and it remains the only option for pre-provisioned, self-deploying and existing-device scenarios, for Microsoft Entra hybrid join, Windows 10, HoloLens and Teams Meeting Rooms. If you run it, the group tag approach in routing Autopilot profiles with group tags and dynamic device groups is still the way to keep profiles predictable.
The friction sits in two places. Devices have to be registered before anyone can use them, so a laptop bought outside the usual reseller channel waits until someone registers it. And configuration depends on dynamic group membership being evaluated in time; Microsoft notes that assigning devices directly to a device group delivers apps, scripts and policies faster and more efficiently than a dynamic device group. When something stalls, the classic Autopilot deployment report shows only registered devices and is not real time, so a half-built laptop can reach its user before anyone at the service desk notices.
#A better way to get configuration onto new devices
Windows Autopilot device preparation replaces the registration step and the dynamic group with enrollment time grouping. When the user authenticates during OOBE, Intune adds the device to a predefined assigned security group as it enrolls, and configuration assigned to that group starts arriving immediately. One policy holds the deployment settings, the OOBE settings, and the list of apps and scripts that must finish before the user reaches the desktop. There is no ESP; if you see one, the device is running classic Autopilot instead.
Three things are worth knowing before you choose it for a device type:
- Only the apps and scripts selected in the policy install during OOBE: up to 25 managed apps and up to 10 PowerShell scripts. Anything else assigned to the device group installs after the deployment finishes.
- Policies assigned to the device group are synced during the deployment, but their application isn’t tracked, so a configuration profile may land during OOBE or shortly after.
- Win32 and line-of-business apps can be deployed in the same deployment, which classic Autopilot doesn’t support.
The flow below shows the order the pieces depend on each other and where a pilot device drops out of device preparation.
Rendering diagram...
#Setting up a pilot device preparation policy
Do this with a small pilot user group and a few unregistered Windows 11 devices. The steps follow Microsoft’s user-driven Microsoft Entra join tutorial. Before you start, confirm that Windows automatic Intune enrollment is configured and that pilot users are allowed to join devices to Microsoft Entra ID (Microsoft Entra ID > Devices > Device settings > Users may join devices to Microsoft Entra). Pilot users also need an Intune licence.
-
Check that the service principal exists. This is read-only. Connect with
Connect-MgGraph -Scopes 'Application.Read.All','Group.Read.All', then run:1Get-MgServicePrincipal -Filter "appId eq 'f1346770-5b25-470b-88bd-d5744ab7952c'" | Format-List Id, DisplayName, AppIdOne result means it’s there. In some tenants it’s named Intune Autopilot ConfidentialClient rather than Intune Provisioning Client; the AppId is what matters. Save the
Idvalue. -
Only if nothing came back, add it. This changes the tenant. In a session opened with
Connect-MgGraph -Scopes "Application.ReadWrite.All"by an administrator allowed to add service principals, runNew-MgServicePrincipal -AppID f1346770-5b25-470b-88bd-d5744ab7952c. If it already exists you get a 409 Conflict withRequest_MultipleObjectsWithSameKeyValue, which changes nothing. -
Create the device group. In the Intune admin center, go to Groups > New group. Set Group type to Security, Microsoft Entra roles can be assigned to the group to No and Membership type to Assigned. Under Owners, add Intune Provisioning Client. Device preparation uses assigned groups only, never dynamic ones. Microsoft recommends a new group used only for this policy rather than one shared with classic Autopilot. Don’t add devices; the deployment adds them.
-
Create the user group. A security group, assigned or dynamic, containing only the pilot users or groups of users. Its members are the people who get the deployment.
-
Assign the essential apps and scripts to the device group. For each app, open Apps > Windows, select it, then Properties > Assignments > Edit and add the device group under Required, with Install Context set to Device context where it applies. For each script, open Devices > Scripts and remediations > Platform scripts, and add the device group under Included groups. Set Run this script using the logged on credentials to No so it runs as System, because nobody is signed in during OOBE. Supported app types are LOB, Win32, Microsoft Store apps that support WinGet, Microsoft 365 and Enterprise App Catalog.
-
Create the policy. Go to Devices > Windows > Enrollment > Device preparation policies > Create > User Driven. On Device group, choose the device group, not the user group. Under Deployment settings, choose User-driven, Single user and Microsoft Entra joined, and set User account type. Under Out-of-box experience settings, set Minutes allowed before showing installation error (15 to 720, for the whole deployment) and decide on Allow users to skip setup after multiple attempts and Show link to diagnostics. Add the same apps and scripts you assigned in step 5 under Apps and Scripts. On Assignments, choose the user group. Review and save.
-
Decide how devices are trusted. Corporate identifiers are required only if enrollment restrictions block personal Windows devices. Device association is optional, and the language, keyboard, privacy, licence terms and device name settings in the policy only take effect on associated devices. The Apps and Scripts sections apply to every deployment.
Before the pilot, read the device group’s owners back with Get-MgGroupOwner -GroupId $deviceGroupId and confirm the service principal’s Id from step 1 is listed. Keep that output and the group IDs with your change record.

#Who can change the policy and the device group
Give the people who manage device preparation a custom Intune role instead of Intune Administrator. Microsoft’s required permissions are: Device configurations Read, Delete, Assign, Create and Update; Enrollment programs Enrollment time device membership assignment; Managed apps Read; Mobile apps Read; and Organization Read. Create it under Tenant administration > Roles > Create > Intune role, and use scope tags if regional teams need their own policies. Microsoft’s troubleshooting guidance lists a missing enrollment time permission on the admin who created the policy as one reason devices aren’t added to the group.
Treat the device group as part of the policy. Anyone who can change its owners, delete it or switch it from assigned to dynamic can break deployments: Microsoft lists each of those as a cause of failed group membership updates, which can leave devices without the security configuration assigned to the group. Who may own and edit it belongs in the same change control as the policy itself.
Two settings change what a new user can do on the device. Allow users to skip setup after multiple attempts adds a Continue anyway button that lets a user reach the desktop after a failed deployment, so leave it off for devices that must not be used half-configured. And check the local administrator outcome described under the mistakes below before relying on Standard User.
#Check it worked on the first pilot device
Run the first device with a pilot user and watch it from the admin center: Devices > Monitor > Windows Autopilot device preparation deployments. The report updates in near real time and shows each device’s deployment status (In progress, then Success or Failed), the last reported phase (policy installation, script installation or app installation), the deployment time and the user who signed in.
Select the device to open its deployment details. The pilot passes when:
- the deployment status is Success and the deployment policy and policy version are the ones you just saved;
- every app and script you selected shows Installed, with nothing Skipped or Failed;
- the device appears as a member of the device group; and
- the signed-in user has the account type you chose.
Skipped usually means the item was selected in the policy but isn’t assigned to the policy’s device group, or the app isn’t applicable to the device. Deployment records are cleaned up automatically every 28 days, so note pilot results before then.
#Where it goes wrong
The ESP appears, or device preparation never starts. The ESP isn’t part of device preparation, so seeing it means the device is a registered Autopilot device with a profile. Pick pilot devices that aren’t registered, or use device association. If a registered device shows no profile at all, finding why an Autopilot device shows profile not assigned covers the classic side. A device that never launches device preparation may also be below the minimum Windows build: check with the OEM that devices ship with KB5035942 or later, and use installation media dated April 2024 or later for 23H2 and 22H2.
The policy won’t save its device group, or shows 0 groups assigned. The group isn’t owned by Intune Provisioning Client. Saving may show “There was a problem with the device security group” or “Failed to update security group device preparation setting”. Add the service principal as owner.
Devices aren’t added to the device group. Check the owner, check that the policy names the right group, check that Microsoft Entra roles can be assigned to the group is No, and check that the admin who created the policy has the enrollment time membership permission.
Users reach the desktop without their apps. There’s a documented conflict between the policy’s User account type and the Microsoft Entra setting Registering user is added as local administrator on the device during Microsoft Entra join. With Standard User in the policy and that Entra setting on Selected or None, provisioning is skipped. To get standard users, Microsoft lists three working combinations: Entra setting None with the policy on Administrator; Entra setting Selected, without those users, with the policy on Administrator; or Entra setting All with the policy on Standard User.
A user gets the wrong policy. When several user-driven policies reach the same user, the one highest in the list (smallest Priority number) wins. Drag policies to reorder them.
The device sits at 100%. This is a known issue; the user has to restart the device for the deployment to continue. Tell pilot users before they start.

#Backing out of the pilot
The policy reaches people only through its user group, so the cleanest rollback is to remove a user, or the whole pilot group, from the policy’s user group. A user outside the policy’s user group doesn’t get the device preparation deployment on the next device they set up. Removing them doesn’t undo what a completed deployment already did, so handle devices that finished through your usual Intune assignments.
If a change to the policy causes failures, compare the policy version on failed devices with the last version that succeeded. The version goes up by one each time the policy is saved, which tells you which edit to undo. Put the setting back from your change record and run one device again before reopening the pilot.
Don’t remove Intune Provisioning Client as the group’s owner or delete the device group while any policy uses it. If devices were deployed while the group was broken, Microsoft’s fix is to add the affected devices to the correct security group by hand. If you added the service principal in step 2 and are abandoning device preparation altogether, and no device preparation policy references any group it owns, Microsoft’s device preparation pages don’t describe taking it out again, so treat removal as optional: if you want it gone, remove it with Remove-MgServicePrincipal -ServicePrincipalId $servicePrincipalId in a session with Application.ReadWrite.All, and recreate it with step 2 if you change your mind. Leave it in place if you might return to device preparation.
#What to track during the pilot
The first three come straight from the deployment report. Over the pilot, track:
- the share of deployments that end in Success rather than Failed;
- the median deployment time against the error threshold you set in the policy;
- how many apps or scripts end Skipped, which should fall to zero once assignments are right; and
- how many failed deployments the service desk first hears about from the user rather than from the report.
Compare those with the same device model provisioned through classic Autopilot, so the decision to widen the pilot rests on your own figures. Review them weekly until the user group covers the device types you intend to move.
#Before you go live with more users
- Devices run Windows 11 at the minimum build, are Microsoft Entra joined only, and aren’t registered Autopilot devices unless associated.
- The device group is assigned, security, not role-assignable, owned by Intune Provisioning Client and used by one policy.
- Every app and script in the policy is assigned to that device group and runs in System context.
- The user group contains users only, and policy priorities are in the order you expect.
- The account type and the Entra local administrator setting are one of Microsoft’s working combinations.
- Admins hold the custom role with the enrollment time membership permission.
- Pilot devices showed Success with every item Installed.
- If enrollment restrictions block personal devices, corporate identifiers are uploaded. If a pilot device is refused with 0x80180014, see what error 0x80180014 means when Windows MDM enrollment is blocked.
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 articles
Zero-Touch & Automation
Route Windows Autopilot Profiles With Group Tags and Dynamic Device Groups
Autopilot devices getting the wrong profile? Set group tags, build OrderID dynamic device groups, assign one profile per group, then validate and roll back.
ReadEnterprise 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.
ReadPlatforms and devices
Microsoft Previews Remote Lock for Lost Windows Devices in Intune
Microsoft has started a preview that lets IT lock a lost or stolen Windows device from Intune without wiping it. How the group-based preview works, which editions it covers, and why the lock group needs protecting.
ReadDiscover more
Graduate Learning
Ops Playbook
- 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
- PlaybookIntune Endpoint Analytics Devices Missing Startup Performance Scores
Lexicon Definitions
Was this useful?
Reports go to the site owner and are used to correct pages. Corrections are listed at /corrections.
Operate smarter, with fewer recurring tickets.
Receive new operational playbooks, incident-prevention guidance, automation scripts and recovery runbooks.
Comments
Add a thoughtful note on Set Up Windows Autopilot Device Preparation With Enrollment Time Grouping in Intune. Comments are checked for spam and held for moderation before appearing.