2.2. Implement and Manage Authentication and Access
💡 First Principle: Authentication answers "are you really this identity?" and access control answers "given who you are, and how risky this moment looks, what may you reach?" Microsoft Entra keeps them as separate layers — methods and password rules on one side, Conditional Access on the other — so you can strengthen proof of identity without rewriting every access rule, and the reverse.
Why care? Stolen and guessed credentials remain the most common way attackers get into Microsoft 365 tenants, and every downstream control — Purview, Defender, Copilot settings — assumes the person signing in is who they claim to be. This layer has also changed more than any other in the past two years: authentication methods moved out of the legacy MFA and SSPR pages, and risk-based policies moved out of ID Protection into Conditional Access. Material written for MS-102 is wrong on both points.
The mental model is an evaluation pipeline. At sign-in, Entra checks the password against Password Protection rules and lockout, then asks for a second method allowed by the Authentication methods policy, and only then evaluates every Conditional Access policy whose assignments match — user, app, location, device, risk — combining their grant controls. When something fails, the sign-in logs tell you which stage stopped it.
⚠️ Common Misconception: Many admins still try to configure MFA methods in the legacy per-user MFA service settings or the SSPR methods page. Since 30 September 2025, authentication methods can't be managed in those legacy policies. The Authentication methods policy is the place. Only security questions and the SSPR "number of methods required to reset" setting still live in the legacy SSPR policy.