Conditional Access Explained: Sign-In Rules for Microsoft 365

How Conditional Access sign-in rules work in Microsoft 365, which license you need, and the starter policies a small professional firm should use.

Guide · By NexJen IT Solutions · Reviewed October 2026 · 6 min read
Key takeaways
Conditional Access is a set of if-then sign-in rules: if a person, device or location matches a condition, Microsoft 365 allows the sign-in, asks for more proof, or blocks it.
It requires Microsoft Entra ID P1, which is included in Microsoft 365 Business Premium, and it replaces Security Defaults rather than running alongside them.
Roll policies out in stages, starting in report-only mode, and keep tested emergency access accounts so a mistake never locks everyone out.

Sign-in rules (Conditional Access) let Microsoft 365 decide, at the moment someone signs in, whether to let them in, ask for more proof, or block them. The rules look at who is signing in, from where, on what device and to which app. For most small firms, Conditional Access is the step up from the basic protection Microsoft turns on by default, and it requires a license such as Microsoft 365 Business Premium.

Why business owners should care

A password alone no longer tells you much about who is signing in. Conditional Access lets you set rules that match your actual risk: require a second check (multi-factor authentication, or MFA) for everyone, protect administrator accounts more tightly, and refuse sign-ins from places your firm never works.

The business value is control without friction. A partner signing in from the office laptop they use every day should not face the same hurdles as an unknown sign-in from overseas. Well-designed rules keep normal work smooth and put the friction where the risk is.

How a sign-in rule works: signals and decisions

Microsoft describes each policy as an if-then statement. If certain conditions (signals) are true, then a decision applies. Policies are evaluated after the first step of sign-in, the password or passkey, is complete.

Signals Conditional Access can look at

User or group
Who is signing in. Policies can target everyone, specific groups such as partners or administrators, or exclude named accounts.
Location
Where the sign-in appears to come from, based on the network address. You can define trusted office networks or entire countries.
Device
The device platform (Windows, Mac, iPhone, Android) and whether it is marked as compliant with your device management rules.
Application
Which app or service is being opened, so you can treat email differently from, say, your accounting system's single sign-on.
Risk
Microsoft's real-time estimate that a sign-in or account is compromised. Risk-based rules need a higher license, covered below.

Decisions a policy can make

Allow
Let the sign-in proceed if no rule requires anything more.
Require MFA
Ask for a second factor, such as an Authenticator app approval or a passkey.
Require a compliant device
Allow access only from a company-managed device that meets your security rules.
Block
Refuse the sign-in. Microsoft calls this the most restrictive decision and recommends testing before using it widely.

What you need to use it

Conditional Access requires Microsoft Entra ID P1 for the users the policies cover. P1 is included in Microsoft 365 Business Premium. Business Basic and Business Standard include the free tier of Entra ID, which does not include Conditional Access.

Policies based on sign-in risk or user risk need Microsoft Entra ID P2, which Business Premium does not include on its own. As of this writing, Microsoft offers P2 through add-ons such as Microsoft Defender Suite for Business Premium or as a standalone license. Licensing changes, so check Microsoft's current documentation before you buy.

Security Defaults or Conditional Access: pick one

Security Defaults is Microsoft's free, on-or-off baseline. It requires users to register for MFA, protects admin accounts and blocks older sign-in methods. It is turned on for most newer Microsoft 365 tenants and is a sensible choice when you do not have P1.

You cannot run both. Microsoft says the two are not meant to be combined, and organizations that move to Conditional Access must turn Security Defaults off, then immediately put equivalent or stronger policies in place. The gap between those two steps should be minutes, not days.

Starter policies for a small professional firm

Take a 15-person engineering firm on Business Premium, with staff who work from the office, from home and occasionally from client sites. A practical first set of policies might look like this:

1. Require MFA for all users on all apps, excluding only your emergency access accounts.
2. Block legacy authentication. Older protocols such as POP, IMAP and basic SMTP cannot do MFA, and Microsoft reports that more than 99 percent of password spray attacks use them.
3. Protect administrator roles with stronger requirements, such as MFA every time and, where possible, phishing-resistant methods like passkeys.
4. Block sign-ins from countries your firm never works from, with a documented exception group for staff who travel.
5. Require a compliant, company-managed device for sensitive apps, such as your document management or accounting system. This depends on devices being managed with Microsoft Intune, so it usually comes after the first four.

That is five policies, not fifty. Small firms are usually better served by a short, well-documented set they understand than by a long list nobody remembers the reason for.

Roll out in stages, starting with report-only mode

Every Conditional Access policy can run in report-only mode. In that state, Microsoft evaluates the rule on each sign-in and records what would have happened in the sign-in logs, but does not enforce it. That shows you who would have been blocked or prompted before anyone is.

1. Create each policy in report-only mode.
2. Let it run for at least a week; Microsoft's own deployment guidance suggests that as a minimum.
3. Review the sign-in logs for anyone who would be blocked, such as an old scanner using basic email authentication or a staff member with an outdated phone.
4. Fix those cases, tell staff what will change and when, then switch the policy on.
5. For bigger changes, enable the policy for a pilot group first, then widen it.

Break-glass emergency access accounts

Microsoft recommends at least two emergency access accounts, sometimes called break-glass accounts. These are cloud-only Global Administrator accounts that are not tied to one person, are excluded from policies that could lock everyone out, have long, securely stored credentials, and trigger an alert whenever they are used.

Microsoft also recommends testing them regularly, at least every 90 days and whenever IT staff change. Microsoft has made MFA mandatory for its admin portals, and its emergency access guidance has been updated accordingly, so follow the current version when you set these up.

Common mistakes

• Locking yourself out: enforcing a block policy for all users, including every administrator, without testing first or keeping an emergency account excluded.
• Excluding too many people: every exception is a gap. An exclusion list that grows to include the managing partner, the office manager and a shared mailbox defeats the purpose.
• Forgetting shared and service accounts: scanners, phone systems and older apps that send email often rely on legacy sign-in and will break quietly.
• No documentation: if nobody can explain why a policy or exception exists, it will not survive the next staff change.
• Treating Conditional Access as the whole strategy: it decides who gets in, but you still need patching, endpoint protection, backup and good offboarding.

How NexJen can help

For NexJen Essentials clients on Microsoft 365 Business Premium, our security baseline includes Conditional Access, rolled out in stages: report-only first, then monitoring, then enforcement. On Business Basic or Standard, the baseline uses Security Defaults and MFA instead. The Essentials price is the same either way.

If you are not looking for managed IT, our Microsoft Entra ID and Security Posture & Compliance Assessment consulting engagements review your current sign-in settings and deliver written, risk-rated findings and a roadmap. Consulting is advisory only; any changes are quoted separately.

Common questions

Do I need Business Premium for Conditional Access?

You need Microsoft Entra ID P1 for the users the policies cover. Business Premium includes P1; Business Basic and Standard do not. P1 can also be purchased separately.

Can I use Security Defaults and Conditional Access together?

No. Microsoft says they are not meant to be combined: creating Conditional Access policies prevents you from enabling Security Defaults, and moving to Conditional Access means turning Security Defaults off. Switch it off and replace it with policies at the same time.

Will Conditional Access annoy my staff?

It should not if it is designed well. Most staff on their usual devices see an occasional MFA prompt. Report-only testing helps you find problems before anyone is blocked.

What happens if we stop paying for P1?

According to Microsoft, existing policies are not automatically deleted when the license expires, but they can no longer be edited. Plan any license change before it happens.

Want sign-in rules without the lockouts?

We can review your current sign-in settings and plan a staged Conditional Access rollout that fits how your team actually works.

Want a second opinion on your setup?

Start with a free Security Snapshot. We'll tell you honestly what we find and whether we can help.