From 534cfaa98e59ceb8e174e5103011503265bcc44d Mon Sep 17 00:00:00 2001
From: Jake Stoker <94176328+JASTOKER@users.noreply.github.com>
Date: Wed, 21 Sep 2022 15:22:59 +0100
Subject: [PATCH] adding additional scenario for line of sight

HAADJ devices also require line of sight to access on-premises resources. This is only called out for AADJ devices in the FAQ.
---
 .../hello-for-business/hello-hybrid-cloud-kerberos-trust.md     | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

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 da2c3ed436..3a879cfdd0 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
@@ -253,7 +253,7 @@ Windows Hello for Business cloud Kerberos trust looks for a writeable DC to exch
 ### Do I need line of sight to a domain controller to use Windows Hello for Business cloud Kerberos trust?
 
 Windows Hello for Business cloud Kerberos trust requires line of sight to a domain controller for some scenarios:
-- The first sign-in or unlock with Windows Hello for Business after provisioning on a Hybrid Azure AD joined device
+- The first sign-in or unlock with Windows Hello for Business after provisioning and when attempting to access an on-premises resource on a Hybrid Azure AD joined device
 - When attempting to access an on-premises resource from an Azure AD joined device
 
 ### Can I use RDP/VDI with Windows Hello for Business cloud Kerberos trust?