Conditional Access is where your sign-in rules actually live
Conditional Access is the policy engine inside Microsoft Entra ID. Every time someone signs in, it looks at who the user is, which app they want, where they are, what device they use and how risky the sign-in looks, and then decides: allow, require MFA, require a compliant device, or block. If your company depends on Microsoft 365, these policies decide whether a stolen password becomes a breach.
The trouble is that policies drift. A vendor account is excluded "for now", a pilot policy stays in report-only mode, a new app is never added to the policy that protects the others, and nobody notices because nothing breaks. Our Conditional Access policy review reads every policy in your tenant, compares the design with Microsoft guidance and the CIS Microsoft 365 benchmark, and then checks your sign-in logs to see what really got through.
You get a clear list of gaps ranked by business risk, the exact policy changes to make, and a way to test each change safely before it affects your users.

What the Conditional Access policy review checks
Each check has a result, the evidence behind it and the fix. These are the questions we answer about your policies.
MFA for every user, every app
Whether one policy requires MFA for all users on all cloud apps, or whether coverage depends on a patchwork of smaller policies.
Legacy authentication blocked
Older protocols such as IMAP, POP and SMTP AUTH cannot do MFA. We check that they are blocked and whether legacy sign-ins still succeed.
Administrators and admin portals
Whether admin roles and the Microsoft admin portals have their own, stronger policy, ideally requiring phishing-resistant MFA.
Sign-in risk and user risk
Whether risky sign-ins and users flagged as compromised trigger MFA, a password change or a block, where your licensing supports it.
Exclusions and break-glass accounts
Who is excluded from each policy and why. Emergency access accounts should be the only standing exclusions, and they should be monitored.
Report-only and disabled policies
Policies left in report-only or off since a pilot. We show what they would have blocked so you can decide whether to switch them on.
Device and location controls
Whether corporate apps require a compliant or hybrid-joined device, and how named locations and country blocks are used.
Session controls and registration
Sign-in frequency and persistent browser settings for privileged access, and whether registering MFA methods or joining devices is protected.
From the sample report: Conditional Access findings
These rows come from the sample audit of Veltrana Logistics, a fictional company. Your report lists every finding with the affected policies and users.
| Severity | Finding (SAMPLE) | What it means |
|---|---|---|
| High | No policy responds to sign-in risk | Risky sign-ins are detected but allowed to continue without extra checks. |
| High | No policy responds to user risk | A user flagged as compromised keeps working normally until someone notices. |
| Medium | Admin portals not targeted by a policy | Some admin roles must use MFA, but no policy protects the Microsoft admin portals for everyone who can reach them. |
| Medium | Registering security information not protected | An attacker with a password alone could register their own MFA method. |
| Medium | Compliant device not required for all users | The device policy applies to one group, so most staff can sign in from any device. |
| Low | Policies with broad user exclusions | Two enabled policies exclude more than three users or groups. |
| Low | No session controls for privileged access | No policy sets sign-in frequency or turns off persistent browser sessions for admins. |
Veltrana Logistics is a fictional company; all figures are illustrative. See the full sample report.
Five steps, read-only from start to finish
Read-only access
Your Global Administrator approves our read-only audit app once, and we sign in with a Global Reader account. Nothing in your tenant is changed.
Policy inventory
We export every Conditional Access policy, named location, authentication strength and exclusion, and map which users and apps each policy really covers.
Gap analysis
We compare the policy set with Microsoft guidance and the CIS Microsoft 365 benchmark and list each gap with its business impact.
Proof from the logs
We check 30 days of sign-ins for successful single-factor, legacy-protocol and risky sign-ins that your policies should have stopped.
Safe rollout plan
Each fix comes with the order to apply it, a report-only test with the What If tool, and how to confirm it worked in the sign-in logs.
fixed · any tenant size · read-only
What you receive from this review
This review is part of the Entra ID audit. See what the price includes.
More of the Microsoft Entra ID security audit

Microsoft Entra ID security audit
The full audit this review is part of: 75 checks, sign-in analysis and the report pack.
Learn more →
Entra ID audit sample report
See real pages from all seven deliverables, for a fictional company.
Learn more →
Privileged access and PIM review
Standing admin roles, PIM settings and access reviews, checked read-only.
Learn more →
Every Conditional Access Policy Review is led by Ali Hassani, CISO
Certified CISO (C|CISO) and CISSP with 25+ years in IT, cybersecurity, compliance and infrastructure. Ali personally reviews every finding before it reaches your desk, and walks your leadership and IT team through the results.
He holds dozens of Microsoft and Cisco credentials (CCNP, CCNA, MCSE, MCITP, MCSA Security) and works on-site across Orange County, Los Angeles and Southern California, and remotely for organizations nationwide.



