Autopilot with white glove deployment

Microsoft has released an updated autopilot version called white glove! With the traditional autopilot version there was one big disadvantage on delivering a laptop directly from the OEM to the end user, and that was the waiting time for the end user to complete the installation of all applications, settings and policies.

OEM
The original Autopilot deployment (Source: docs.microsoft.com)

With the next release the provisioning will be split. The time consuming part can now be performed by the IT department, IT Partner or even the OEM provider. Giving the end user a short and simple process before they can start using their device.

OEM
The new white glove Autopilot deployment (Source: docs.microsoft.com)

But with new features there are always new requirements. With the new white glove autopilot it is still possible to use both the Azure AD join and the Hybrid Azure AD join scenarios. However these are the new requirements:

  • Windows 10 version 1903 is required
  • An Intune subscription (customer)
  • Physical devices with a TPM 2.0 chip (Virtual machines are not supported!)
  • Physical devices with Ethernet connectivity, Wi-fi is not supported.

Because the OEM or vendor performs the white glove process, this doesn’t require access to an end-user’s on-premise domain infrastructure. This is unlike a typical hybrid Azure AD-joined scenario because rebooting the device is postponed. The device is resealed prior to the time when connectivity to a domain controller is expected, and the domain network is contacted when the device is unboxed on-premise by the end-user.