From ae0f81829df0db1f37b7bfa90fdc19854b902c4c Mon Sep 17 00:00:00 2001 From: Paolo Matarazzo <74918781+paolomatarazzo@users.noreply.github.com> Date: Tue, 5 Nov 2024 07:14:56 -0500 Subject: [PATCH 1/2] fixed table --- .../identity-protection/hello-for-business/configure.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/windows/security/identity-protection/hello-for-business/configure.md b/windows/security/identity-protection/hello-for-business/configure.md index 901fa618d2..4d59656ecb 100644 --- a/windows/security/identity-protection/hello-for-business/configure.md +++ b/windows/security/identity-protection/hello-for-business/configure.md @@ -2,7 +2,7 @@ title: Configure Windows Hello for Business description: Learn about the configuration options for Windows Hello for Business and how to implement them in your organization. ms.topic: how-to -ms.date: 04/23/2024 +ms.date: 11/05/2024 --- # Configure Windows Hello for Business @@ -109,7 +109,7 @@ Configuration type| Details | | CSP (user)|**Key path**: `HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Policies\PassportForWork\\UserSid\Policies`
**Key name**: `UsePassportForWork`
**Type**: `REG_DWORD`
**Value**:
 `1` to enable
 `0` to disable | | CSP (device)|**Key path**: `HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Policies\PassportForWork\\Device\Policies`
**Key name**: `UsePassportForWork`
**Type**: `REG_DWORD`
**Value**:
 `1` to enable
 `0` to disable | | GPO (user)|**Key path**: `HKEY_USERS\\SOFTWARE\Policies\Microsoft\PassportForWork`
**Key name**: `Enabled`
**Type**: `REG_DWORD`
**Value**:
 `1` to enable
 `0` to disable | -| GPO (user)|**Key path**: `KEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\PassportForWork`
**Key name**: `Enabled`
**Type**: `REG_DWORD`
**Value**:
 `1` to enable
 `0` to disable | +| GPO (device)|**Key path**: `KEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\PassportForWork`
**Key name**: `Enabled`
**Type**: `REG_DWORD`
**Value**:
 `1` to enable
 `0` to disable | > [!NOTE] > If there's a conflicting device policy and user policy, the user policy takes precedence. It's not recommended to create Local GPO or registry settings that could conflict with an MDM policy. This conflict could lead to unexpected results. From 606cf781048cd3f1fb8041ce2fdf1f9bd7184795 Mon Sep 17 00:00:00 2001 From: Padma Jayaraman Date: Tue, 5 Nov 2024 19:03:14 +0530 Subject: [PATCH 2/2] pencil edit --- .../identity-protection/hello-for-business/configure.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/security/identity-protection/hello-for-business/configure.md b/windows/security/identity-protection/hello-for-business/configure.md index 4d59656ecb..29cb37b8e0 100644 --- a/windows/security/identity-protection/hello-for-business/configure.md +++ b/windows/security/identity-protection/hello-for-business/configure.md @@ -83,7 +83,7 @@ To check the Windows Hello for Business policy settings applied at enrollment ti 1. Select **Windows Hello for Business** 1. Verify the status of **Configure Windows Hello for Business** and any settings that might be configured -:::image type="content" source="deploy/images/whfb-intune-disable.png" alt-text="Disablement of Windows Hello for Business from Microsoft Intune admin center." lightbox="deploy/images/whfb-intune-disable.png"::: + :::image type="content" source="deploy/images/whfb-intune-disable.png" alt-text="Disablement of Windows Hello for Business from Microsoft Intune admin center." lightbox="deploy/images/whfb-intune-disable.png"::: ## Policy conflicts from multiple policy sources