Black Friday sale: an extra 40% off every course until Monday, November 30.New Year sale: an extra 30% off every course until Friday, January 1.Memorial Day sale: an extra 25% off every course until Monday, May 31.SysAdmin Day sale: an extra 25% off every course until Sunday, August 1.Back to School sale: an extra 25% off every course until Sunday, August 22.Labor Day sale: an extra 25% off every course until Monday, September 6.Black Friday sale: an extra 40% off every course until Monday, November 29.New Year sale: an extra 30% off every course until Saturday, January 1.Choose your certification →

Copyright (c) 2026 MindMesh Academy. All rights reserved. This content is proprietary and may not be reproduced or distributed without permission.

2.2.2. Microsoft Entra Password Protection

💡 First Principle: Attackers don't guess passwords at random — they try the passwords people actually choose: the company name with a year, the season with an exclamation mark. Password Protection blocks the patterns attackers try first, which is why it normalizes and fuzzy-matches rather than only comparing exact strings.

Password Protection evaluates every password change or reset against two lists:

  • The global banned password list, maintained by Microsoft from attack data. It applies to everyone automatically, can't be configured or disabled, and isn't published.
  • The custom banned password list, up to 1,000 terms, where you add your organization's own weak terms — brand names, product names, office locations, sports teams. Use base terms; you don't need to list variations.

Evaluation normalizes the candidate password (lowercasing, and substitutions such as 0→o, 1→l, $→s, @→a), fuzzy-matches banned terms at an edit distance of one, and substring-matches the user's first and last name and the tenant name. Each banned term found scores one point and each remaining character scores one point; a password needs at least five points to be accepted. So in Contoso's tenant C0nt0s0!! normalizes to contoso!!: one point for the banned term plus two for the remaining characters makes three, and it's rejected, even though no list contains that exact string. Adding length raises the score — Contoso2026! scores six and passes — so the custom list stops the weakest variants rather than every password containing a banned word.

Licensing:
UsersGlobal listCustom list
Cloud-onlyFreeEntra ID P1 or P2
Synchronized from on-premises AD DSP1 or P2P1 or P2

On-premises. To apply the same lists to passwords changed on domain controllers, you install the DC agent on domain controllers and a proxy service that fetches the policy from Entra. On-premises enforcement can run in Audit mode (log what would be rejected) or Enforced mode; audit mode exists only on-premises — the cloud always enforces.

Smart lockout sits alongside it, locking out sign-in attempts that look like attacks while letting the real user in. Defaults are a threshold of 10 failed attempts and a 60-second lockout; customizing them needs P1. In a hybrid environment, set the Entra lockout threshold lower than the AD DS threshold so Entra locks out the attacker before the on-premises account is locked.

⚠️ Exam Trap: "Test the impact of banned passwords before enforcing them" is possible only for on-premises domain controllers, through the DC agent's Audit mode. There is no audit mode for cloud password changes.

Reflection Question: Contoso adds "contoso" to its custom banned list. A user tries C0nt0s0!!. Walk through its score and why it's rejected, then explain why a longer password that still contains "contoso" might pass.

See how it connects
Alvin Varughese
Written byAlvin Varughese
Founder•26 professional certifications earned