From e129e6c72269c3d7fe0a70e70eb6d2d1fc328468 Mon Sep 17 00:00:00 2001 From: Paolo Matarazzo <74918781+paolomatarazzo@users.noreply.github.com> Date: Mon, 12 Feb 2024 18:30:11 +0100 Subject: [PATCH] Update Windows Hello for Business configuration documentation --- .../identity-protection/hello-for-business/configure.md | 9 ++------- 1 file changed, 2 insertions(+), 7 deletions(-) diff --git a/windows/security/identity-protection/hello-for-business/configure.md b/windows/security/identity-protection/hello-for-business/configure.md index 625c55a872..ba9a89f070 100644 --- a/windows/security/identity-protection/hello-for-business/configure.md +++ b/windows/security/identity-protection/hello-for-business/configure.md @@ -29,14 +29,9 @@ Some of the Windows Hello for Business policies are available for both computer - Exchange Active Sync (DeviceLock CSP) >[!IMPORTANT] ->All devices only have one PIN associated with Windows Hello for Business. This means that any PIN on a device will be subject to the policies specified in the PassportForWork CSP. The values specified take precedence over any complexity rules set via Exchange ActiveSync (EAS) or the DeviceLock CSP. - - +>The DeviceLock CSP utilizes the Exchange ActiveSync Policy (EAS) engine. For more information, see [Exchange ActiveSync Policy Engine Overview](/previous-versions/windows/it-pro/windows-server-2012-r2-and-2012/dn282287(v=ws.11)). >[!NOTE] > If a policy isn't explicitly configured to require letters or special characters, users can optionally set an alphanumeric PIN.