Merge pull request MicrosoftDocs#35790 from RolfJacobson/patch-1

American-Dipper · web-flow · commit 6c650d3ce3a9 · 2019-07-25T08:42:10.000-07:00
Update active-directory-ds-getting-started-password-sync-synced-tenan…
diff --git a/articles/active-directory-domain-services/active-directory-ds-getting-started-password-sync-synced-tenant.md b/articles/active-directory-domain-services/active-directory-ds-getting-started-password-sync-synced-tenant.md
@@ -37,7 +37,7 @@ The steps involved are different for cloud-only user accounts vs user accounts t
 A synced Azure AD tenant is set to synchronize with your organization's on-premises directory using Azure AD Connect. By default, Azure AD Connect does not synchronize NTLM and Kerberos credential hashes to Azure AD. To use Azure AD Domain Services, you need to configure Azure AD Connect to synchronize credential hashes required for NTLM and Kerberos authentication. The following steps enable synchronization of the required credential hashes from your on-premises directory to your Azure AD tenant.
 
 > [!NOTE]
-> **If your organization has user accounts that are synchronized from your on-premises directory, you must enable synchronization of NTLM and Kerberos hashes in order to use the managed domain.** A synced user account is an account that was created in your on-premises directory and is synchronized to your Azure AD tenant using Azure AD Connect.
+> **If your organization has user accounts that are synchronized from your on-premises directory, you must enable synchronization of NTLM and Kerberos hashes in order to use the managed domain.** A synced user account is an account that was created in your on-premises directory and is synchronized to your Azure AD tenant using Azure AD Connect.  The password hash sync is a different process from user/object sync. You need to disable/enable password hash sync to get full password sync, then you will see the batch password hash updates in the application event log.
 >
 >
 

Original file line number	Diff line number	Diff line change
`@@ -37,7 +37,7 @@ The steps involved are different for cloud-only user accounts vs user accounts t`
`37`	`37`	A synced Azure AD tenant is set to synchronize with your organization's on-premises directory using Azure AD Connect. By default, Azure AD Connect does not synchronize NTLM and Kerberos credential hashes to Azure AD. To use Azure AD Domain Services, you need to configure Azure AD Connect to synchronize credential hashes required for NTLM and Kerberos authentication. The following steps enable synchronization of the required credential hashes from your on-premises directory to your Azure AD tenant.
`38`	`38`
`39`	`39`	`> [!NOTE]`
`40`		`-> If your organization has user accounts that are synchronized from your on-premises directory, you must enable synchronization of NTLM and Kerberos hashes in order to use the managed domain. A synced user account is an account that was created in your on-premises directory and is synchronized to your Azure AD tenant using Azure AD Connect.`
	`40`	+> If your organization has user accounts that are synchronized from your on-premises directory, you must enable synchronization of NTLM and Kerberos hashes in order to use the managed domain. A synced user account is an account that was created in your on-premises directory and is synchronized to your Azure AD tenant using Azure AD Connect. The password hash sync is a different process from user/object sync. You need to disable/enable password hash sync to get full password sync, then you will see the batch password hash updates in the application event log.
`41`	`41`	`>`
`42`	`42`	`>`
`43`	`43`