Better Description of what StrongPasswordRequired does

Bronze Contributor

Can anyone location MSFT Documentation for exactly what this does?

set-msoluser -StrongPasswordRequired $true


set-msoluser -StrongPasswordRequired $false

The documentation on set-msoluser only states:

"Specifies whether to require a strong password for the user"

But what I'm trying to find out is, what is the password policy for a strong password, and what is the policy for when this is set to false?

For example, Strong prevents you using your own username in the password, etc. ( I need the full policy definition on a Microsoft documentation site).





7 Replies
Thanks Dean. I've read that document multiple times but I can't seem to find what the *policy* difference is when this parameter is set to true or false?
StrongPasswordRequired $true vs StrongPasswordRequired $false
For example, Strong prevents you using your own username in the password? Anything else?

A little late, but just wanted to complete the thread.


Strong passwords only:


-Requires three out of four of the following:
-Lowercase characters.
-Uppercase characters.
-Numbers (0-9).
--A – Z
--a - z
--0 – 9
--@ # $ % ^ & * - _ ! + = [ ] { } | \ : ‘ , . ? / ` ~ " ( ) ;

Also, don't do it! It's shown that adding password complexity doesn't really decrease the risk in your environment. Better to use AzureAD SSPR and AzureAD Password Protection to ensure your users don't pick common passwords.

NIST guidance no longer recommends complex passwords, or regularly changing passwords.

Yeah! Totally agree! And SSPR is an awesome feature

SSPR will only allow passwords that match the Azure AD Password complexity requirements when the 'strongpasswordrequired' parameter is set to True. Also, the Azure AD password protection proxy feature is in preview and requires AD integration. For in cloud environments only, it won't work.

Sorry, @Ipsito_Dutta that's not correct


See as all cloud only account passwords are matched against Microsoft's list of weak passwords. The custom banned list and on premises integration are preview, not checking against weak passwords. It's easy to prove as well.