From 544f7a4d82ee642db53590420d7ffdc1ca8b97e3 Mon Sep 17 00:00:00 2001 From: Paolo Matarazzo <74918781+paolomatarazzo@users.noreply.github.com> Date: Tue, 20 Sep 2022 11:45:09 -0400 Subject: [PATCH] updates --- .../hello-hybrid-cloud-kerberos-trust.md | 34 +++++++++---------- .../security/images}/icons/accessibility.svg | 0 .../security/images}/icons/group-policy.svg | 0 .../security/images}/icons/intune.svg | 0 .../security/images}/icons/powershell.svg | 0 .../images}/icons/provisioning-package.svg | 0 .../security/images}/icons/registry.svg | 0 .../security/images}/icons/windows-os.svg | 0 8 files changed, 17 insertions(+), 17 deletions(-) rename {images => windows/security/images}/icons/accessibility.svg (100%) rename {images => windows/security/images}/icons/group-policy.svg (100%) rename {images => windows/security/images}/icons/intune.svg (100%) rename {images => windows/security/images}/icons/powershell.svg (100%) rename {images => windows/security/images}/icons/provisioning-package.svg (100%) rename {images => windows/security/images}/icons/registry.svg (100%) rename {images => windows/security/images}/icons/windows-os.svg (100%) diff --git a/windows/security/identity-protection/hello-for-business/hello-hybrid-cloud-kerberos-trust.md b/windows/security/identity-protection/hello-for-business/hello-hybrid-cloud-kerberos-trust.md index b8c20ad0f1..c20f96039f 100644 --- a/windows/security/identity-protection/hello-for-business/hello-hybrid-cloud-kerberos-trust.md +++ b/windows/security/identity-protection/hello-for-business/hello-hybrid-cloud-kerberos-trust.md @@ -87,7 +87,7 @@ If you haven't deployed Azure AD Kerberos, follow the instructions in the [Enabl After setting up the Azure AD Kerberos Object, Windows Hello for business cloud Kerberos trust must be enabled on your Windows devices. Follow the instructions below to configure your devices using either Microsoft Intune or group policy (GPO). -#### [:::image type="icon" source="../../../../images/icons/intune.svg"::: **Intune**](#tab/intune) +#### [:::image type="icon" source="../../images/icons/intune.svg"::: **Intune**](#tab/intune) Windows Hello for Business can be enabled using device enrollment or device configuration policy. Device enrollment policy is only applied at device enrollment time. Any modifications to the configuration in Intune won't apply to already enrolled devices. Device configuration policy is applied after device enrollment. Changes to this policy type in Intune are applied to already enrolled devices. @@ -97,15 +97,15 @@ The cloud Kerberos trust policy needs to be configured using a custom template a If you have an existing group you want to target with Windows Hello for Business cloud Kerberos trust policy, you can skip this step. -1. Sign in to the [Microsoft Endpoint Manager admin center](https://endpoint.microsoft.com/). -1. Browse to **Groups** and select **New group**. +1. Sign in to the [Microsoft Endpoint Manager admin center](https://endpoint.microsoft.com/) +1. Browse to **Groups** and select **New group** 1. Configure the following group settings: - 1. Group type: "Security" - 1. Group name: "WHFBCloudTrustUsers" or a group name of your choosing - 1. Membership type: Assigned -1. Select **Members** and add users that you want to target with Windows Hello for Business cloud Kerberos trust. + 1. Group type: **Security** + 1. Group name: *WHFB cloud Kerberos trust users* or a group name of your choosing + 1. Membership type: **Assigned** +1. Select **Members** and add users that you want to target with Windows Hello for Business cloud Kerberos trust -You can also create a group through the Azure portal instead of using the Microsoft Endpoint Manager admin center. +You can also create a group through the Azure portal instead of using the Microsoft Endpoint Manager admin center ### Enable Windows Hello for Business @@ -125,7 +125,7 @@ You can also follow these steps to create a device configuration policy instead 1. Select Next to move to **Assignments**. 1. Under Included groups, select **Add groups**. -1. Select the user group you would like to use Windows Hello for Business cloud Kerberos trust. This group may be WHFBCloudTrustUsers or a group of your choosing. +1. Select the user group you would like to use Windows Hello for Business cloud Kerberos trust. This group may be *WHFB cloud Kerberos trust users* or a group of your choosing. 1. Select Next to move to the Applicability Rules. 1. Select Next again to move to the **Review + create** tab and select the option to create the policy. @@ -142,25 +142,25 @@ To configure the cloud Kerberos trust policy, follow the steps below: 1. Name the profile with a familiar name. For example, "Windows Hello for Business cloud Kerberos trust". 1. In Configuration Settings, add a new configuration with the following settings: -| Setting | -|--------| -|
  • Name: **Windows Hello for Business cloud Kerberos trust** or another familiar name
  • Description (optional): *Enable Windows Hello for Business cloud Kerberos trust for sign-in and on-premises SSO*
  • OMA-URI: **`./Device/Vendor/MSFT/PassportForWork/`**`/Policies/UseCloudTrustForOnPremAuth`**
  • Data type: **Boolean**
  • Value: **True**
    • | + | Setting | + |--------| + |
  • Name: **Windows Hello for Business cloud Kerberos trust** or another familiar name
  • Description (optional): *Enable Windows Hello for Business cloud Kerberos trust for sign-in and on-premises SSO*
  • OMA-URI: **`./Device/Vendor/MSFT/PassportForWork/`**`/Policies/UseCloudTrustForOnPremAuth`**
  • Data type: **Boolean**
  • Value: **True**
    • | ->[!IMPORTANT] ->*Tenant ID* in the OMA-URI must be replaced with the tenant ID for your Azure AD tenant. See [How to find your Azure AD tenant ID](/azure/active-directory/fundamentals/active-directory-how-to-find-tenant) for instructions on looking up your tenant ID. + >[!IMPORTANT] + >*Tenant ID* in the OMA-URI must be replaced with the tenant ID for your Azure AD tenant. See [How to find your Azure AD tenant ID](/azure/active-directory/fundamentals/active-directory-how-to-find-tenant) for instructions on looking up your tenant ID. - [![Intune custom-device configuration policy creation](./images/hello-cloud-trust-intune.png)](./images/hello-cloud-trust-intune-large.png#lightbox) + [![Intune custom-device configuration policy creation](./images/hello-cloud-trust-intune.png)](./images/hello-cloud-trust-intune-large.png#lightbox) 1. Select Next to navigate to **Assignments**. 1. Under Included groups, select **Add groups**. -1. Select the user group you would like to use Windows Hello for Business cloud Kerberos trust. This group may be WHFBCloudTrustUsers or a group of your choosing. +1. Select the user group you would like to use Windows Hello for Business cloud Kerberos trust. This group may be *WHFB cloud Kerberos trust users* or a group of your choosing. 1. Select Next to move to the Applicability Rules. 1. Select Next again to move to the **Review + create** tab and select the option to create the policy. > [!Important] > If the Use certificate for on-premises authentication policy is enabled, we will enforce certificate trust instead of cloud Kerberos trust on the client. Please make sure that any machines that you want to use Windows Hello for Business cloud Kerberos trust have this policy not configured or disabled. -#### [:::image type="icon" source="../../../../images/icons/group-policy.svg"::: **GPO**](#tab/gpo) +#### [:::image type="icon" source="=../../images/icons/group-policy.svg"::: **GPO**](#tab/gpo) Hybrid Azure AD joined organizations can use Windows Hello for Business Group Policy to manage the feature. Group Policy can be configured to enable users to enroll and use Windows Hello for Business. diff --git a/images/icons/accessibility.svg b/windows/security/images/icons/accessibility.svg similarity index 100% rename from images/icons/accessibility.svg rename to windows/security/images/icons/accessibility.svg diff --git a/images/icons/group-policy.svg b/windows/security/images/icons/group-policy.svg similarity index 100% rename from images/icons/group-policy.svg rename to windows/security/images/icons/group-policy.svg diff --git a/images/icons/intune.svg b/windows/security/images/icons/intune.svg similarity index 100% rename from images/icons/intune.svg rename to windows/security/images/icons/intune.svg diff --git a/images/icons/powershell.svg b/windows/security/images/icons/powershell.svg similarity index 100% rename from images/icons/powershell.svg rename to windows/security/images/icons/powershell.svg diff --git a/images/icons/provisioning-package.svg b/windows/security/images/icons/provisioning-package.svg similarity index 100% rename from images/icons/provisioning-package.svg rename to windows/security/images/icons/provisioning-package.svg diff --git a/images/icons/registry.svg b/windows/security/images/icons/registry.svg similarity index 100% rename from images/icons/registry.svg rename to windows/security/images/icons/registry.svg diff --git a/images/icons/windows-os.svg b/windows/security/images/icons/windows-os.svg similarity index 100% rename from images/icons/windows-os.svg rename to windows/security/images/icons/windows-os.svg