Description
Microsoft Azure applies a default global banned password list to all user and admin accounts that are created and managed directly in Microsoft Entra ID.
The Microsoft Entra password policy does not apply to user accounts that are synchronized from an on-premises Active Directory environment, unless Microsoft Entra ID Connect is used and EnforceCloudPasswordPolicyForPasswordSyncedUsers
is enabled.
Review the Default Value
section for more detail on the password policy.
For increased password security, a custom banned password list is recommended
Rationaleβ
Enabling this gives your organization further customization on what secure passwords are allowed. Setting a bad password list enables your organization to fine-tune its password policy further, depending on your needs. Removing easy-to-guess passwords increases the security of access to your Azure resources.
Impactβ
Increasing needed password complexity might increase overhead on administration of user accounts. Licensing requirement for Global Banned Password List and Custom Banned Password list requires Microsoft Entra ID P1 or P2. On-premises Active Directory Domain Services users that are not synchronized to Microsoft Entra ID also benefit from Microsoft Entra ID Password Protection based on existing licensing for synchronized users.
Auditβ
From Azure Portalβ
- From Azure Home select the Portal Menu.
- Select
Microsoft Entra ID
. - Under
Manage
, selectSecurity
. - Under
Manage
, selectAuthentication Methods
. - Under
Manage
, selectPassword Protection
. - Ensure
Enforce custom list
is set toYes
. - Scroll through the list to view the enforced passwords.
Default Valueβ
By default the custom bad password list is not Enabled
. Organizational-specific terms can be added to the custom banned password list, such as the following examples:
- Brand names
- Product names
- Locations, such as company headquarters
- Company-specific internal terms
- Abbreviations that have specific company meaning
- Months and weekdays with your company's local languages
The default Azure bad password policy is already applied to your resources which applies the following basic requirements:
Characters allowedβ
- Uppercase characters (A - Z)
- Lowercase characters (a - z)
- Numbers (0 - 9)
- Symbols:
- @ # $ % ^ & * - _ ! + = [ ] { } | \ : ' , . ? / ` ~ " ( ) ; < >
- blank space
Characters not allowedβ
- Unicode characters
Password lengthβ
Passwords require:
- A minimum of eight characters
- A maximum of 256 characters
Password complexityβ
Passwords require three out of four of the following categories:
- Uppercase characters
- Lowercase characters
- Numbers
- Symbols
Note: Password complexity check isn't required for Education tenants.
Password not recently usedβ
- When a user changes or resets their password, the new password can't be the same as the current or recently used passwords.
- Password isn't banned by Entra ID Password Protection.
- The password can't be on the global list of banned passwords for Azure AD Password Protection, or on the customizable list of banned passwords specific to your organization.
Evaluationβ
New passwords are evaluated for strength and complexity by validating 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.
Referencesβ
- https://learn.microsoft.com/en-us/entra/identity/authentication/concept-password-ban-bad-combined-policy
- https://learn.microsoft.com/en-us/entra/identity/authentication/concept-password-ban-bad
- https://docs.microsoft.com/en-us/powershell/module/Azuread/
- https://www.microsoft.com/en-us/research/publication/password-guidance/
- https://learn.microsoft.com/en-us/entra/identity/authentication/tutorial-configure-custom-password-protection
- https://learn.microsoft.com/en-us/security/benchmark/azure/mcsb-identity-management#im-6-use-strong-authentication-controls