This page provides a high-level overview of the licenses and accounts needed to deploy both managed and unmanaged HoloLens 2 devices in your organization. It also includes information for licensing of Dynamics 365 Remote Assist and Guides.
1Auto-enrollment during initial device setup, which registers and joins Microsoft Entra and allows the device to be managed with Intune.
2Windows Autopilot for HoloLens 2 simplifies the provisioning experience for both IT admins and end users. IT admins can preconfigure HoloLens 2 policies, and upon first boot, devices will be deployed in business-ready state with zero end-user interaction.
3 This account must be provisioned ahead of time with Windows Configuration Designer (WCD).
Important
Active Directory (AD) cannot be used to manage HoloLens devices.
Warning
Multiple users are not supported for a device using either a MSA or local account.
Dynamics 365 Licensing and Requirements
Dynamics 365 Remote Assist
Admin
Microsoft Entra account (required for purchasing the subscription and assigning licenses)
If you plan on implementing this cross-tenant scenario, you may need an Information Barriers license. See this article to determine if an Information Barrier License is required.
Dynamics 365 Guides
Admin
Microsoft Entra account (required for purchasing the subscription and assigning licenses)
Plan and execute an endpoint deployment strategy, using essential elements of modern management, co-management approaches, and Microsoft Intune integration.