A conditional access policy is an if-then rule for your Microsoft 365 sign-ins: if someone tries to reach a resource under certain conditions, they must meet a requirement or be blocked. For a small business, the right first set is short: require multi-factor authentication (MFA), block old sign-in methods, and add a device or location rule. Roll each one out in report-only mode, with a break-glass account excluded, so no one gets locked out. Mavericks Office Solutions runs this kind of identity security for small and mid-sized businesses as part of an outsourced IT department.
TL;DR
- Conditional Access is Microsoft Entra’s policy engine. It reads signals (who, what device, where, how risky) and then allows, blocks, or asks for more proof.
- Start with three policies: MFA for everyone, blocking legacy authentication, and a device-compliance or location rule.
- Always exclude emergency-access accounts and test in report-only mode before you enforce.
- Device-based policies need Entra ID P1 or P2, which Microsoft 365 Business Premium includes.
- Policies stack. Every one that applies to a sign-in must be satisfied, so design them as a set.
Table of Contents
- What a conditional access policy actually does
- Conditional access examples worth copying
- Licenses and roles: what you need
- Risk-based policies: when to add them
- Best practices for rollout without lockouts
- What Conditional Access cannot do
- A realistic starter plan for a 50-person company
- Where Mavericks fits
- Perspective
- FAQ
- Sources
What a conditional access policy actually does
A password only proves someone knows a secret. Conditional Access adds context. Microsoft describes policies at their simplest as if-then statements: if a user wants a resource, then they must complete an action.
Every policy has two halves.
Assignments (the “if”). Who the policy covers (users, groups, roles, guests), which apps or resources, and the conditions: device platform, location, client app, and sign-in or user risk.
Access controls (the “then”). Either block access, or grant it with requirements such as MFA, a compliant device, or an approved app. Session controls can then limit what the person does once inside.
The decision logic matters, because it explains most surprises:
- Conditions inside one policy are combined with AND. A policy for “guests on mobile devices outside the US” only fires when all three are true.
- If a policy says block, access stops there.
- If no policy blocks, the user must satisfy the grant controls of every applicable policy. Multiple policies stack rather than cancel each other.
Two more facts save you from false assumptions. A Conditional Access policy is evaluated after the first sign-in step, the password, is completed, so Microsoft says it is not meant as a front-line defense against denial-of-service attacks. And it works as an adaptive engine that weighs real-time user, device, location and session-risk signals, as described on Microsoft’s product page, so one rule can be strict for an unknown laptop in another country and quiet for a managed laptop in your office.
Conditional access examples worth copying
Microsoft publishes a set of common policies and templates. These are the ones that fit a company of 10 to 250 people.
1. Require MFA for all users
This is the baseline. Microsoft recommends requiring MFA for all users and all resources, with exclusions for emergency-access accounts and directory-synchronization accounts. Guests can be left out only if a separate guest policy covers them. The step-by-step procedure needs at least the Conditional Access Administrator role.
If you have not set up MFA yet, our guides to MFA for business and a Microsoft 365 MFA setup with a recovery checklist cover the user side: enrollment, recovery, and what to tell staff.
2. Block legacy authentication
Older protocols such as basic email sign-in cannot prompt for MFA, so attackers use them to skip it. Blocking legacy authentication is one of the policies Microsoft includes among its recommended templates. Most small tenants find that nothing legitimate still depends on it, and the report-only results prove that before you enforce.
3. Require a compliant device or MFA
This rule says: reach company data from a managed, compliant (or hybrid-joined) device, or complete MFA. It keeps a personal laptop from becoming a quiet side door into email and files.
4. Require approved apps or app protection on phones
For staff who read email on personal phones, you can require an approved app with app protection, so company data stays inside a managed container.
5. Block by location
If you only operate in the US, a policy that blocks sign-ins from countries where you have no staff removes a large share of junk attempts. Microsoft’s block-access example excludes trusted locations, sets conditions such as location and client app, and keeps the policy in report-only mode before enabling it. Travelers need a plan: a temporary group exclusion beats disabling the rule.
6. Require MFA for guests
Vendors, contractors and clients who join Teams or SharePoint should meet the same bar as employees. A guest-specific MFA policy does that, and it is what lets your all-users policy leave guests out without a gap.
A quick reference
| Policy | Who it covers | What it does | License note |
|---|---|---|---|
| MFA for all users | Everyone, minus break-glass | Requires a second factor | Template-based, no P2 needed |
| Block legacy authentication | All users | Stops protocols that can’t do MFA | Template-based |
| Compliant device or MFA | Staff on company resources | Ties access to device health | Entra ID P1 or P2, plus Intune compliance |
| Block by location | Everyone except travelers | Denies sign-ins from countries you don’t serve | Named locations |
| Sign-in risk and user risk | All users | Challenges or forces password change on risky behavior | Entra ID P2 |
Licenses and roles: what you need
The most common question after “what is it” is what it costs to turn on. Three facts cover most small businesses.
- Entra ID P1 is the usual entry point. Microsoft’s licensing page says P1 is included in Microsoft 365 Business Premium, the plan aimed at small and mid-sized businesses. If you are on Business Basic or Standard, check your tenant before you plan.
- Device-based policies need more than the license. Microsoft’s Intune documentation says they require Entra ID P1 or P2, a Security Administrator or Conditional Access Administrator role, and configured Intune device-compliance policies.
- Risk-based rules need P2. Microsoft’s templates list the sign-in-risk and high-risk-user password-change policies as requiring Entra ID P2. Insider-risk policies need Microsoft Purview.
Microsoft changes plan names and bundles over time, so confirm your own tenant’s licenses in the admin center before you design around a feature. If you want help reading what you own, our Microsoft 365 services cover licensing and administration for small businesses.
Risk-based policies: when to add them
Sign-in risk and user risk are Microsoft’s own scoring of how likely a sign-in or an account is compromised. A risk-based policy might require MFA at medium risk, or force a password change when an account is flagged as high risk.
These are worth adding once your baseline is stable and you hold P2. Before that, three plain policies deliver most of the protection. The pattern is familiar from other industries: businesses that handle sensitive filings online often publish a security policy for online filing that explains how accounts and data are protected. Your Conditional Access set is the technical backbone of the same promise to your own customers.

Best practices for rollout without lockouts
The fastest way to turn a security project into an outage is enforcing a tenant-wide policy on a Monday morning. Use this sequence.
- Create two emergency-access (break-glass) accounts first. Microsoft’s guidance is to exclude them from policies that block or restrict sign-in, because an enforced policy could stop them in the very emergency they exist for. Protect them with a phishing-resistant method such as a passkey (FIDO2), and store the details offline.
- Start in report-only mode. Microsoft advises creating template policies in report-only mode, then testing and monitoring their usage before turning them on. Report-only logs what would have happened without blocking anyone.
- Read the sign-in logs for a week or two. Look for shared mailboxes, scanners, old apps and travelers that would have been blocked.
- Handle service accounts separately. Microsoft recommends addressing service accounts and service principals with workload-identity controls or managed identities instead of user MFA rules.
- Enforce one policy at a time, to a pilot group first. Start with IT and a few willing staff, then widen.
- Tell people before it happens. A two-line email about the new prompt prevents most help desk calls.
- Review quarterly. Overlapping policies are easy to accumulate. Remember they stack, so one forgotten rule can block someone for reasons nobody remembers.
Two mistakes recur. The first is excluding too many people “just for now” and never removing them. The second is trying to build a policy for every scenario on day one. A small, well-tested set beats a clever one nobody understands.
Policies also work best alongside the rest of your identity hygiene. Our password policy checklist, the least privilege access guide, and the Microsoft Secure Score walkthrough show how access rules connect to the wider picture. For attacks that exploit approval prompts, read about MFA fatigue attacks.
What Conditional Access cannot do
It controls access decisions. It does not clean an infected laptop, filter email, or back up your files. It also depends on accurate inputs: a device-compliance rule only works if devices are enrolled and compliance policies are configured, and a location rule only works if your named locations are current. Treat it as one layer in a security plan, next to endpoint protection, email filtering, backup and staff training.
A realistic starter plan for a 50-person company
Here is how a first month often looks when someone owns it:
- Week 1: Inventory licenses, admin roles and any legacy mail clients. Create break-glass accounts.
- Week 2: Deploy MFA for all users and legacy-authentication blocking in report-only mode. Review logs.
- Week 3: Enforce both for a pilot group, then everyone. Add a guest MFA policy.
- Week 4: Enroll devices in Intune, set compliance rules, and add a compliant-device-or-MFA policy in report-only mode.
After that, location blocking and risk-based rules follow at your own pace. The work is not hard, but it needs someone who watches the logs and answers questions when a prompt surprises a user.
Where Mavericks fits

Most owners we talk to do not want to become Entra administrators. They want sign-ins protected and the phone not to ring when something changes. Mavericks Office Solutions operates as an outsourced IT department, combining managed IT services with cybersecurity and Microsoft 365 support, backed by 24/7 monitoring and a USA-based help desk in Ohio with an average response under 12 minutes.
If you want your access policies designed, tested and watched by the same team that answers your help desk calls, start with our cybersecurity services.

One provider for IT, security, voice, print and cloud means your access rules, your phones and your devices are planned together, not by four vendors who never talk.
Perspective
Conditional Access is where small businesses get the best security return for the least spending, and it is also where well-meaning DIY projects cause outages. The technology is not the hard part. The hard part is the discipline: break-glass accounts, report-only testing, log reviews, and a clear owner when a policy needs to change.
That is why we treat it as part of running a business’s IT, not as a one-time setup. When the same people monitor your environment around the clock and answer your help desk locally, a blocked sign-in becomes a quick fix instead of a lost morning. Our view is simple: the best policy set is the one that is documented, tested, and maintained by someone accountable for it.
If you are in Ohio or Michigan and want that accountability without hiring a full-time security engineer, that is exactly the gap we are built to fill.
Jeffrey
FAQ
What is an example of a Conditional Access policy?
The simplest is “require MFA for all users on all cloud apps,” with your emergency-access accounts excluded. Others include blocking legacy authentication, requiring a compliant device for company data, and blocking sign-ins from countries where you have no staff. Microsoft publishes these as ready-made templates.
What license do I need for Conditional Access policies?
Most small businesses use Microsoft Entra ID P1, which is included in Microsoft 365 Business Premium. Risk-based policies such as sign-in risk require Entra ID P2. Confirm what your tenant holds before planning.
Where do I find Conditional Access policies?
Sign in to the Microsoft Entra admin center and open the Conditional Access section under Protection. You need an admin role such as Conditional Access Administrator or Security Administrator to create or change policies, as noted in Microsoft’s MFA procedure.
Can Conditional Access policies lock me out?
Yes, if you enforce a policy without testing it. Exclude two break-glass accounts, run new policies in report-only mode, and read the sign-in logs before enforcing. This is the sequence Microsoft recommends.
Sources
- Build Conditional Access policies in Microsoft Entra
- Microsoft Entra Conditional Access overview (Microsoft Learn)
- Microsoft Entra Conditional Access product page
- Conditional Access templates
- Require MFA for all users with Conditional Access
- Conditional Access: Block access example
- Device-based Conditional Access with Intune
- Microsoft Entra licensing
- Manage emergency access accounts in Microsoft Entra ID