For hybrid environments if you need to find out what password policy is officially being used there are few guidelines to keep abreast of.
If your user accounts are synchronized using Azure AD connect they will be using the on-premises AD policy
Use this command to check the policy from the on-prem AD
Get-ADDefaultDomainPasswordPolicy -Identity <YourDomain.com>AzureAD policies apply when user accounts that are created and managed directly in Azure AD.
The following information is pulled from this guide directly from MS.
AzureAD Password Policies
| Property | Requirements |
| Characters allowed | A – Z a – z 0 – 9 @ # $ % ^ & * – _ ! + = [ ] { } | \ : ‘ , . ? / ` ~ ” ( ) ; blank space |
| Characters not allowed | Unicode characters. |
| Password restrictions | A minimum of 8 characters and a maximum of 256 characters. Requires three out of four of the following: Lowercase characters. Uppercase characters. Numbers (0-9). Symbols (see the previous password restrictions). |
| Password expiry duration (Maximum password age) | Default value: 90 days. The value is configurable by using the Set-MsolPasswordPolicy cmdlet from the Azure Active Directory Module for Windows PowerShell. |
| Password expiry notification (When users are notified of password expiration) | Default value: 14 days (before password expires). The value is configurable by using the Set-MsolPasswordPolicy cmdlet. |
| Password expiry (Let passwords never expire) | Default value: false (indicates that password’s have an expiration date). The value can be configured for individual user accounts by using the Set-MsolUser cmdlet. |
| Password change history | The last password can’t be used again when the user changes a password. |
| Password reset history | The last password can be used again when the user resets a forgotten password. |
| Account lockout | After 10 unsuccessful sign-in attempts with the wrong password, the user is locked out for one minute. Further incorrect sign-in attempts lock out the user for increasing durations of time. Smart lockout [docs.microsoft.com] tracks the last three bad password hashes to avoid incrementing the lockout counter for the same password. If someone enters the same bad password multiple times, this behavior will not cause the account to lock out. |
It’s important to note that some settings can’t be modified if your user accounts are exclusively managed within AzureAD.
