Skip to content

Commit 2864c57

Browse files
committed
[AzureADDS] Incorporating PM feedback
1 parent 287e6ce commit 2864c57

File tree

1 file changed

+7
-2
lines changed

1 file changed

+7
-2
lines changed

articles/active-directory/hybrid/how-to-connect-password-hash-synchronization.md

Lines changed: 7 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -99,13 +99,18 @@ The synchronization of a password has no impact on the Azure user who is signed
9999

100100
## Password hash sync process for Azure AD Domain Services
101101

102-
If you use Azure AD Domain Services to provide authentication for applications and services, some additional processes are part of the password hash synchronization flow. Azure AD Connect uses the additional following process to synchronize password hashes to Azure AD for use in Azure AD Domain Services:
102+
If you use Azure AD Domain Services to provide legacy authentication for applications and services that need to use Keberos, LDAP, or NTLM, some additional processes are part of the password hash synchronization flow. Azure AD Connect uses the additional following process to synchronize password hashes to Azure AD for use in Azure AD Domain Services:
103+
104+
> [!IMPORTANT]
105+
> Azure AD Connect only synchronizes legacy password hashes when you enable Azure AD DS for your Azure AD tenant. The following steps aren't used if you only use Azure AD Connect to synchronize an on-premises AD DS environment with Azure AD.
106+
>
107+
> If your legacy applications don't use NTLM authentication or LDAP simple binds, we recommend that you disable NTLM password hash synchronization for Azure AD DS. For more information, see [Disable weak cipher suites and NTLM credential hash synchronization](../../active-directory-domain-services/secure-your-domain.md).
103108
104109
1. Azure AD Connect retrieves the public key for the tenant's instance of Azure AD Domain Services.
105110
1. When a user changes their password, the on-premises domain controller stores the result of the password change (hashes) in two attributes:
106111
* *unicodePwd* for the NTLM password hash.
107112
* *supplementalCredentials* for the Kerberos password hash.
108-
1. Azure AD Connect detects password changes through the directory replication channel (attribute changes the need for replication to other domain controllers).
113+
1. Azure AD Connect detects password changes through the directory replication channel (attribute changes needing to replicate to other domain controllers).
109114
1. For each user whose password has changed, Azure AD Connect performs the following steps:
110115
* Generates a random AES 256-bit symmetric key.
111116
* Generates a random initialization vector needed for the first round of encryption.

0 commit comments

Comments
 (0)