azureblog.co.uk
← SC-300 study plan
SC-300 · Implement authentication and access management

Plan, implement and manage Conditional Access

Planning policies, assignments and controls, testing with What If and report-only, session management, device restrictions, CAE, authentication context, protected actions and templates.

  • 25 min
  • 10 concepts
  • Try it yourself
  • 5-question check

Learn

Conditional Access is the Zero Trust policy engine for Entra ID. Each policy says: when these users sign in to these resources under these conditions, grant access only if these controls are met, or block.

This is the most heavily tested area of SC-300. Build a policy in the sandbox and watch how each sign-in is treated.

  1. 1

    Plan Conditional Access policies

    Plan a small set of clear policies: require MFA for all users, phishing-resistant MFA for admins, block legacy authentication, require compliant or hybrid joined devices for corporate data, and risk-based policies. Use a naming convention, exclude emergency access accounts from every policy, and start new policies in report-only mode.

    Remember: Always exclude break-glass accounts.

  2. 2

    Implement Conditional Access policy assignments

    Assignments define who: users, groups, directory roles, guests and external users, workload identities, with include and exclude. What: target resources (cloud apps, user actions such as registering security info, or authentication context). Conditions: user risk, sign-in risk, insider risk, device platforms, locations (named locations and countries), client apps (including legacy authentication) and filters for devices.

    Remember: Exclude beats include.

  3. 3

    Implement Conditional Access policy controls

    Grant controls: block access, or require MFA, an authentication strength, a compliant device, a hybrid joined device, an approved client app, an app protection policy, a password change, or terms of use. With several controls, choose require all or require one. When several policies apply, all must be satisfied, and block wins.

    Remember: Block always wins across policies.

  4. 4

    Test and troubleshoot Conditional Access policies

    What If simulates which policies would apply to a user, app, IP, country, device platform and risk. Report-only mode evaluates real sign-ins and logs the result without enforcing. The sign-in logs Conditional Access tab shows every policy's result for each sign-in. The Conditional Access insights and reporting workbook summarises impact.

    Remember: What If before, report-only during, sign-in logs after.

  5. 5

    Implement session management

    Session controls include sign-in frequency (how often users must reauthenticate), persistent browser session, app enforced restrictions (SharePoint and Exchange limit downloads on unmanaged devices), Conditional Access App Control (routes sessions through Defender for Cloud Apps) and token protection (binds tokens to the device).

    Remember: Sign-in frequency 'every time' for very sensitive apps.

  6. 6

    Implement device-enforced restrictions

    Require devices to be marked compliant by Intune or Microsoft Entra hybrid joined to reach corporate resources. Use filters for devices to target or exclude devices by attributes such as model, operating system or extension attributes, for example privileged access workstations.

    Remember: Compliant device = Intune decided it meets your rules.

  7. 7

    Implement continuous access evaluation

    Continuous access evaluation (CAE) lets supported services (Exchange Online, SharePoint Online, Teams, Microsoft Graph) react in near real time to critical events, such as a user disabled, password changed, sessions revoked, high user risk, or a move off an allowed IP, instead of waiting for the access token to expire. Strict location enforcement is an optional stricter mode.

    Remember: CAE closes the gap until the token expires.

  8. 8

    Configure authentication context

    Authentication context labels (c1 to c99) let you protect specific data and actions inside apps, not just the app as a whole. For example, a SharePoint site with a sensitivity label can require the 'Highly confidential' context, which a Conditional Access policy maps to phishing-resistant MFA and a compliant device.

    Remember: Step-up MFA for one site or action, not the whole app.

  9. 9

    Implement protected actions

    Protected actions require extra protection, through an authentication context, when admins perform sensitive tasks such as changing Conditional Access policies, deleting them, or changing cross-tenant access settings. Even with the right role, the admin must meet the policy, for example phishing-resistant MFA, before the change is allowed.

    Remember: Protect the policies that protect you.

  10. 10

    Create a Conditional Access policy from a template

    Templates create policies from Microsoft's recommendations in categories such as Secure foundation, Zero Trust, Remote work, Protect administrator and Emerging threats. They're created in report-only mode by default and exclude the current admin, so review and adjust before turning them on.

    Remember: Templates are a quick, safe starting point.

How a policy is evaluated

  1. Collect signalsUser, app, location, device, risk.
  2. Find applicable policiesEvery enabled policy whose assignments match.
  3. EnforceBlock wins; otherwise satisfy every applicable policy's grant controls.
  4. Apply session controlsSign-in frequency, app restrictions and so on.
  5. Keep watchingCAE revokes access on critical events.

Try it

Build one policy and see how it treats five sign-ins. Try blocking all users without the exclusion.

This interactive part needs JavaScript.

In the portal

  • New policyEntra admin center: Entra ID > Conditional Access > Policies > New policy
  • Create from templateEntra admin center: Entra ID > Conditional Access > Policies > New policy from template
  • What IfEntra admin center: Entra ID > Conditional Access > Policies > What If
  • Named locationsEntra admin center: Entra ID > Conditional Access > Named locations
  • Authentication contextsEntra admin center: Entra ID > Conditional Access > Authentication contexts

Key terms

Click a card to see the definition.

Check your understanding

5 questions. Score 80% or more and these skills are marked as confident in your SC-300 study plan.

  1. Two policies apply: one requires MFA, one blocks. What happens?

  2. How do you see a new policy's impact without affecting users?

  3. A SharePoint site needs stronger MFA than the rest of SharePoint. What do you use?

  4. Which feature revokes access soon after a user is disabled, before the token expires?

  5. What should every Conditional Access policy exclude?

Sources

Facts in this lesson are from Microsoft Learn. This site isn't affiliated with Microsoft.