Deployment Guide - Corporate Connected HoloLens 2 with Dynamics 365 Guides - Overview

This guide will help IT professionals plan for and deploy Microsoft HoloLens 2 devices with Dynamics 365 Guides (Guides) to their organization. This guide is great for pilots as well as production deployments and is similar to the Scenario B: Deploy inside your organization's network guide. After testing your proof-of-concept, use this guide to move forward with integrating HoloLens into your organization.

In this guide, we will cover how to enroll your devices into your existing device management, apply licenses as needed, and validate that your end users are able to operate a Dynamics 365 Guide, as well as use custom line of business apps, after device set up.


The following infrastructure should already be in place:

  • Wi-Fi
    • Internal corporate network with access to internal resources and limited access to the internet or Cloud services
    • Device-based certificate authentication.
  • Azure Active Directory (Azure AD) Join with MDM Auto Enrollment (Azure AD P1 subscription needed)
  • MDM (Intune) Managed
    • One or more applications are deployed via MDM.
  • Network
    • Certificates (SCEP or PKCS)
    • Proxy configuration
  • Users sign in with their own corporate account (Azure AD)
    • Single or multiple users per device is supported.
  • Varying levels of device lockdown configurations applied based on specific use cases, from Fully Open to Single App Kiosk.

Guides Licensing and Requirements

  • Azure AD account
  • Dynamics 365 Guides applications PC and HoloLens
  • Dynamics 365 Guides subscription
    • Microsoft Dataverse (included)
    • Power Apps (included)
  • Power BI Desktop
  • Network Connectivity

Corp connected network diagram, stage 1.

Corp connected network diagram, stage 2.

In this guide you will:





Next step