windows-itpro-docs/windows/deployment/windows-autopilot/user-driven.md

title, description, keywords, ms.reviewer, manager, ms.prod, ms.mktglfcycl, ms.localizationpriority, ms.sitesec, ms.pagetype, audience, author, ms.author, ms.collection, ms.topic

title	description	keywords	ms.reviewer	manager	ms.prod	ms.mktglfcycl	ms.localizationpriority	ms.sitesec	ms.pagetype	audience	author	ms.author	ms.collection	ms.topic
Windows Autopilot User-Driven Mode	Windows Autopilot user-driven mode allows devices to be deployed to a ready-to-use state without requiring help from IT personnel.	mdm, setup, windows, windows 10, oobe, manage, deploy, autopilot, ztd, zero-touch, partner, msfb, intune	mniehaus	laurawi	w10	deploy	medium	library	deploy	itpro	greg-lindsay	greglin	M365-modern-desktop	article

Windows Autopilot user-driven mode

Windows Autopilot user-driven mode is designed to enable new Windows 10 devices to be transformed from their initial state, directly from the factory, into a ready-to-use state without requiring that IT personnel ever touch the device. The process is designed to be simple so that anyone can complete it, enabling devices to be shipped or distributed to the end user directly with simple instructions:

• Unbox the device, plug it in, and turn it on.
• Choose a language (only required when multiple languages are installed), locale and keyboard.
• Connect it to a wireless or wired network with internet access. If using wireless, the user must establish the Wi-Fi link.
• Specify your e-mail address and password for your organization account.

After completing those simple steps, the remainder of the process is completely automated, with the device being joined to the organization, enrolled in Intune (or another MDM service), and fully configured as defined by the organization. Any additional prompts during the Out-of-Box Experience (OOBE) can be suppressed; see Configuring Autopilot Profiles for options that are available.

Windows Autopilot user-driven mode supports Azure Active Directory and Hybrid Azure Active Directory joined devices. See What is a device identity for more information about these two join options.

From a process flow perspective, the tasks performed during the user-driven process are as follows:

• Once connected to a network, the device will download a Windows Autopilot profile specifying the settings that should be used (e.g. the prompts during OOBE that should be suppressed).
• Windows 10 will check for critical OOBE updates, and if any are available they will be automatically installed (rebooting if required).
• The user will be prompted for Azure Active Directory credentials, with a customized user experience showing the Azure AD tenant name, logo, and sign-in text.
• The device will join Azure Active Directory or Active Directory, based on the Windows Autopilot profile settings.
• The device will enroll in Intune (or other configured MDM services). (This occurs as part of the Azure Active Directory join process via MDM auto-enrollment, or before the Active Directory join process, as needed.)
• If configured, the enrollment status page (ESP) will be displayed.
• Once the device configuration tasks have completed, the user will be signed into Windows 10 using the credentials they previously provided. (Note that if the device reboots during the device ESP process, the user will need to re-enter their credentials as these are not persisted across reboots.)
• Once signed in, the enrollment status page will again be displayed for user-targeted configuration tasks.

If any issues are encountered during this process, see the Windows Autopilot Troubleshooting documentation.

For more information on the available join options, see the following sections:

• Azure Active Directory join is available if devices do not need to be joined to an on-prem Active Directory domain.
• Hybrid Azure Active Directory join is available for devices that must be joined to both Azure Active Directory and your on-prem Active Directory domain.

User-driven mode for Azure Active Directory join

In order to perform a user-driven deployment using Windows Autopilot, the following preparation steps need to be completed:

• Ensure that the users who will be performing user-driven mode deployments are able to join devices to Azure Active Directory. See Configure device settings in the Azure Active Directory documentation for more information.
• Create an Autopilot profile for user-driven mode with the desired settings. In Microsoft Intune, this mode is explicitly chosen when creating the profile. With Microsoft Store for Business and Partner Center, user-driven mode is the default and does not need to be selected.
• If using Intune, create a device group in Azure Active Directory and assign the Autopilot profile to that group.

For each device that will be deployed using user-driven deployment, these additional steps are needed:

• Ensure that the device has been added to Windows Autopilot. This can be done automatically by an OEM or partner at the time the device is purchased, or it can be done through a manual harvesting process later. See Adding devices to Windows Autopilot for more information.
• Ensure an Autopilot profile has been assigned to the device:
  • If using Intune and Azure Active Directory dynamic device groups, this can be done automatically.
  • If using Intune and Azure Active Directory static device groups, manually add the device to the device group.
  • If using other methods (e.g. Microsoft Store for Business or Partner Center), manually assign an Autopilot profile to the device.

User-driven mode for hybrid Azure Active Directory join

Windows Autopilot requires that devices be Azure Active Directory joined. If you have an on-premises Active Directory environment and want to also join devices to your on-premises domain, you can accomplish this by configuring Autopilot devices to be hybrid-joined to Azure Active Directory (Azure AD).

Requirements

To perform a user-driven hybrid Azure AD joined deployment using Windows Autopilot:

• A Windows Autopilot profile for user-driven mode must be created and
  • Hybrid Azure AD joined must be specified as the selected option under Join to Azure AD as in the Autopilot profile.
• If using Intune, a device group in Azure Active Directory must exist with the Windows Autopilot profile assigned to that group.
• The device must be running Windows 10, version 1809 or later.
• The device must be able to access an Active Directory domain controller, so it must be connected to the organization's network (where it can resolve the DNS records for the AD domain and the AD domain controller, and communicate with the domain controller to authenticate the user).
• The device must be able to access the Internet, following the documented Windows Autopilot network requirements.
• The Intune Connector for Active Directory must be installed.
  • Note: The Intune Connector will perform an on-prem AD join, therefore users do not need on-prem AD-join permission, assuming the Connector is configured to perform this action on the user's behalf.
• If using Proxy, WPAD Proxy settings option must be enabled and configured.

Azure AD device join: The hybrid Azure AD join process uses the system context to perform device Azure AD join, therefore it is not affected by user based Azure AD join permission settings. In addition, all users are enabled to join devices to Azure AD by default.

Step by step instructions

See Deploy hybrid Azure AD joined devices using Intune and Windows Autopilot.