← cd ~/topics
// topics
Conditional Access
Conditional Access is where Entra decides who gets in, from where and on what. These guides cover designing, testing and troubleshooting policies.
Start here
- Rolling out "require compliant device" without a flood of tickets
Requiring a compliant device is one of the strongest Conditional Access controls you can apply. It's also one of the easiest to get wrong. - Named locations: getting IP ranges and countries right in Conditional Access
Named locations look simple, but trusted IPs and country blocks are easy to get subtly wrong. What they can and can't do, and how to use them well. - Authentication strengths: requiring the right kind of MFA
Requiring MFA treats an SMS code and a passkey as equals. Authentication strengths let you say which methods are good enough for which resources.
Coming up
- 1 Feb 2027 Microsoft-provided SMS and voice MFA retired
- 2 Feb 2027 Entra Connect 2.5.190.0 reaches end of support
- 7 Apr 2027 Entra Connect Sync must use app-based auth
- 1 Jul 2027 SMS and voice retirement for Global Admins and external users
- 1 Jul 2027 Microsoft-provided SMS and voice MFA retired for Global Administrators and external users
Learning paths
Reference and tools
All Conditional Access posts (6)
- Rolling out "require compliant device" without a flood of tickets 20 May 2026
- Require phishing-resistant MFA on every PIM activation 22 Apr 2026
- Named locations: getting IP ranges and countries right in Conditional Access 17 Dec 2025
- Authentication strengths: requiring the right kind of MFA 10 Dec 2025
- Test Conditional Access safely with report-only mode and What If 26 Nov 2025
- Break-glass accounts done right 12 Nov 2025