Due to different environments, configurations, and needs, Windows Autopilot offers several different scenarios. Depending on whether the device is meant for a single user or multiple users and how the device is managed, Autopilot has different capabilities for each scenario. Choose the recipe based on the ingredients in your pantry! Today, let’s focus on two of the most common scenarios for user-driven and pre-provisioned Microsoft Entra join (previously, Azure Active Directory join) deployments.
Editor's note 9.11.2023: We have replaced the resource on Entra joined devices with a more complete one and adjusted the reading time difference.
Time to learn: 119 minutes
READCompare and contrast different scenarios available in Windows Autopilot. Explore a number of scenario capabilities, including comprehensive pros and cons of each. This overview documentation helps you decide between Microsoft Entra join (formerly Azure AD) and hybrid Microsoft Entra join, as well as choose the scenario that’s right for you. User-Driven + Pre-Provisioned + Self-Deployed + Existing Devices + Reset + TPM Attestation + Device Identity + VM |
READJoin your cloud-native endpoints to Azure AD Since today’s scenarios are focused on Microsoft Entra joined devices, let’s start with its basic understanding. Learn about device authentication and management with Microsoft Entra join (formerly Azure AD join). Compare the use cases, options, and benefits of joining devices to Microsoft Entra. Entra + AAD + Hybrid + Join + Identity + Intune + Authentication + Pro + Enterprise |
|
READWindows Autopilot user-driven Microsoft Entra join in Intune Use this scenario if users at your organization receive new devices directly from an original equipment manufacturer (OEM) or reseller without IT intervention. Speed the deployment up by following the steps in this scenario. Use this walkthrough in a lab or a production environment as needed. User-Driven + Deployment + OEM + Device ESP + User ESP + Entra ID |
READWindows Autopilot for pre-provisioned deployment Microsoft Entra join in Intune Built on top of Windows Autopilot user-driven Microsoft Entra join, this scenario automates the configuration of Windows on new devices delivered from an IT department, OEM, or reseller. Incorporate the new technician flow step toward the end to speed up the final user flow for quick deployment. Pre-Provisioned + Deployment + IT + Device ESP + User ESP + Entra ID |
|
READFollow these steps to deploy Windows with Autopilot in user-driven Microsoft Entra join scenario in Intune.
(39 mins) User-Driven + Entra + Join + Intune + ESP |
READFollow these steps to deploy Windows with Autopilot in pre-provisioned Microsoft Entra join scenario in Intune.
(50 mins) Pre-Provisioned + Entra + Join + Intune + ESP |
|
WATCHWindows Autopilot: User experience with user-driven Microsoft Entra join Want to see what user-driven Autopilot deployment looks like? Take a look at what the users in your organization will experience as part of their device setup. Share this video with your users to familiarize them with the process. (2 mins) Entra + User-Driven + Autopilot + Device Deployment + Region + Keyboard + Network + Updates + Profile + ESP |
If you’ve missed the introduction, review Skilling snack: Windows Autopilot 101. Is it the user-driven or the pre-provisioned scenario that fits your needs best? Don’t forget that there are more Autopilot scenarios available for less common situations.
Come back for more skilling snacks biweekly. Leave a comment below with ideas for future skilling snacks or to share your experience with peers!
Continue the conversation. Find best practices. Bookmark the Windows Tech Community and follow us @MSWindowsITPro on Twitter. Looking for support? Visit Windows on Microsoft Q&A.
Updated Sep 11, 2023
Version 2.0FrankRojas
Microsoft
Joined December 14, 2018
Windows IT Pro Blog
Follow this blog board to get notified when there's new activity