From ffee722399bf31d923bc1a965e6fdab59269b715 Mon Sep 17 00:00:00 2001 From: Corey McClain Date: Fri, 6 Mar 2020 10:30:25 -0500 Subject: [PATCH] Update feature-multifactor-unlock.md Updated Requirements section to be more clear that the device deployment options were 'or' rather than 'and'. --- .../hello-for-business/feature-multifactor-unlock.md | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/windows/security/identity-protection/hello-for-business/feature-multifactor-unlock.md b/windows/security/identity-protection/hello-for-business/feature-multifactor-unlock.md index 4ddcb35964..a3a94da88d 100644 --- a/windows/security/identity-protection/hello-for-business/feature-multifactor-unlock.md +++ b/windows/security/identity-protection/hello-for-business/feature-multifactor-unlock.md @@ -23,10 +23,8 @@ ms.reviewer: **Requirements:** * Windows Hello for Business deployment (Hybrid or On-premises) -* Azure AD joined device (Cloud and Hybrid deployments) -* Hybrid Azure AD joined (Hybrid deployments) -* Domain Joined (on-premises deployments) -* Windows 10, version 1709 +* Azure AD, Hybrid Azure AD, or Domain Joined (Cloud, Hybrid, or On-Premises deployments) +* Windows 10, version 1709 or newer * Bluetooth, Bluetooth capable phone - optional Windows, today, natively only supports the use of a single credential (password, PIN, fingerprint, face, etc.) for unlocking a device. Therefore, if any of those credentials are compromised (shoulder surfed), an attacker could gain access to the system.