This article will explain on how to change/disable Password Complexity Requirement for the Office 365 users. It is recommended that you configure these policies before setting up the user’s final passwords, and this would force the user’s to change the password again. Please be careful with the commands you run on PowerShell, it’s a powerful tool, and can do a lot more than you can imagine.

  • Command to change the Complexity for single user:

Set-MsolUser -UserPrincipalName -StrongPasswordRequired $false

  • Command to change the Complexity requirements for All Users:

Get-MsolUser | Set-MsolUser –StrongPasswordRequired $false

Note: Once you run this command, you will be prompted to change the password on the next login. You can run the following command to ensure that the password is not expired on the next login. However there is a catch, in any case  you’ll either settings up a new password for them, or you’ll need to know their existing passwords.

  • Disable password change on next login for one user:

Set-MsolUserPassword -UserPrincipalName -NewPassword “password” -ForceChangePassword $false

Note: Value for New Password can be an existing password or a new Password.

  • Disable password change on next login for all Users:

Get-MsolUser | Set-MsolUserPassword –NewPassword “password” -ForceChangePassword $false

Note: This command will assign a common password for all users. However, my suggestion would be change the ForceChangePassword to True, as the users can than choose their own password when doing this for bulk users.

Although it’s a complicated process to not allow the password to expire after configuring the password, I would still advise that one should change the complexity before sharing new password with the users. To know more about the Password Complexity requirements for Office 365, click here.

Please do not forget to share your feedback, or ask us a question by clicking here.

The following two tabs change content below.
Passionate for Latest Gadgets, a Computer geek by Hobby, and luckily Profession too. Started my career in 2005 with IBM, worked with Microsoft later. Back in 2009, started Pledge Technologies ( (parent company to Grishbi). We, at Pledge Technologies, provide IT Consulting to SMBs across US & UK. Specialized in Microsoft Technologies like AD, Exchange, etc., and lot of experience of Office 365 Migration for various clients. Grishbi is a platform where we express what we learned today, and share it with world.
%d bloggers like this: