Deploy cloud connected HoloLens 2 to external clients

This guide is a supplement to the Cloud Connected Deployment Guide. It's used in situations where your organization wants to ship HoloLens 2 devices to an external client's facility for short or long-term use. The external client will log into the HoloLens 2 device using credentials provided by your organization, and use Remote Assist to contact your experts. This guide provides general HoloLens 2 deployment recommendations that are applicable to most external HoloLens 2 deployment scenarios and common concerns that customers have when deploying Remote Assist for external use.


The following infrastructure should be in place per the Cloud Connected Deployment Guide to deploy the HoloLens 2 externally.

  • Azure AD Join with MDM Auto Enrollment—MDM-managed (Intune)
  • Users sign in with their own corporate account (Azure AD)
    • Single or multiple users per device are supported.

Remote Assist licensing and requirements

See Learn more about Remote Assist.

Dynamics 365 Remote Assist user

  • Remote Assist license
  • Network Connectivity

Microsoft Teams user

General deployment recommendations

We recommend the following steps for external HoloLens 2 deployment:

  1. Use the latest HoloLens OS release as your baseline build.

  2. Assign user-based or device-based licenses by following the steps below:

    1. Create a group in AAD and add members for HoloLens/RA users.
    2. Assign device-based or user-based licenses to this group.
    3. (Optional) Target groups for Mobile device management (MDM) policies.
  3. Join AAD devices to your tenant, auto enroll, and configure through Autopilot. For more information, see device owner.

    1. The first user on the device will be the device owner.
    2. If the device is AAD joined, the user that performed the join is made device owner.
  4. Tenant lock the device so that it can only be joined by your tenant.

    1. See also Tenant lock CSP.
  5. Configure Kiosk mode using global assigned access.

  6. Disable the following (optional) capabilities:

    1. Ability to put the device into developer mode here.
    2. Ability to connect the HoloLens to a PC to copy date disable USB.


      If you don’t want to disable USB but want the ability to apply a provisioning package to the device using USB, follow the instructions on how to allow provisioning package installation.

  7. Use Windows Defender Application Control (WDAC) to allow or block apps on the HoloLens 2 device.

  8. Update Remote Assist to the latest version as part of the setup. Consider the following two options:

    1. Go to Windows Microsoft Store --> Remote Assist --> and Update App.
    2. ApplicationManagement/AllowAppStoreAutoUpdate - which allows automatic app updates - is enabled by default. Keep the device plugged in to receive updates.
  9. Disable all settings pages except the network settings to allow users to connect to guest networks at client sites.

  10. Manage HoloLens updates

    1. Option to control OS updates or allow to flow freely.
  11. Set common device restrictions.

Now your external clients are ready to use their HoloLens 2.

Common external client deployment concerns

Ensure that external clients can't communicate with one another

Remote Assist HoloLens to HoloLens calls aren't supported. Clients can search for, but can't communicate with each other. Information barriers in Microsoft 365 can further restrict with whom a client can search and call. Another option is to use Microsoft Teams scoped directory search.


Since single sign on is enabled, it is important to disable the browser using Windows Defender Application Control (WDAC). If an external client opens the browser and uses the web version of Teams, the client will have access to your chat history.

Ensure that clients won't have access to company resources

There are two options to consider.

The first option is a multi-layer approach:

  1. Only assign licenses that the user requires. If you don't assign OneDrive, Outlook, SharePoint, Yammer, etc., the user will not have access to those resources. The only licenses the users will need is Remote Assist, Intune, and AAD licenses to begin.
  2. Block apps (such as email) that you don’t want clients to access (See [Apps are hidden or restricted](#apps are hidden or restricted)).
  3. Don't share usernames nor password with clients. To log into the HoloLens 2, an email and numerical PIN is required.

The second option is to create a separate tenant that hosts clients (see Image 1.1).

Image 1.1

Service Tenant Image.

Hidden or restricted apps

Kiosk mode and/or Windows Defender Application Control (WDAC) are options for hiding and/or restricting applications.

Password management for your clients

  1. Remove password expiration. However, this option may increase the chance that an account will be compromised. NIST password recommendation is change passwords every 30-90 days.
  2. Extend the password expiration for HoloLens 2 devices to exceed 90 days.
  3. The devices should be returned to your organization to change the passwords. However, this option can cause issues if the devices are expected to be in the client's plant for 90+ days.
  4. For devices that are sent to multiple clients, reset passwords before shipping the device to clients.

Ensure that clients won't have access to chat history

Remote Assist clears chat history after each session. However, chat history will be available for Microsoft Teams users.


Since single sign on is enabled, it is important to disable the browser using Windows Defender Application Control (WDAC). If a external client opens the browser and uses the web version of Teams, the client will have access to call/chat history.