Securing Sign-Ins: MFA, Conditional Access, Privileged Identity Management, Identity Protection and Passwordless
Identity Is the New Perimeter
Attackers mostly steal or guess passwords. The best defenses are MFA, smart access rules, least privilege and just-in-time admin rights.
Multifactor Authentication (MFA)
- Something you know (password), have (phone, key) or are (fingerprint). MFA asks for two or more
- Microsoft Authenticator app, FIDO2 security keys, Windows Hello for Business and certificates are strong. SMS and voice are weaker
- Security defaults (free) turn on basic protections for small tenants: MFA for admins and users, block legacy authentication
- Larger organizations use Conditional Access instead of security defaults
Conditional Access
Conditional Access is an if-then policy engine: if a sign-in matches signals, then apply controls.
| Part | Examples |
|---|---|
| Assignments (who, what) | Users and groups, cloud apps, conditions such as location, device platform, sign-in risk, client app |
| Access controls | Block, require MFA, require a compliant device, require a hybrid joined device, require password change, limit session |
| Common policy | Idea |
|---|---|
| Require MFA for all admins | Protect privileged accounts |
| Block legacy authentication | Old protocols cannot do MFA |
| Require MFA when off the corporate network | Use named locations |
| Require compliant device for Azure management | Only managed devices reach the portal |
| Block sign-ins from risky countries | Location rule |
| Require MFA for risky sign-ins | Uses Identity Protection (P2) |
Use report-only first Start new policies in Report-only mode, read the sign-in logs, then enable. Always exclude break-glass accounts so you cannot lock yourself out.
Break-Glass Accounts
- Two emergency admin accounts, cloud-only, with very long passwords stored safely, excluded from Conditional Access, monitored with alerts when used
Privileged Identity Management (PIM)
- Admins are eligible for a role and must activate it when needed, for a limited time, with MFA, justification and approval
- Works for Entra roles and Azure RBAC roles
- Gives alerts, access reviews and an audit history
- Reduces the time attackers can use stolen admin accounts (zero standing privilege)
Identity Protection
- Detects risky sign-ins and risky users (leaked credentials, impossible travel, anonymous IP, unfamiliar sign-in properties)
- Risk-based policies can require MFA or password change automatically
- Needs Entra ID P2
Passwordless and SSPR
| Feature | Description |
|---|---|
| Passwordless | Windows Hello for Business, Authenticator phone sign-in, FIDO2 keys, passkeys |
| Self-service password reset (SSPR) | Users reset their own password with verification, lowering help-desk work. Password writeback syncs to on-premises |
| Password protection | Blocks weak and banned passwords, also for on-premises AD with an agent |
| Temporary Access Pass | Short-lived code to onboard passwordless methods |
Hands-On Policy Sketch
text
Policy: "Require MFA for Azure management"
Users: All users Exclude: break-glass accounts
Target resources: Microsoft Azure Management
Conditions: any location
Grant: Require multifactor authentication
Enable policy: Report-only → On after review
Practice
- Enable security defaults on a test tenant or create a Conditional Access policy in report-only mode
- Create two break-glass accounts and exclude them
- Make a user eligible for Contributor with PIM and activate it
- Explain why SMS MFA is weaker than a FIDO2 key
Conclusion
Secure sign-ins with MFA and Conditional Access, use PIM for just-in-time admin rights, Identity Protection for risk, and move toward passwordless. Test in report-only mode and always keep break-glass accounts.
Quick Summary: identity perimeter; MFA; Conditional Access; break-glass; PIM; Identity Protection; passwordless; sketch.

