Getting Started with Windows Autopilot and OneDeploy

Overview

Windows Autopilot integration allows devices deployed with OneDeploy to automatically enrol into your Organisation’s Microsoft Autopilot management environment during the Windows Out-of-Box Experience (OOBE).

When this integration is configured:

• OneDeploy deploys Windows to the device.
• The device hardware ID is automatically registered with Windows Autopilot.
• Microsoft recognises the device during first boot.
• The user signs in with organisational credentials.
• The device joins Microsoft Entra and enrols into Intune.

This allows devices to be rebuilt, replaced, or newly deployed while still using modern cloud-based device management.

Setup Overview

Autopilot integration requires configuration in two systems:

1. Microsoft Entra / Microsoft Intune
2. The OneDeploy WebApp

It is recommended the Microsoft Entra environment be prepared first, as it provides the credentials and configuration required for OneDeploy to communicate with Microsoft services.

After this preparation is complete, the integration can be configured in the OneDeploy WebApp so that devices are automatically registered with Windows Autopilot during deployment.

Where to Start

To configure Autopilot integration, follow the documentation in the order below.

1. Prepare Microsoft Entra

This article explains how to configure Microsoft Entra and Intune so that devices uploaded by OneDeploy can be recognised and assigned an Autopilot deployment profile.

See “Windows Autopilot Integration – Microsoft Entra” 

2. Configure Autopilot in the OneDeploy WebApp

This article explains how to configure the OneDeploy WebApp so that deployments automatically register devices with Windows Autopilot

See “Windows Autopilot Integration – OneDeploy Steps” 

End-to-End AutoPilot Enrollment Flow

• A device is registered in Windows Autopilot with a Group Tag. You set the Group Tag in a OneDeploy build’s properties.
• The Group Tag is stored as an attribute on the device in Microsoft Entra ID.  OneDeploy handles this for you during deployment.
• A Dynamic Device Group uses the Group Tag to automatically include the device (based on the Group Tag).  Set this up in Entra with a Dynamic membership rule.
• The device becomes a member of the group without manual intervention.  Entra handles this automatically.
• An AutoPilot Deployment Profile is assigned to that group.  By assigning our group to an Autopilot profile, it ensures enrollment is automatic.
• When the device boots and connects to the internet, it contacts the AutoPilot service.
• The assigned AutoPilot profile is applied based on group membership
• The device proceeds through the AutoPilot enrolment experience

For more information on self-deploying and user-driven enrolments, see Technical Overview – Windows Autopilot

Related Articles

• Windows Autopilot Integration – Microsoft Entra
• Windows Autopilot Integration – OneDeploy Steps
• Technical Overview – Windows Autopilot