mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-18 20:03:40 +00:00
Merge pull request #6363 from joinimran/patch-68
Point to correct resource
This commit is contained in:
@ -102,8 +102,8 @@ Organizations using older directory synchronization technology, such as DirSync
|
|||||||
<br>
|
<br>
|
||||||
|
|
||||||
|
|
||||||
## Federation with Azure ##
|
## Federation with Azure
|
||||||
You can deploy Windows Hello for Business key trust in non-federated and federated environments. For non-federated environments, key trust deployments work in environments that have deployed [Password Synchronization with Azure AD Connect](https://docs.microsoft.com/azure/active-directory/connect/active-directory-aadconnectsync-implement-password-synchronization) or [Azure Active Directory Pass-through-Authentication](https://docs.microsoft.com/azure/active-directory/connect/active-directory-aadconnect-pass-through-authentication). For federated environments, you can deploy Windows Hello for Business key trust using Active Directory Federation Services (AD FS) 2012 R2 or later.
|
You can deploy Windows Hello for Business key trust in non-federated and federated environments. For non-federated environments, key trust deployments work in environments that have deployed [Password Synchronization with Azure AD Connect](https://docs.microsoft.com/azure/active-directory/hybrid/whatis-phs) or [Azure Active Directory Pass-through-Authentication](https://docs.microsoft.com/azure/active-directory/connect/active-directory-aadconnect-pass-through-authentication). For federated environments, you can deploy Windows Hello for Business key trust using Active Directory Federation Services (AD FS) 2012 R2 or later.
|
||||||
|
|
||||||
> [!div class="checklist"]
|
> [!div class="checklist"]
|
||||||
> * Non-federated environments
|
> * Non-federated environments
|
||||||
|
Reference in New Issue
Block a user