From 1d19f98f7fefcc326e4f74b0870d1045dd804f9d Mon Sep 17 00:00:00 2001 From: Paolo Matarazzo <74918781+paolomatarazzo@users.noreply.github.com> Date: Thu, 31 Oct 2024 07:40:32 -0400 Subject: [PATCH] updates --- .../deploy/hybrid-cloud-kerberos-trust.md | 2 +- .../identity-protection/hello-for-business/deploy/index.md | 6 +++--- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/windows/security/identity-protection/hello-for-business/deploy/hybrid-cloud-kerberos-trust.md b/windows/security/identity-protection/hello-for-business/deploy/hybrid-cloud-kerberos-trust.md index c547b535eb..6a73849697 100644 --- a/windows/security/identity-protection/hello-for-business/deploy/hybrid-cloud-kerberos-trust.md +++ b/windows/security/identity-protection/hello-for-business/deploy/hybrid-cloud-kerberos-trust.md @@ -41,7 +41,7 @@ If you haven't deployed Microsoft Entra Kerberos, follow the instructions in the When Microsoft Entra Kerberos is enabled in an Active Directory domain, an *AzureADKerberos* computer object is created in the domain. This object: -- Appears as a Read Only Domain Controller (RODC) object, but isn't associated with any physical servers +- Appears as a read only domain controller (RODC) object, but isn't associated with any physical servers - Is only used by Microsoft Entra ID to generate TGTs for the Active Directory domain > [!NOTE] diff --git a/windows/security/identity-protection/hello-for-business/deploy/index.md b/windows/security/identity-protection/hello-for-business/deploy/index.md index 10823c86c1..fb262a5ee4 100644 --- a/windows/security/identity-protection/hello-for-business/deploy/index.md +++ b/windows/security/identity-protection/hello-for-business/deploy/index.md @@ -65,7 +65,7 @@ Windows Hello for Business authentication to Microsoft Entra ID always uses the The trust type determines whether you issue authentication certificates to your users. One trust model isn't more secure than the other. -The deployment of certificates to users and Domain Controllers requires more configuration and infrastructure, which could also be a factor to consider in your decision. More infrastructure needed for certificate-trust deployments includes a certificate registration authority. In a federated environment, you must activate the Device Writeback option in Microsoft Entra Connect. +The deployment of certificates to users and domain controllers requires more configuration and infrastructure, which could also be a factor to consider in your decision. More infrastructure needed for certificate-trust deployments includes a certificate registration authority. In a federated environment, you must activate the Device Writeback option in Microsoft Entra Connect. There are three trust types from which you can choose: @@ -264,9 +264,9 @@ All supported Windows versions can be used with Windows Hello for Business. Howe ### Windows Server requirements -All supported Windows Server versions can be used with Windows Hello for Business as Domain Controller. However, cloud Kerberos trust requires minimum versions: +Windows Hello for Business can be used to authenticate against all supported Windows Server versions as a domain controller. However, cloud Kerberos trust requires minimum versions: -| | Deployment model | Trust type | Domain Controller OS version | +| | Deployment model | Trust type | Domain controller OS version | |--|--|--|--| | **🔲** | **Cloud-only** | n/a | All supported versions | | **🔲** | **Hybrid** | Cloud Kerberos | - Windows Server 2016, with [KB3534307][KB-3] and later
- Windows Server 2019, with [KB4534321][KB-4] and later
- Windows Server 2022
- Windows Server 2025|