Merge pull request #11148 from kondalarao-MSFT/patch-17

prmerger-automator[bot] · web-flow · commit 61455678a6e1 · 2026-03-25T10:48:02.000Z
(AzureCXP) fixes MicrosoftDocs/entra-docs-pr#547967
diff --git a/docs/identity/hybrid/connect/how-to-connect-password-hash-synchronization.md b/docs/identity/hybrid/connect/how-to-connect-password-hash-synchronization.md
@@ -211,7 +211,7 @@ With password hash synchronization enabled, this AD password hash is synced with
 >
 > Previously, when SCRIL was re-enabled and a new randomized AD password was generated, the user was still able to use their old password to authenticate to Microsoft Entra ID. Now, Connect Sync has been updated so that new randomized AD password is synced to Microsoft Entra ID and the old password cannot be used once smart card login is enabled. 
 >
-> We recommend that admins person any of the below actions if they have users with a SCRIL bit in their AD Domain
+> We recommend that admins perform any of the below actions if they have users with a SCRIL bit in their AD Domain
 > 1.	Perform a full password hash sync as per [this guide](tshoot-connect-password-hash-synchronization.md) to ensure the passwords of all SCRIL users are scrambled
 > 2.	Scramble the password of an individual user by toggling SCRIL settings off then back on or directly changing the user's password
 > 3.	Periodically rotate the passwords for SCRIL users. Eventually all such users will have their passwords scrambled

Original file line number	Diff line number	Diff line change
`@@ -211,7 +211,7 @@ With password hash synchronization enabled, this AD password hash is synced with`
`211`	`211`	`>`
`212`	`212`	`> Previously, when SCRIL was re-enabled and a new randomized AD password was generated, the user was still able to use their old password to authenticate to Microsoft Entra ID. Now, Connect Sync has been updated so that new randomized AD password is synced to Microsoft Entra ID and the old password cannot be used once smart card login is enabled.`
`213`	`213`	`>`
`214`		`-> We recommend that admins person any of the below actions if they have users with a SCRIL bit in their AD Domain`
	`214`	`+> We recommend that admins perform any of the below actions if they have users with a SCRIL bit in their AD Domain`
`215`	`215`	`> 1. Perform a full password hash sync as per [this guide](tshoot-connect-password-hash-synchronization.md) to ensure the passwords of all SCRIL users are scrambled`
`216`	`216`	`> 2. Scramble the password of an individual user by toggling SCRIL settings off then back on or directly changing the user's password`
`217`	`217`	`> 3. Periodically rotate the passwords for SCRIL users. Eventually all such users will have their passwords scrambled`