In this guide · 7 sections
- 01Security defaults vs Conditional Access
- 02Before you start: break-glass accounts and report-only mode
- 03The 5 Conditional Access policies worth turning on
- 04How to create a policy in the Entra admin centre
- 05Mistakes that lock people out or leave gaps
- 06Do it yourself or get help?
- 07Frequently asked questions
Short answer
You need Microsoft Entra ID P1, which comes with Microsoft 365 Business Premium. Start with five policies: MFA for all users, stronger MFA for admins, block legacy authentication, require a managed device for company data, and block countries you never work from. Test each in report-only mode first.
Security defaults vs Conditional Access
Every Microsoft 365 tenant can use security defaults: a free, one-switch package that requires all users to register for MFA, requires admins to use MFA every time, and blocks legacy authentication protocols. Microsoft says these protections stop the vast majority of common identity attacks, and recommends them for tenants on the free tier of Entra ID.
Conditional Access lets you write your own rules instead. Microsoft's overview describes policies as if-then statements built from signals (user, location, device, app, risk) and decisions (block, require MFA, require a compliant device, and more). It requires Microsoft Entra ID P1 licences.
Security defaults
Free- One switch, no design work
- MFA registration for everyone
- MFA every time for admins
- Blocks legacy authentication
- No exceptions or device rules
Best for: Business Basic and Standard tenants.
Conditional Access
Needs Entra ID P1- Rules per user, app, device and location
- Can require managed or compliant devices
- Can require phishing-resistant methods for admins
- Exceptions for break-glass accounts
- Needs testing and upkeep
Best for: Business Premium tenants and anyone handling sensitive data.
Microsoft's Business Premium guidance lists Business Premium as including Entra ID P1, and says not to turn off security defaults unless you are switching to Conditional Access policies. Our guide on whether Business Premium is worth it covers the cost side.
Before you start: break-glass accounts and report-only mode
A badly scoped policy can lock every admin out of the tenant. Two habits prevent that.
Create two emergency access accounts
Microsoft's emergency access guidance says to create two or more cloud-only accounts on the onmicrosoft.com domain, with Global Administrator rights.
Protect them with a different strong method
Use a phishing-resistant method such as a FIDO2 passkey on a hardware key, not the same Authenticator app your normal admin uses. Store the keys safely.
Exclude them from blocking policies
Add both accounts to a group and exclude that group from every Conditional Access policy that blocks or restricts sign-in.
Set up an alert on their use
Monitor sign-in logs for these accounts. They should almost never be used, so any sign-in deserves a look.
Create every new policy in report-only mode
Report-only evaluates the policy at sign-in and logs the result without enforcing it. Leave it a week, check the sign-in logs, then switch it on.
See Microsoft's pages on emergency access accounts and report-only mode for the details.
The 5 Conditional Access policies worth turning on
Microsoft's overview lists common policies and the admin centre offers templates for most of them. For a small business, these five deliver most of the value.
| Policy | Users | Control | Why |
|---|---|---|---|
| 1. Require MFA for all users | All users, exclude break-glass | Require MFA | Stops sign-in with a stolen password alone |
| 2. Stronger MFA for admins | Admin roles | Require phishing-resistant authentication strength | Admin accounts are the biggest prize |
| 3. Block legacy authentication | All users | Block old protocols (POP, IMAP basic, SMTP AUTH) | Legacy protocols cannot do MFA |
| 4. Require a managed device | All users, Microsoft 365 apps | Require compliant device or app protection on mobile | Company data only on devices you control |
| 5. Block countries you never use | All users, exclude break-glass | Block by location | Cuts sign-in attempts from abroad |
Policy 2 pairs well with passkeys; our passkeys guide explains how to register them. Microsoft's template for blocking legacy authentication is the quickest to deploy, but check report-only logs for old scanners, printers or apps that send email with a password first.
Policy 4 is the one that changes daily life. Microsoft's device compliance policy template assumes devices are enrolled in Intune and marked compliant. Enrol company laptops before you enforce it, and use app protection policies for staff on personal phones.
How to create a policy in the Entra admin centre
The flow is the same for every policy.
- Sign in to the Microsoft Entra admin centre as a Conditional Access Administrator.
- Go to Entra ID, Conditional Access, Policies, and select New policy or Create from templates.
- Under Users, include the target group and exclude the break-glass group.
- Under Target resources, choose All resources or the Microsoft 365 apps you want to cover.
- Set Conditions (for example locations or client apps) and the Grant control.
- Set Enable policy to Report-only, create it, and review the sign-in logs after a few days.
Name policies clearly, for example CA01 Require MFA all users, so whoever looks after the tenant next understands them.
Mistakes that lock people out or leave gaps
A good set-up
- Two break-glass accounts excluded from blocking policies
- Each policy tested in report-only before enforcement
- Devices enrolled before a compliant-device rule goes live
- A short written list of policies and exceptions
Red flags
- Security defaults turned off with no MFA policy enforced
- Admins excluded from MFA "temporarily" and forgotten
- Country blocks that also block staff travelling for work
- Dozens of overlapping policies nobody can explain
MFA alone is not the end of the story. Push-approval MFA can be abused by attackers who send repeated prompts; our guide to MFA fatigue attacks explains number matching and other defences.
Do it yourself or get help?
If you are on Business Basic or Standard, keep security defaults on; that is the right answer, not a compromise. If you have Business Premium, Conditional Access is worth the effort, but it needs careful testing and someone who will look at the sign-in logs.
Our Microsoft 365 / Google Security Lockdown (S$590) sets up break-glass accounts, the five policies above in report-only, then enforces them once the logs are clean. Device Encryption and Management (S$490) enrols laptops and phones in Intune so the managed-device policy can go live. The rest of the tenant is covered in our Microsoft 365 security checklist.
Frequently asked questions
You need Microsoft Entra ID P1. The usual way for a small business to get it is Microsoft 365 Business Premium, which Microsoft lists as including Entra ID P1 along with Intune and Defender for Business. Entra ID P1 can also be bought as a separate add-on for users on Business Basic or Standard.
No. Security defaults must be turned off before Conditional Access policies take effect, and Microsoft advises turning them off only when you are switching to Conditional Access. Build replacement MFA and legacy authentication policies in report-only mode first, then switch them on as you turn security defaults off.
It is a policy state in which Microsoft Entra evaluates the policy at every sign-in and records what it would have done, without enforcing it. You review the results in the sign-in logs. It lets you find staff, devices or old apps that would be blocked before you switch the policy on.
It is an emergency Global Administrator account used only when normal admin access fails, for example after a misconfigured policy. Microsoft recommends at least two, cloud-only on the onmicrosoft.com domain, protected with a strong method such as a hardware passkey, excluded from blocking policies, and monitored for any sign-in.
Possibly old devices and apps that sign in with only a password: some copiers that scan to email, old Outlook versions, and scripts using POP or IMAP. Run the policy in report-only mode for a week and check the sign-in logs for legacy client apps before enforcing it.