Skip to content

Commit ae28239

Browse files
Update concept-identity-protection-risks.md
Changed line 106 from #### Why are not I seeing any leaked credentials? to #### Why am I not seeing any leaked credentials? closes MicrosoftDocs/azure-docs/issues/88845 ------- cc: @MicrosoftGuyJFlo
1 parent 348e522 commit ae28239

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/active-directory/identity-protection/concept-identity-protection-risks.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -103,7 +103,7 @@ Microsoft finds leaked credentials in various places, including:
103103
- Law enforcement agencies.
104104
- Other groups at Microsoft doing dark web research.
105105

106-
#### Why are not I seeing any leaked credentials?
106+
#### Why am I not seeing any leaked credentials?
107107

108108
Leaked credentials are processed anytime Microsoft finds a new, publicly available batch. Because of the sensitive nature, the leaked credentials are deleted shortly after processing. Only new leaked credentials found after you enable password hash synchronization (PHS) will be processed against your tenant. Verifying against previously found credential pairs is not done.
109109

0 commit comments

Comments
 (0)