From b31b11e6de416527f18774cb5a259f4a135a11ed Mon Sep 17 00:00:00 2001 From: Paolo Matarazzo <74918781+paolomatarazzo@users.noreply.github.com> Date: Fri, 3 May 2024 11:49:07 -0400 Subject: [PATCH] update --- .../security/book/identity-protection-passwordless-sign-in.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/security/book/identity-protection-passwordless-sign-in.md b/windows/security/book/identity-protection-passwordless-sign-in.md index 3c132e2ed7..44ccdb7147 100644 --- a/windows/security/book/identity-protection-passwordless-sign-in.md +++ b/windows/security/book/identity-protection-passwordless-sign-in.md @@ -40,7 +40,7 @@ During a device's lifecycle, a password may only need to be used once during the Provisioning methods include: - Temporary Access Pass (TAP), a time-limited passcode with strong authentication requirements issued through Microsoft Entra ID -- Existing multifactor authentication with Microsoft Entra ID[\[9\]](conclusion.md#footnote9), including authentication methods like the Microsoft Authenticator app +- Existing multifactor authentication with Microsoft Entra ID, including authentication methods like the Microsoft Authenticator app Windows Hello for Business replaces the username and password by combining a security key or certificate with a PIN or biometric data and then mapping the credentials to a user account during setup. There are multiple ways to deploy Windows Hello for Business depending on an organization's needs. Organizations that rely on certificates typically use on-premises public key infrastructure (PKI) to support authentication through Certificate Trust. Organizations using key trust deployment require root-of-trust provided by certificates on domain controllers.