Where find account with leaked password

Brass Contributor

we setup password has sync and all about azure ad assword protection in audit mode.

Now where i find account with leaked password?

When i try chenge password do som leaked pass like asdf123456789, in evenlog i see password would normally have been rejected but in audit mode its ok.

So now i need somewhere view all users with leaked password.
Where to find this info?

11 Replies
Hi @Marek_Belan,

Great to hear that you have found your way to use Azure AD Password Protection.

As far as my knowledge goes, you won't be able to request a list of the leaked passwords.
Furthermore, since Microsoft purchases leaked passwords from several sources (e.g., Dark web), you won't get a list with the passwords known as leaked passwords on the so-called Global Banned Password List. The user only will receive a prompt that the password does not meet the length, complexity, or history requirements. It also won't read all the current passwords. Azure AD Password Protection only will audit or enforce newly created/configured passwords.

I hope this answers your question.
i dont want to see leaked password !
I want to see which account have leaked password.
Hi, again @Marek_Belan,

You won't be able to see users with a leaked password configured. As stated earlier, when changing the configuration to enforced mode, users will be prevented from setting newly created passwords that are on the (custom and global) banned passwords list. The attempt will be, of course, logged.

Does this answer your question?
So we setup The Azure AD Password Protection and we cant identify users with leaked password??????

Did you already read the Microsoft documentation about this feature? I assume not. Your suggestion would be a great feature request but isn't available at the moment.

When a user changes or resets their password, the new password is checked for strength and complexity by validating it against the combined list of terms from the global and custom banned password lists.

Even if a user's password contains a banned password, the password may be accepted if the overall password is otherwise strong enough. A newly configured password goes through the following steps to assess its overall strength to determine if it should be accepted or rejected:


Password hash synchronization
Risk detections like leaked credentials require the presence of password hashes for detection to occur. For more information about password hash synchronization, see the article, Implement password hash synchronization with Azure AD Connect sync.

So where is the risk? We setup hash sync, user has leaked pasword, where i see rising risk of this user?
If you want to see a current overview of the Risky sign-ins or Risky users, you must have an Azure AD Premium P2 license. I have written a blog about Azure AD Password Protection that might help you.


I would recommend you read the license requirements.
We have on all users Microsoft 365 E5 Security....
In that case, see the following article which gives you insights on how to, e.g., investigate risks within your tenant. But, again, I don't want to sound rude, but these kinds of things can be found on Google easily.


I hope this helps and good luck!
This is primary problem.
User have leaked password BUT DONT HAVE RISED RISK.
Hello again. I would advise you to create a support request so one of the Microsoft engineers can dig into this behavior.