Before you start
- An Entra ID P1 licence (included in Microsoft 365 Business Premium, E3, E5); P2 for risk-based policies
- Strong authentication methods already deployed (see two-factor authentication and FIDO2 keys)
- Two emergency accounts created (see identity management)
In plain words
Conditional access is a smart doorkeeper. It doesn't just check your badge: it looks at who you are, where you're coming from, with which device, which application you're heading to, and whether anything seems suspicious. Depending on the answers, it lets you through, asks for extra proof, or refuses entry. Governance is the rulebook this doorkeeper follows: written down, reviewed, tested, and not changed by anyone on their own.
This guide covers conditional access in Microsoft Entra ID, the most widespread in businesses. The principle is the same at other identity providers (section 8). Information checked on 20 October 2026 in Microsoft's documentation.
1. The principle: "if… then…"
Each policy reads like a rule:
If these users access these applications under these conditions, then grant, require or block.
| Element | Examples |
|---|---|
| Users (who?) | All, a group, administration roles, guests; with exclusions |
| Resources (to what?) | All applications, Microsoft 365, the admin portals, a line-of-business application |
| Conditions (in what context?) | Platform (Windows, iOS, Android…), location (country, IP addresses), client type, sign-in or user risk |
| Decision (then?) | Block; or grant while requiring: two-factor authentication, an authentication strength (for example "phishing-resistant"), a compliant device (Intune), a hybrid-joined device, an approved application |
| Session (and afterwards?) | Sign-in frequency, no persistent browser session, in-app restrictions |
All the policies that apply are evaluated together: all their requirements must be met, and a block always wins.
Conditional access applies after the password check
It decides what happens once the first factor has been validated. It doesn't replace protection against brute-force attacks or the password policy; it adds a control on top.
2. Without a P1 licence: security defaults
Tenants without Entra ID P1 have security defaults, enabled on new tenants. It's a single switch, with no settings:
| What they enforce |
|---|
| All users register for two-factor authentication (Microsoft Authenticator) |
| Two-factor authentication at every sign-in for the main administration roles |
| Two-factor authentication "when necessary" for other users |
| Blocking legacy authentication (IMAP, POP3, authenticated SMTP, old Office clients) |
| Blocking the device code flow, widely used in attacks |
| Two-factor authentication for access to Azure management (portal, PowerShell, CLI) |
For a small organisation without a P1 licence, turn them on: it's the best free protection. Security defaults and conditional access can't both be active: you turn off the former when you deploy the latter.
3. Microsoft-managed policies
On tenants with P1 licences, Microsoft creates managed policies in report-only mode, then turns them on if the administrator doesn't react. You can turn them on or off or add exclusions, but not delete or rename them. Among them:
- Block legacy authentication;
- Block the device code flow;
- Two-factor authentication for administrators on Microsoft admin portals;
- Two-factor authentication for all users;
- Two-factor authentication and reauthentication for risky sign-ins;
- Phishing-resistant authentication for administrators.
See them in Entra ID > Conditional Access > Policies: they're flagged as managed by Microsoft.
4. The recommended foundation
Microsoft offers ready-to-use templates (New policy from template) and a three-phase deployment. Here's a reasonable foundation for a small business, to adapt:
| No. | Policy | Users | Decision | Licence |
|---|---|---|---|---|
| CA001 | Block legacy authentication | All | Block | P1 |
| CA002 | Block the device code flow (except Teams Rooms devices that need it) | All | Block | P1 |
| CA003 | Secure method registration (My Security Info page) | All | From a trusted location or a compliant device, or a Temporary Access Pass | P1 |
| CA004 | Phishing-resistant authentication for administrators | Administration roles | "Phishing-resistant MFA" authentication strength | P1 |
| CA005 | Two-factor authentication for everyone | All | Require two-factor authentication (or an authentication strength) | P1 |
| CA006 | Two-factor authentication for guests | Guests and external users | Require two-factor authentication | P1 |
| CA007 | Compliant or hybrid-joined device for company applications | Employees | Require a compliant (Intune) or hybrid-joined device | P1 + Intune |
| CA008 | Block unknown platforms | All | Block unrecognised systems | P1 |
| CA009 | Sign-ins with medium or high risk | All | Require two-factor authentication and reauthentication | P2 |
| CA010 | High-risk users | All | Require a secure password change, or block | P2 |
The emergency accounts are excluded from all these policies, as are the synchronisation accounts (Entra Connect, Cloud Sync), which don't sign in interactively.
Block by country?
A policy that blocks sign-ins from countries where the business doesn't operate reduces the noise, but attackers use VPNs and servers located in your country. It's a complement, never a replacement for two-factor authentication.
5. Deploying without locking yourself out
A badly set policy can block everyone, including you
A "Block, all users, all applications" policy with no exclusion locks the entire tenant. That's exactly the situation emergency accounts exist for.
- Emergency accounts: two cloud-only accounts, Global Administrators, protected by a FIDO2 key, excluded from every policy, and monitored (an alert at every sign-in).
- Report-only mode: every new policy starts in report-only mode; Entra calculates what it would have done without blocking anything. Templates are created in this mode by default.
- Analysis: sign-in logs (the Conditional Access tab of each sign-in), the Conditional Access Insights and Reporting workbook, the What If tool to simulate a sign-in.
- Pilot group: turn it on first for the IT department, then a volunteer department.
- Communication: tell users beforehand (what changes, when, who to contact).
- General activation, then monitoring of failures for a few days.
6. Governing the policies
| Practice | Why |
|---|---|
Naming convention: CA004-Admins-PhishingResistant-All-Apps (number, population, control, resource) |
You understand the policy without opening it |
| Policies by population (personas): users, administrators, guests, service accounts, emergency accounts | Each population has its own needs; avoids catch-all policies |
Exclusions through named, documented groups (CA-Exclusion-Emergency), never individual users |
Exclusions are visible, justified and reviewed |
| Dedicated role: Conditional Access Administrator, assigned just in time (PIM) | Few people can change the doorkeeper |
| Change management: every change goes through report-only mode and approval | No last-minute change that blocks the business |
| Backup and versioning of the policies (JSON export through Microsoft Graph, tools such as Microsoft365DSC) | Go back to the previous state after a mistake |
| Quarterly review: unused policies, exclusions still justified, new recommendations | The context and the threats change |
| Alerts on changes to a policy and on emergency account sign-ins | Detect an attacker weakening the protection |
Export all the policies with the Microsoft Graph PowerShell module, to archive them:
Connect-MgGraph -Scopes "Policy.Read.All"
Get-MgIdentityConditionalAccessPolicy -All |
ConvertTo-Json -Depth 10 |
Out-File "CA-export-$(Get-Date -Format yyyy-MM-dd).json"
7. Going further
| Feature | What it brings |
|---|---|
| Custom authentication strength | Require precisely certain methods (for example FIDO2 only) for a sensitive application |
| Continuous access evaluation (CAE) | Near-immediate revocation of a session when an account is disabled or the user changes network |
| Token protection | Binds the session token to the device: a stolen token doesn't work elsewhere |
| Conditional access for workload identities | Control applications and service principals, not just humans |
| Authentication contexts | Require stronger authentication for a specific action (opening a confidential SharePoint site, activating a PIM role) |
| Microsoft Entra Internet Access and Private Access | Extend these controls to web browsing and internal applications, replacing the VPN |
8. Outside Microsoft
| Solution | Equivalent |
|---|---|
| Google Workspace | Context-Aware Access: conditions on the device, IP address, location |
| Okta | Authentication policies and access rules based on network, device and risk |
| Keycloak (open source) | Conditional authentication flows: require a second factor depending on role, client or IP address |
| authentik (open source) | Customisable policies and flows, suited to homelabs and small businesses |
| Identity-aware proxy (Pomerium, oauth2-proxy, Cloudflare Access) | Put an access decision in front of any internal web application |
9. Checklist
| Item | Done? |
|---|---|
| Security defaults on if there's no P1 licence | ☐ |
| Two emergency accounts excluded from every policy, and monitored | ☐ |
| Legacy authentication and device code flow blocked | ☐ |
| Two-factor authentication for everyone, phishing-resistant for administrators | ☐ |
| Authentication method registration protected | ☐ |
| Compliant devices required for company applications | ☐ |
| Every new policy tested in report-only mode | ☐ |
| Naming convention and documented exclusions | ☐ |
| Policies exported and versioned | ☐ |
| Alerts on policy changes | ☐ |
Key points
- Conditional access decides who accesses what, from where and with what: block, or grant with requirements.
- Without a P1 licence: security defaults, to turn on. With P1: keep an eye on the Microsoft-managed policies and build your foundation from the templates.
- The foundation: legacy authentication blocked, two-factor authentication for everyone, phishing-resistant for administrators, compliant devices.
- Report-only mode, pilot group, What If tool, and emergency accounts excluded: you never lock yourself out.
- Governance: naming, exclusions through documented groups, export of the policies and alerts on changes.