Windows Autopilot introduces device association for provisioning

Windows Autopilot is introducing Device Association to streamline the Windows provisioning process. This new feature allows for device recognition by an organization before a user signs in, enabling the retrieval of settings early enough to modify the out-of-box experience (OOBE).

Unlike classic Autopilot, which requires hardware-hash registration in advance, Device Preparation uses device association to link a device to a tenant during setup. This reduces manual administrative work and prevents stale records caused by hardware repairs or replacements. Administrators can use policies to control enrollment, Entra join settings, and the installation of specific application types, including Win32 and Microsoft 365 packages.

However, Device Preparation is not a complete replacement for the original Autopilot. It does not currently support pre-provisioning, white-glove deployment, self-deploying kiosk modes, or hybrid Active Directory joins. Organizations requiring hardware-bound identity controls or specific Group Tags should continue using the original Windows Autopilot, while Device Preparation is positioned as a simpler option for new cloud-only and Windows 365 environments.