The use of HL2 with the Dynamics RA license added to our tenant, for internal users, is straightforward. However, for example, if we want to send two units, one to Customer 1, and one to Customer 2, we don’t want to allow Customer 1 to contact Customer 2, via HoloLens (technically, via Teams), or contact\interact with anyone else outside of our support group. That falls under scenario 2 from this article https://docs.microsoft.com/en-us/dynamics365/mixed-reality/remote-assist/vendor-use-ra . In that case, it looks like we’d also need to buy an “Office 365 E5” license for each customer, to be able to use the information barrier license that comes with it. Do you have any experience with that scenario? Is there a better, more cost effective way of doing this?”
- Considering that we manage our AD env. on-site, and just sync with Azure, is it OK to use our tenant to manage HL2 devices for the above scenario? Should we consider creating a separate tenant for the use case mentioned above?
- What exact licenses would I need, besides Dynamics RA, to be able to manage the HLs devices, and separate the user accounts assigned to customers?

Report
All responses (
Answers (