,

Windows Autopilot Self-Deploying for HoloLens 2 devices (Preview)

Platforms
Windows
Products
IntuneAutopilotHoloLens 2
Result
A HoloLens 2 joins Microsoft Entra ID, enrolls in Intune and shows the sign-in screen without any user setup

Overview

Ship HoloLens 2 devices that join Microsoft Entra ID and enroll in Intune by themselves with Windows Autopilot self-deploying mode.

Since November 2020, Windows Autopilot for HoloLens 2 has been available in public preview to anyone with Intune and Microsoft Entra ID licences and a real HoloLens 2 (it doesn't work in virtual machines or emulators).

The preview supports self-deploying mode with Microsoft Entra join. Self-deploying mode sets up a device as a kiosk, digital signage or shared device without user interaction.

For a fully automatic setup, connect the device to the network on the first setup screen with a USB-C to Ethernet adapter. Otherwise, the user must connect to Wi-Fi or a hotspot manually to start enrollment.

I wrote about a similar self-deploying scenario for Microsoft Surface devices as a single-app kiosk, see here.

Prerequisites

Before you start, check that you have the following.

What you need

checked 10/2026

Area What you need Docs
Licence Microsoft Intune Plan 1 and Microsoft Entra ID P1 (or a bundle such as Microsoft 365 E3) Autopilot licences
Admin role Policy and Profile Manager in Intune, to register devices and create the Autopilot profile RolesRegister
Entra ID Automatic MDM enrollment turned on, and no enrollment restriction that blocks Windows devices MDM enrollment
Intune The HoloLens 2 devices registered in Windows Autopilot (reseller, Microsoft Support or hardware hash) RegisterSupport
Devices HoloLens 2 on a supported Windows Holographic version, with a USB-C to Ethernet adapter or Wi-FiWi-Fi in OOBE needs Windows Holographic 20H2 or later. Release notesRequirements
Network Network access to the Autopilot and self-deploying (TPM attestation) URLs Networking

Configuration

With the prerequisites in place, register the devices, then create and assign the profile.

Register the devices with Autopilot

Usually the reseller or distributor registers new devices when you place the order. You can also register them yourself: get the hardware hash (hardware ID) from the HoloLens and upload it to Intune.

Unlike other Windows devices, HoloLens 2 doesn't need a PowerShell script to collect the hardware hash:

  1. While the HoloLens 2 is turned on, press and release the Power and Volume down buttons together. This collects the hardware ID and diagnostic logs (AutopilotDiagnostics.zip).
  2. Connect the HoloLens 2 to a PC with a USB-C cable so that it shows up in File Explorer.
  3. Extract AutopilotDiagnostics.zip from \Internal Storage\Documents on the device. The CSV file name starts with DeviceHash.
Windows Autopilot Self-Deploying for HoloLens 2 devices (Preview) - screenshot 1

Import the CSV file into Intune under Windows Autopilot devices:

Windows Autopilot Self-Deploying for HoloLens 2 devices (Preview) - screenshot 2

For more details, see Obtain hardware hash.

Update (October 2026): you can also ask Microsoft Support to register your HoloLens 2 devices or to send you their hardware hashes (with proof of purchase), see HoloLens 2 registration support for Autopilot.

Create an Autopilot profile for HoloLens 2

In 2021 the profiles were under Devices > Windows > Windows enrollment > Windows Autopilot deployment profiles:

Windows Autopilot Self-Deploying for HoloLens 2 devices (Preview) - screenshot 3

Select Create profile > HoloLens (in 2021 it was called HoloLens (preview)):

Windows Autopilot Self-Deploying for HoloLens 2 devices (Preview) - screenshot 4

Note: Convert all targeted devices to Autopilot isn't supported on HoloLens.

The HoloLens profile uses these settings:

  • Deployment mode: Self-Deploying
  • Join to Microsoft Entra ID as: Microsoft Entra joined
Windows Autopilot Self-Deploying for HoloLens 2 devices (Preview) - screenshot 5

Assign the profile to a Microsoft Entra ID group with your HoloLens 2 devices. When the profile shows under Assigned profile, the device is ready for Autopilot:

Windows Autopilot Self-Deploying for HoloLens 2 devices (Preview) - screenshot 6

Update (October 2026): Microsoft also recommends an Enrollment Status Page (ESP) assigned to the same device group, and checking that no enrollment restriction blocks Windows devices, see Windows Autopilot for HoloLens 2.

Result

Finally, turn on the HoloLens 2 with network access and watch it set itself up.

I didn't find a way to take screenshots on HoloLens 2 during Autopilot (OOBE).

When the HoloLens 2 starts with an internet connection (USB-C to Ethernet adapter), it joins Microsoft Entra ID and enrolls in Intune by itself (through automatic MDM enrollment), and then shows the sign-in screen.

The new device in the Intune admin center:

Windows Autopilot Self-Deploying for HoloLens 2 devices (Preview) - screenshot 7

Because the device enrolled with a self-deploying profile, no user enrolled it and it has no primary user:

  • Ownership: Corporate
  • Operating system: Windows Holographic for Business (no extra licence needed)
  • Device model: HoloLens 2
Windows Autopilot Self-Deploying for HoloLens 2 devices (Preview) - screenshot 8

My device configuration profiles installed in the device context during Autopilot, but my Microsoft Store for Business (MSfB) apps didn't:

Windows Autopilot Self-Deploying for HoloLens 2 devices (Preview) - screenshot 9

App installs in the device context were a known issue in the preview, see the known issues and limitations.

Update (October 2026): Microsoft Store for Business is retired. Download Store apps for HoloLens with WinGet and deploy them with Intune, see Microsoft Store & Intune.

Discover more from HMASLOWSKI.COM

Subscribe now to keep reading and get access to the full archive.

Continue reading