This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 96%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAA%3C/text%3E%3C/svg%3E)
Hello!
Currently, we're using the deployment profile and Enrollment Status Page for Autopilot devices. I’d like to explore using Device Preparation Policies under Windows Autopilot Device Preparation in Intune.
If we decide to use Device Preparation Policies, should we remove the main Autopilot group from the deployment profile and Enrollment Status Page? Additionally, I don't see an option to set a naming convention or exclude a group. How do Device Preparation Policies work?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(188.79999999999998, 35%, 28%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EZM%3C/text%3E%3C/svg%3E)
@Ahmed Alshatawi, Thanks for posting in Q&A.
Based on my research, if you we decide to use Device Preparation Policies, we should remove the main Autopilot group from the deployment profile and Enrollment Status Page, because Windows Autopilot and assigned a deployment profile will prioritize the Autopilot profile over the Device Preparation policy.
Windows Autopilot device preparation user-driven Microsoft Entra join is a solution that automates the configuration of Windows on a new device without the need for IT intervention. Normally the device is delivered directly from an OEM or reseller to the end-user Windows Autopilot device preparation user-driven deployments use the existing Windows installation installed by the OEM at the factory. It improves the onboarding experience by providing a profile experience to deploy configurations efficiently, consistently, and remove the complexity out of troubleshooting. Windows Autopilot Device Preparation is a feature designed to streamline device provisioning by automating the deployment of applications and configurations during the out-of-box experience (OOBE). It enhances the traditional Autopilot process by providing near real-time deployment status and monitoring, thereby reducing IT overhead and improving user experience. So, there is not an option to set a naming convention or exclude a group.
During the out-of-box experience (OOBE), a user authenticates with their corporate credentials. If there's a Windows Autopilot device preparation policy assigned to the user signing in, then that policy is delivered to the device. It then determines the configuration that needs to be applied to the device based on the settings configured in the policy.
Here is a link about Windows Autopilot device preparation user-driven Microsoft Entra join process
Hope above information can help you.
If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Thank you @ZhoumingDuan-MSFT for all the info.
We currently have four deployment profiles, each with different configurations, naming conventions, user account types, dynamic groups, deployment modes, etc., and they are excluded from the main deployment profile. Can this process be accomplished with Device Preparation Policies through priority settings, and how exactly does it work? Also, what's the difference between 'Device group' and 'Assignments'? Should the same group be assigned? Does Self-Deploying available with Autopilot device preparation (we have shared devices)? Thanks you!
If the device was not Windows autopilot and deployed Windows Autopilot device preparation policy, the process can be accomplished, when the user of the include group login in device, the process will start.
Device Group: This is a security group that devices are automatically added to during the deployment process. It's essential to create this group with specific configurations, including assigning ownership to the "Intune Provisioning Client" service principal. This group serves as a target for device-specific configurations, applications, and scripts.
Assignments: This refers to the user group to which the Device Preparation Policy is assigned. When a user from this group signs into a device during OOBE, the associated policy is applied, and the device is subsequently added to the specified device group.
It's crucial to ensure that the device group specified in the policy is the same group to which configurations, applications, and scripts are assigned. This alignment guarantees that devices receive the intended settings during deployment.
Currently, Windows Autopilot device preparation policy only support user-driven model.
https://learn.microsoft.com/en-us/autopilot/device-preparation/overview#capabilities
Naming conversation is not supported in Device Preparation. As I know it, you can keep both solutions same time. But Device Preparation has some serious lacks, so my recommendation is that if you are already set and experienced with Autopilot in the company, stick with it. Device Preparation might be a good start with light enrollment approach if device hash gathering is for some reason difficult for the company. We are still looking forward how this will develope :)