trio.so
Templates

Conditional Access Policy Templates: Uses and Best Practices

Ten Microsoft Entra conditional access policy templates with what each does, the order to enable them in report-only mode, licensing, and a free download.

Mountain landscape representing leadership perspective and vision
Written by
Atena Ladchartabi

Content writer, trio.so

Published on
Modified on

Conditional Access policy templates are ready-made Microsoft Entra ID policies that you create in a few clicks from the Entra admin center (Entra ID > Conditional Access > Create new policy from templates), instead of building each rule from scratch. Most tenants start with the same set: require multifactor authentication for all users and for admins, block legacy authentication, require a compliant device, and block sign-ins from countries you do not operate in, then add risk-based policies if they have Entra ID P2. Every template is created in report-only mode, so you check the sign-in logs before turning it on, and you exclude at least two emergency access accounts first. The ten templates below come with what each does, the licence it needs and the order to enable them.

If you are setting up Conditional Access for the first time, or you are an MSP rolling the same baseline out to client tenants, start with the quick reference table and the report-only section; the free template download is just below.

TL;DR

  • A Conditional Access policy is an if-then rule: if a sign-in matches the conditions, the user must meet a grant control, such as MFA, or is blocked.
  • Microsoft groups its templates into six categories: Secure foundation, Zero Trust, Remote work, Protect administrator, Emerging threats and AI agents.
  • Templates are created in report-only mode. Review the sign-in logs before you switch a policy on.
  • Core templates with Entra ID P1: MFA for all users, MFA for admins, block legacy authentication, require a compliant device, block by location.
  • Sign-in risk and user risk policies need Entra ID P2.
  • Microsoft retired the "Require approved client app" grant in June 2026; use "Require app protection policy" instead.
  • Create two emergency access (break-glass) accounts and exclude them from every blocking policy before you enforce anything.

What a Conditional Access Policy Actually Does

If you have already run at least one Conditional Access policy in production, skip to the templates.

Conditional Access evaluates each sign-in against signals: who the user is and their roles, the device's platform and compliance state, the location or IP address, the app being opened, and, with Entra ID P2, the sign-in and user risk. If a policy's conditions match, its grant control applies. Grant controls include requiring MFA (or a specific authentication strength), requiring a compliant or Microsoft Entra hybrid joined device, requiring an app protection policy, requiring a password change, or blocking access.

Session controls are lighter: they set how often users must sign in again, or turn off persistent browser sessions, without blocking access. They suit personal and unmanaged devices.

Microsoft describes Conditional Access as its Zero Trust policy engine. Every sign-in passes through it, and if any applicable policy blocks, the sign-in fails, whatever other policies allow. When a sign-in is blocked and you cannot tell why, open the sign-in logs in Entra ID: the Conditional Access tab on each entry shows which policies applied and what each returned.

Free Conditional Access Policy Template

Download the template to plan your policies before you build them: users and exclusions, conditions, grant and session controls, and the date each one moves from report-only to on.

The Conditional Access Policy Templates You Should Actually Deploy

Microsoft's template list changes as it adds and renames policies, so check the names in your Entra admin center. The ten below are the ones most tenants need, in the order most teams deploy them. Some challenge the user (MFA), some require a condition (a compliant device, a trusted location), and some simply block.

Require MFA for All Users

The first policy for most organizations: every user must complete multifactor authentication to reach cloud apps. Microsoft reports that MFA blocks the large majority of automated account compromise attacks.

  • Users: all users, excluding your emergency access accounts.
  • Target resources: all resources.
  • Grant: require multifactor authentication, or an authentication strength.
  • Licence: Entra ID P1 (included in Microsoft 365 Business Premium, E3 and E5).

Microsoft now enforces MFA for its admin portals on its own, but this policy is still needed for everything else. If users are blocked instead of prompted, check that they have registered an authentication method; the "Securing security info registration" template protects that registration step.

Require MFA for Admins

The same control, scoped to privileged roles such as Global Administrator, Security Administrator and the other admin roles in the template.

  • Users: selected directory roles.
  • Target resources: all resources.
  • Grant: require MFA; the "Require phishing-resistant multifactor authentication for administrators" template goes further, with passkeys or FIDO2 keys.
  • Licence: P1.

Even if the all-users policy covers admins, a separate admin policy makes it harder to exclude an admin by accident.

Block Legacy Authentication

Blocks sign-ins over older protocols that cannot do MFA, such as POP, IMAP, SMTP authentication, older Exchange ActiveSync clients and basic authentication.

  • Condition: client apps "Exchange ActiveSync clients" and "Other clients".
  • Grant: block access.
  • Licence: P1.

Before you enforce it, run it in report-only mode and filter the sign-in logs by client app to find printers, scanners, service accounts and old mail clients that still use these protocols. If something stops working afterwards, its sign-in entries show the client app it used.

Require Compliant Device

Allows access only from devices that are marked compliant by an MDM connected to Microsoft Entra ID, or that are Microsoft Entra hybrid joined, depending on the template you choose.

  • Users: all users, or targeted groups.
  • Target resources: all resources, or selected apps.
  • Grant: require device to be marked as compliant.
  • Licence: P1, plus an MDM that reports compliance to Entra ID, such as Intune or a compliance partner that Microsoft supports.

Plan for the effect: unmanaged personal devices lose access to the targeted apps until they are enrolled, so decide your BYOD approach first. The "Require compliant or Microsoft Entra hybrid joined device or multifactor authentication" template is a softer starting point.

Block Access by Country or Region

Blocks sign-ins from countries where you have no reason to expect them.

  • Condition: include all locations, exclude a named location that lists your allowed countries.
  • Grant: block access.
  • Licence: P1.

Decide how to treat IP addresses that cannot be mapped to a country. Location is checked when the user signs in; it is a sign-in filter, not a firewall, and it does not stop anyone reaching the sign-in page.

IP-Based Named Location Policy

Uses your office IP ranges as a trusted named location, in one of two ways: skip some prompts on the trusted network, or allow access only from it.

  • Create a named location with your office ranges in CIDR notation, IPv4 and IPv6.
  • Mark it as trusted.
  • Exclude it from a policy, or include only it, depending on the goal.
  • Licence: P1.

If your network uses IPv6 to reach the internet, add the IPv6 ranges too, or users in the office will still be treated as outside.

Require App Protection Policy

Limits mobile access to apps that have an Intune app protection policy, which suits personal phones that are not enrolled.

  • Users: all users, or targeted groups.
  • Platforms: iOS and Android.
  • Grant: require app protection policy.
  • Licence: P1 plus Intune.

Microsoft retired the older "Require approved client app" grant in June 2026 (Microsoft 365 message center, MC1220751). Policies that use that grant are now read-only, so check older policies and move them to "Require app protection policy". Not every app that worked with the old grant supports app protection policies, so check the apps you need.

Sign-In Risk Policy

Uses Microsoft Entra ID Protection's real-time risk detection, such as anonymous IP addresses or unfamiliar sign-in properties, and challenges risky sign-ins.

  • Condition: sign-in risk medium and high.
  • Grant: require MFA.
  • Licence: Entra ID P2 (Microsoft 365 E5, or P2 added).

User Risk Policy

Responds to signs that an account itself is compromised, such as leaked credentials, by requiring a secure password change.

  • Condition: user risk high.
  • Grant: require password change, with MFA.
  • Licence: P2.

Microsoft recommends configuring both risk policies in Conditional Access rather than in the older Identity Protection policy pages.

Session Controls for Unmanaged Devices

Shortens how long sessions last on devices you do not manage.

  • Condition: a filter for devices, or the client apps, that targets unmanaged devices.
  • Session: sign-in frequency, for example every few hours, and no persistent browser session (Microsoft's "No persistent browser session" template).
  • Licence: P1.

Expect help desk calls from people who can no longer stay signed in on personal laptops, and tell them before you enforce it.

Conditional Access Policy Templates: Quick Reference

TemplateUseLicenceGrant controlExclude emergency accounts?
Require MFA for all usersBaseline for all cloud accessEntra ID P1Require MFAYes
Require MFA for adminsProtect privileged rolesEntra ID P1Require MFAYes
Block legacy authenticationStop protocols that cannot do MFAEntra ID P1BlockYes
Require compliant deviceOnly managed, compliant devicesP1 plus a compliance-reporting MDMRequire compliant deviceYes
Block by country or regionLimit sign-ins to allowed countriesEntra ID P1BlockYes
IP-based named locationTrust or require office networksEntra ID P1Block or require MFAYes
Require app protection policyProtected apps on personal phonesP1 plus IntuneRequire app protection policyYes
Sign-in risk policyChallenge risky sign-insEntra ID P2Require MFAYes
User risk policyReset compromised accountsEntra ID P2Require password changeYes
Session controls for unmanaged devicesShort sessions on personal devicesEntra ID P1Sign-in frequency, no persistent sessionYes

MSPs: Deploying Conditional Access Templates Across Client Tenants

MSPs usually apply the same baseline to every client tenant. Microsoft's partner tools support this: with granular delegated admin privileges (GDAP), the MSP gets limited admin roles in each client tenant, and Microsoft 365 Lighthouse lets partners apply baselines and review tenants from one place. Each template can also be exported as JSON from the admin center and imported into another tenant with the "Upload policy file" option. Whichever route you use, start every policy in report-only mode in each tenant, because each client's apps and accounts are different.

Before You Enable Anything: Report-Only Mode and Break Glass Accounts

Treat this as a gate every policy passes through, not a one-time setup step.

Report-only mode evaluates every sign-in and records what the policy would have done, without enforcing it. Review the sign-in logs, filter on the Conditional Access tab, and look for users and service accounts that would be blocked. A few days of logs is a minimum for a small tenant; one to two weeks catches accounts that only sign in occasionally.

Emergency access (break-glass) accounts come first. Create at least two cloud-only accounts, exclude them from every Conditional Access policy, protect them with strong, phishing-resistant credentials kept securely, and alert on any sign-in from them. Microsoft's templates exclude only the person who creates the policy, so add the emergency accounts to each policy yourself.

Before you switch a policy on, ask: are the emergency accounts excluded, have I reviewed the report-only logs, and have I checked service accounts and shared mailboxes?

  • First policy ever: start in report-only mode and review the logs for at least a few days.
  • Adding to existing policies: check for overlaps with what is already enforced, then add the new one in report-only mode.
  • Replacing a policy: keep the old one until the new one has run in report-only mode without surprises.

Which Templates Map to Your Compliance Requirements

Conditional Access produces sign-in records that show access controls working, which auditors often ask for. The mapping below is a guide, not audit advice; your auditor decides what evidence satisfies each control.

  • SOC 2 (logical access, CC6): MFA for all users and admins, block legacy authentication, require compliant device.
  • ISO/IEC 27001:2022 (Annex A 8.2 privileged access rights, 8.5 secure authentication): MFA for admins, MFA for all users, require compliant device, risk policies where licensed.
  • HIPAA (access control and person or entity authentication): MFA for all users, block legacy authentication, require compliant device. A January 2025 proposal to update the HIPAA Security Rule would make MFA an explicit requirement.
  • PCI DSS v4.0.1 (requirement 8.4, MFA): MFA for admins and for all access to the cardholder data environment, block legacy authentication, named locations.
  • GDPR (security of processing): MFA, compliant devices and location controls support the appropriate technical measures the regulation asks for.

Report-only logs are not evidence of enforcement, so make sure the policies are on before an audit period starts. For the access side of an audit, see the user access review template.

Common Mistakes That Break Conditional Access Deployments

  • Too many overlapping policies: they conflict and are hard to troubleshoot. A tenant can hold up to 240 policies, but keep to the smallest set that covers your needs, with a clear name for each.
  • Stale exclusions: people stay in exclusion groups after they change roles or leave. Review exclusion groups every quarter.
  • Forgotten accounts: guests, service accounts, shared mailboxes and unmanaged devices behave differently from normal users. Test them in report-only mode.
  • Policies still relying on "Require approved client app": since its retirement in June 2026 they are read-only. Move them to "Require app protection policy".
  • No emergency access accounts excluded: the most common cause of tenant-wide lockouts.

When a user is blocked after a change, find the failed sign-in in the logs and open its Conditional Access tab; it names the policy that failed. For the principles behind these policies, see the least privilege access model and policy enforcement points.

Managing this across many devices

Conditional Access controls who can sign in to Microsoft 365 and under what conditions; the devices still need managing. trio.so syncs users and groups from Microsoft Entra ID, supports SCIM 2.0 user provisioning with Entra ID and SAML single sign-on, and shows each device's encryption status. For MSPs, trio.so manages several client companies from one console, with each client's devices, users and policies kept separate. See Windows device management.

The trio.so Authentication and Security settings, Sign-in tab, with single sign on through Microsoft Entra ID turned on.
Single sign on with Microsoft Entra ID in the trio.so settings.

Related reading: user access review template, multi-tenant Active Directory, Kipling method zero trust and MDM vs MAM.

Ready-to-use Templates

Must-have Template Toolkit for IT Admins

Explore All
Template Toolkit

Sync users from Entra ID into your device console

trio.so syncs users and groups from Microsoft Entra ID, supports SCIM provisioning and SAML single sign-on, and manages every platform from one console.

Start free trial

Manage Every Device From One Console

trio.so brings device management, patching and security policies for Windows, macOS, Linux, iOS/iPadOS and Android into one console. Enroll a device and see it in the console within minutes.

14-day free trial. No credit card required.

trio.so brings device management, patching and security policies for Windows, macOS, Linux, iOS/iPadOS and Android into one console. Enroll a device and see it in the console within minutes.

Smiling womanAbstract geometric patternAbstract geometric patternSmiling womanSmiling woman

Frequently Asked Questions (FAQ)

A Microsoft Entra ID rule that checks each sign-in against conditions such as user, device, location, app and risk, and then requires something, such as MFA or a compliant device, or blocks access.

Preconfigured policies in the Entra admin center, grouped into Secure foundation, Zero Trust, Remote work, Protect administrator, Emerging threats and AI agents. You create a policy from a template, adjust it, and it starts in report-only mode.

Require MFA for all users, require MFA for admins, block legacy authentication, and a device policy such as require compliant device or app protection, all with emergency access accounts excluded. Add risk policies if you have Entra ID P2.

Yes. Conditional Access needs Microsoft Entra ID P1, included in Microsoft 365 Business Premium, E3 and E5. Sign-in risk and user risk policies need P2.

Through Microsoft's partner tools: granular delegated admin privileges for access to each client tenant, Microsoft 365 Lighthouse for baselines across tenants, or by exporting a policy as JSON and importing it into each tenant. Start each policy in report-only mode.

Related

From the blog

The related industry news, interviews, technologies, and resources.