From b7372caea40c7c63bc88606e65d45e41de620bc0 Mon Sep 17 00:00:00 2001 From: Payge Winfield Date: Fri, 28 Feb 2020 06:59:44 -0800 Subject: [PATCH 1/4] Changed App section --- devices/hololens/hololens-requirements.md | 12 +++++++----- 1 file changed, 7 insertions(+), 5 deletions(-) diff --git a/devices/hololens/hololens-requirements.md b/devices/hololens/hololens-requirements.md index 6c370939da..2a219c7555 100644 --- a/devices/hololens/hololens-requirements.md +++ b/devices/hololens/hololens-requirements.md @@ -33,7 +33,7 @@ This document also assumes that the HoloLens has been evaluated by security team Before deploying the HoloLens in your environment, it is important to first determine what features, apps, and type of identities are needed. It is also important to ensure that your security team has approved of the use of the HoloLens on the company's network. Please see [Frequently ask security questions](hololens-faq-security.md) for additional security information. -### Type of identity +### Type of Identity Determine the type of identity that will be used to sign into the device. @@ -66,13 +66,15 @@ There are two types of Kiosk Modes: Single app and multi-app. Single app kiosk m There are two main ways ([provisioning packages](hololens-kiosk.md#set-up-kiosk-mode-using-a-provisioning-package-windows-10-version-1803) and [MDM](hololens-kiosk.md#set-up-kiosk-mode-using-microsoft-intune-or-mdm-windows-10-version-1803)) to deploy kiosk mode for HoloLens. These options will be discussed later in the document; however, you can use the links above to jump to the respective sections in this doc. -### Apps +### Apps and App Specific Scenarios The majority of the steps found in this document will also apply to the following apps: -1. Remote Assist -2. Guides -3. Customer Apps +| App | App Specific Scenarios | +| --- | --- | +| Remote Assist | [Cross Tenant Communication]()| +| Guides | *Coming Soon* | +|Custom Apps | | ### Determine your enrollment method From d2cc08f41ba2f9a9a18ebc2db11e190fed496af5 Mon Sep 17 00:00:00 2001 From: pawinfie <59937840+pawinfie@users.noreply.github.com> Date: Mon, 9 Mar 2020 10:28:30 -0700 Subject: [PATCH 2/4] added likes to RA docs --- devices/hololens/hololens-licenses-requirements.md | 4 +++- devices/hololens/hololens-requirements.md | 6 ++++-- 2 files changed, 7 insertions(+), 3 deletions(-) diff --git a/devices/hololens/hololens-licenses-requirements.md b/devices/hololens/hololens-licenses-requirements.md index c89587c100..7b843d3280 100644 --- a/devices/hololens/hololens-licenses-requirements.md +++ b/devices/hololens/hololens-licenses-requirements.md @@ -23,7 +23,7 @@ appliesto: If you plan on managing your HoloLens devices, you will need Azure AD and an MDM. Active Director (AD) cannot be used to manage HoloLens devices. If you plan on using an MDM other than Intune, an [Azure Active Directory Licenses](https://docs.microsoft.com/azure/active-directory/fundamentals/active-directory-whatis) is required. -If you plan on using Intune as your MDM, you can acquire an [Enterprise Mobility + Security (EMS) suite (E3 or E5) licenses](https://www.microsoft.com/microsoft-365/enterprise-mobility-security/compare-plans-and-pricing). **Please note that Azure AD is included in both suites.** +If you plan on using Intune as your MDM, [here](https://docs.microsoft.com/intune/fundamentals/licenses) are a list of suites that includes Intune licenses. **Please note that Azure AD is included in the majority of these suites.** ## Identify the licenses needed for your scenario and products @@ -44,6 +44,8 @@ Make sure you have the required licensing and device. Updated licensing and prod 1. [Teams Freemium/Teams](https://products.office.com/microsoft-teams/free) 1. [Azure Active Directory (Azure AD) License](https://docs.microsoft.com/azure/active-directory/fundamentals/active-directory-whatis) +If you plan on implementing a cross-tenant communication scenario, you may need an [Information Barrier license](https://docs.microsoft.com/microsoft-365/compliance/information-barriers?view=o365-worldwide#required-licenses-and-permissions). Please visit the [Cross Tenant Communication Overview](https://docs.microsoft.com/dynamics365/mixed-reality/remote-assist/cross-tenant-licensing-implementation#step-1-determine-if-information-barriers-are-necessary) article to determine if an Information Barrier License is required for your scenario. + ### Guides License Requirements Updated licensing and device requirements can be found [here](https://docs.microsoft.com/dynamics365/mixed-reality/guides/requirements). diff --git a/devices/hololens/hololens-requirements.md b/devices/hololens/hololens-requirements.md index 2a219c7555..86dc598515 100644 --- a/devices/hololens/hololens-requirements.md +++ b/devices/hololens/hololens-requirements.md @@ -41,6 +41,8 @@ Determine the type of identity that will be used to sign into the device. 2. **MSA:** This is a personal account (like outlook, hotmail, gmail, yahoo, etc.) This will allow only 1 user to log into the device. 3. **Azure Active Directory (Azure AD) accounts:** This is an account created in Azure AD. This grants your corporation the ability to manage the HoloLens device. This will allow multiple users to log into the HoloLens 1st Gen Commercial Suite/the HoloLens 2 device. +For more detailed information about identity types, please visit our [HoloLens Identity](#hololens-identity.md) article. + ### Type of Features Your feature requirements will determine which HoloLens you need. One popular feature that we see deployed in customer environments frequently is Kiosk Mode. A list of HoloLens key features, and the editions of HoloLens that support them, can be found [here](hololens-commercial-features.md). @@ -72,9 +74,9 @@ The majority of the steps found in this document will also apply to the followin | App | App Specific Scenarios | | --- | --- | -| Remote Assist | [Cross Tenant Communication]()| +| Remote Assist | [Cross Tenant Communication](https://docs.microsoft.com/dynamics365/mixed-reality/remote-assist/cross-tenant-overview)| | Guides | *Coming Soon* | -|Custom Apps | | +|Custom Apps | *Coming Soon* | ### Determine your enrollment method From 8890c8a641588668ecc0b6673b112249826f5bfb Mon Sep 17 00:00:00 2001 From: pawinfie <59937840+pawinfie@users.noreply.github.com> Date: Mon, 9 Mar 2020 10:34:37 -0700 Subject: [PATCH 3/4] link to RA info barrier article --- devices/hololens/hololens-licenses-requirements.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/devices/hololens/hololens-licenses-requirements.md b/devices/hololens/hololens-licenses-requirements.md index 7b843d3280..ef727bfc77 100644 --- a/devices/hololens/hololens-licenses-requirements.md +++ b/devices/hololens/hololens-licenses-requirements.md @@ -44,7 +44,7 @@ Make sure you have the required licensing and device. Updated licensing and prod 1. [Teams Freemium/Teams](https://products.office.com/microsoft-teams/free) 1. [Azure Active Directory (Azure AD) License](https://docs.microsoft.com/azure/active-directory/fundamentals/active-directory-whatis) -If you plan on implementing a cross-tenant communication scenario, you may need an [Information Barrier license](https://docs.microsoft.com/microsoft-365/compliance/information-barriers?view=o365-worldwide#required-licenses-and-permissions). Please visit the [Cross Tenant Communication Overview](https://docs.microsoft.com/dynamics365/mixed-reality/remote-assist/cross-tenant-licensing-implementation#step-1-determine-if-information-barriers-are-necessary) article to determine if an Information Barrier License is required for your scenario. +If you plan on implementing **[this cross-tenant scenario](https://docs.microsoft.com/dynamics365/mixed-reality/remote-assist/cross-tenant-overview#scenario-2-leasing-services-to-other-tenants)**, you may need an Information Barriers license. Please see [this article](https://docs.microsoft.com/dynamics365/mixed-reality/remote-assist/cross-tenant-licensing-implementation#step-1-determine-if-information-barriers-are-necessary) to determine if an Information Barrier License is required. ### Guides License Requirements From 8b212f1226255a61f396e034e8f7db26e47a894f Mon Sep 17 00:00:00 2001 From: pawinfie <59937840+pawinfie@users.noreply.github.com> Date: Mon, 9 Mar 2020 10:48:34 -0700 Subject: [PATCH 4/4] fixed hololens identity link --- devices/hololens/hololens-requirements.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/devices/hololens/hololens-requirements.md b/devices/hololens/hololens-requirements.md index 86dc598515..6cfcb281b0 100644 --- a/devices/hololens/hololens-requirements.md +++ b/devices/hololens/hololens-requirements.md @@ -41,7 +41,7 @@ Determine the type of identity that will be used to sign into the device. 2. **MSA:** This is a personal account (like outlook, hotmail, gmail, yahoo, etc.) This will allow only 1 user to log into the device. 3. **Azure Active Directory (Azure AD) accounts:** This is an account created in Azure AD. This grants your corporation the ability to manage the HoloLens device. This will allow multiple users to log into the HoloLens 1st Gen Commercial Suite/the HoloLens 2 device. -For more detailed information about identity types, please visit our [HoloLens Identity](#hololens-identity.md) article. +For more detailed information about identity types, please visit our [HoloLens Identity](hololens-identity.md) article. ### Type of Features