Skip to main content
Five Steps for Cloud Compliance Readiness·A practical playbook for security teamsDownload
Academy · Identity and access

Conditional Access

Conditional Access is the policy engine in Microsoft Entra ID that decides at each sign-in whether to allow access, ask for more proof such as MFA, or block it, based on signals like who the user is, which app they open, where they are and what device they use. It matters because a password alone is easy to steal, and these policies are how a Microsoft 365 tenant turns "MFA is available" into "MFA is required".

How it works

A Conditional Access policy is an if-then rule. The "if" part says who and what the rule applies to: which users or groups, which cloud apps, and under which conditions such as location, device state or sign-in risk. The "then" part says what happens: block access, require MFA, require a compliant device, require a specific authentication strength, or limit the session. Microsoft evaluates the policies after the first sign-in step, so the user has already given a password when the decision is made.

Examples on each platform

  • Microsoft 365: a policy that requires MFA for every administrator role, a policy that blocks legacy authentication protocols, or a policy that lets SharePoint open only from a compliant device.
  • Azure: the Azure portal, command line and PowerShell sign in through Microsoft Entra ID as well. Microsoft documents a "Microsoft Azure Management" cloud app that a policy can target, so the same MFA requirement covers administration of subscriptions.
  • Google Cloud: there is no feature with this name. The closest idea is IAM Conditions, which limit a role grant by attributes such as the resource or the time of the request. It controls what a role can do, not how someone signs in.
  • AWS: IAM policies can carry condition keys, for example one that checks whether the caller signed in with MFA. That is a condition inside a permission, not a sign-in policy engine.

Two details that catch admins out

First, report-only mode lets you switch a policy on without enforcing it, and Microsoft reports what would have happened. Second, a policy that blocks sign-ins needs a deliberate exclusion for your emergency access accounts, otherwise a wrong rule can lock everyone out, including you.

Why it matters

Stolen and guessed passwords are the everyday way into a tenant. Microsoft recommends blocking legacy authentication because those older protocols cannot do MFA, and its own analysis found that the large majority of credential stuffing and password spray attacks use them. A tenant can have MFA switched on for users in theory and still accept sign-ins that never ask for it.

The joint NSA and CISA advisory on common misconfigurations (AA23-278A) lists weak or misconfigured MFA among the weaknesses seen again and again. Conditional Access is where that setting lives in Microsoft 365, so a missing or disabled policy is a direct gap. The opposite error is also easy to make: a policy left in report-only never protects anyone, and a group excluded "temporarily" can stay excluded.

How it compares

Conditional Access is often confused with the other ways Microsoft lets you require MFA.

TermWhat it isDifference
Conditional AccessCustom if-then sign-in policies in Microsoft Entra IDFlexible: you choose users, apps, conditions and controls
Security defaultsA preconfigured set of basic protections for tenantsA fixed bundle you switch on or off; Microsoft points tenants without Conditional Access licences to it
Per-user MFAThe older way of enabling MFA account by accountNo conditions; the user is prompted regardless of context
Device compliance (Intune)A check whether a device meets your rulesA signal that Conditional Access can use, not a sign-in policy itself
Zero TrustA security approach: verify explicitly, assume breachA principle; Conditional Access is one way to apply it

Getting started

  1. List your current policies and note which are enabled, which are report-only and which are off. Write down every group or user that is excluded.
  2. Make sure at least two emergency access accounts exist and are excluded from policies that block or restrict sign-in, as Microsoft's emergency access guidance describes.
  3. Start with the basics: require MFA for administrator roles, then for all users, and block legacy authentication.
  4. Create each new policy in report-only mode, read the results, fix the surprises (service accounts, shared mailboxes, older apps) and only then enforce it.
  5. Review exclusions and report-only policies on a regular schedule so that temporary exceptions do not become permanent.

How ConfigCobra fits

ConfigCobra's Inventory module lists the Conditional Access and other policies in a Microsoft 365 tenant, and has a built-in risk view for Conditional Access policies that are not enforced. The relation graph shows the scope of each policy, and you can export the list as CSV.

The CIS Microsoft 365 Foundations Benchmark v7.0.0 has 160 controls; its Microsoft Entra section holds 63 of them, covering MFA, Conditional Access and authentication methods. For a failing control, remediation impact analysis shows which users, groups and apps would be affected before you apply the fix. ConfigCobra is read-only and never changes your tenant.

See where your cloud stands

ConfigCobra checks Microsoft 365, Azure, Google Cloud and AWS against the CIS benchmarks, read-only, with evidence for every finding.

Get in touch

Let's talk.

Whether you're evaluating ConfigCobra, running an audit, or managing a client fleet — we respond within one business day.

Free trial