# Windows Autopilot > Enroll Windows Devices with Applivery through Windows Autopilot — configure the MDM handover, deployment profile, and hardware registration for zero-touch provisioning. Source: https://docs.applivery.com/en/device-management/windows/enrollment/windows-autopilot/ • Last updated: 2026-08-08 **Key topics:** Windows Autopilot, MDM handover, Deployment profile, Hardware registration, Zero-touch provisioning, Microsoft Entra ID, Microsoft Intune, Applivery, MDM --- **TL;DR:** Configure Windows Autopilot with Applivery by setting the MDM handover in Entra, creating a deployment profile, registering device hardware hashes, and letting devices provision automatically on first boot. **Windows Autopilot** is Microsoft's zero-touch provisioning technology: it lets a brand-new Windows Device configure itself the first time it's turned on, with no manual imaging or setup. When you combine Autopilot with Applivery, the device is redirected to Applivery during the out-of-box experience (OOBE) — so the Applivery Agent, your Policies, and your Apps are installed automatically the moment the user signs in. :::warning Before starting this configuration, make sure you have completed the [Microsoft Entra ID setup](https://docs.applivery.com/en/device-management/windows/enrollment/entra-id-enrollment/). Autopilot requires an **active Entra ID integration** to redirect devices to Applivery during enrollment. ::: ## 1\. Configure the MDM Handover This is the most critical step. It tells Microsoft Entra: _"Do not manage this device yourself; send it to Applivery."_ **Log in to the Azure Portal** Sign in to the [**Azure Portal**](https://portal.azure.com/) with an account that has permission to manage Mobility settings. **Open the Mobility (MDM and WIP) settings** Navigate to **Manage** > **Mobility (MDM and WIP)**. **Select your Applivery application** Click on your **Applivery** application. It should already appear listed in the mobility applications panel — if it isn't there, add it first. ![mobility mdm and wip](https://docs.applivery.com/int/_r2/media/09ac0a4e-3ad8-478f-9f15-3474973eec71/7d01e64a-8cac-4039-a2f0-0546df5b1373.png) **Set the MDM User Scope and verify the Discovery URL** Set the **MDM User Scope** to **All**, or target a specific security group by choosing **Some**. Then verify that the **MDM Discovery URL** points to the **Applivery Enrollment Endpoint**. This URL is what redirects the device away from Intune and toward Applivery — it should have been configured during the [Entra ID setup](https://docs.applivery.com/en/device-management/windows/enrollment/entra-id-enrollment/). ![mdm user scope](https://docs.applivery.com/int/_r2/media/09ac0a4e-3ad8-478f-9f15-3474973eec71/95a42853-ac3b-45bb-87b6-cb405eaae406.png) ## 2\. Create the Deployment Profile The deployment profile controls the **Out-of-Box Experience (OOBE)** — what the user sees when they turn on the computer. **Open Deployment Profiles in Intune** In the [**Microsoft Intune Admin Center**](https://intune.microsoft.com/#home), go to **Devices** > **Windows**, then to **Enrollment** > **Deployment Profiles**. :::info Creating a deployment profile requires one of these licenses: **Microsoft 365 E3**, **Microsoft 365 E5**, **Microsoft 365 F1**, **Microsoft 365 F3**, or **Microsoft 365 Business Premium**. ::: **Create a new profile** Click **\+ Create profile** > **Windows PC**. **Name your profile** Use a descriptive name that identifies its purpose, for example: `Applivery-Standard-Setup`. **Configure the OOBE settings** Configure the out-of-box experience with the following settings: - **Deployment mode**: select `User-driven`. - **Join to Microsoft Entra ID as**: select `Microsoft Entra ID joined`. - **Hide privacy settings**: set to `Hide` for a smoother experience. - **User account type**: select `Standard user` (recommended for security). {/\* TODO: image — Deployment profile OOBE settings \*/} **Save and assign the profile** **Save** the profile and assign it to an Entra ID group containing your target devices. The profile will be applied automatically to all devices registered in that group. ## 3\. Hardware Registration The device needs to be _"known"_ by Microsoft before it can be managed by Autopilot. **Get the hardware hash for each device** The hardware hash is a unique identifier used to register the device in Autopilot. You can obtain it by either: - Requesting the `.csv` file directly from your hardware vendor. - Running the `Get-WindowsAutopilotInfo.ps1` PowerShell script on the devices. **Open the Devices import screen in Intune** In the [**Microsoft Intune Admin Center**](https://intune.microsoft.com/#home), go to **Devices** > **Windows**, then to **Enrollment** > **Devices**. **Import the CSV file** Click **Import** and upload your `.csv` file. **Wait for the import to complete** The status will change from **Pending** to **Assigned** once the deployment profile from Phase 2 is applied. This may take a few minutes. ## 4\. Verification & Handover Once a registered device is turned on, the automatic provisioning flow begins. **Connect the device to Wi-Fi** As soon as the device connects to the internet, it recognizes its Autopilot profile automatically. **Sign in with Microsoft Entra credentials** The user is prompted to enter their corporate Microsoft account credentials during the OOBE setup. **Entra ID redirects the device to Applivery** After authentication, Entra ID verifies the user and uses the **MDM Discovery URL** configured in Phase 1 to redirect enrollment to Applivery instead of Intune. **Automatic provisioning begins** The Applivery Agent is installed automatically, and the device starts downloading your configured Policies and Apps. ![provisioning](https://docs.applivery.com/int/_r2/media/09ac0a4e-3ad8-478f-9f15-3474973eec71/afea5756-39df-4eb5-86f3-3375fe99329f.png) With Autopilot configured, every new device your organization powers on enrolls into Applivery on its own — no manual imaging, no technician touch, and your Policies and Apps applied from the very first boot.