Study guide

7.3 Auth Context, Protected Actions, Templates & Troubleshooting

Exam SC-300: Microsoft Identity and Access Administrator Exam

Track your progress as you read

Finished sections get a check mark.

1 Introduction & Exam Overview

1.1 Current Exam Facts & Logistics 1.2 Audience Profile, Zero Trust & Role Scope 1.3 Skills Measured & Study Map

2 Entra Tenant Administration

2.1 Tenant Properties, Domains & Company Branding 2.2 Built-in & Custom Roles, Effective Permissions 2.3 Administrative Units

3 Users, Groups, Licenses & Devices

3.1 Create, Configure & Manage Users 3.2 Groups & Custom Security Attributes 3.3 Licenses, Bulk Operations & Device Join

4 External Identities & Cross-Tenant Access

4.1 External Collaboration & Guest Lifecycle 4.2 Cross-Tenant Access Settings 4.3 Cross-Tenant Sync & External Identity Providers

5 Hybrid Identity

5.1 Entra Connect Sync vs Cloud Sync 5.2 PHS, PTA & Seamless SSO 5.3 AD FS Migration & Connect Health

6 Authentication Methods & MFA

6.1 Authentication Methods Portfolio 6.2 MFA, SSPR & Password Protection 6.3 Passwordless, Session Control & Entra Kerberos

7 Conditional Access

7.1 Planning, Assignments & Controls 7.2 Session Management, Device Restrictions & CAE 7.3 Auth Context, Protected Actions, Templates & Troubleshooting

8 Identity Protection & Global Secure Access

8.1 User Risk & Sign-in Risk 8.2 MFA Registration Campaigns & Risky Workloads 8.3 Global Secure Access

9 Workload & Managed Identities

9.1 Selecting Identities for Apps & Azure Workloads 9.2 Create, Assign & Use Managed Identities 9.3 Service Principals Fundamentals

10 Enterprise Apps & App Registrations

10.1 Enterprise Applications Integration 10.2 App Registrations, API Permissions & App Roles 10.3 Application Proxy & Consent

11 Microsoft Defender for Cloud Apps

11.1 Cloud Discovery & Connected Apps 11.2 CA App Control & Session Policies 11.3 OAuth App Policies & Catalog Management

12 Entitlement Management

12.1 Catalogs & Access Packages 12.2 Access Requests & Terms of Use 12.3 Connected Organizations & External User Lifecycle

13 Access Reviews

13.1 Plan & Create Access Reviews 13.2 Monitor & Respond to Access Reviews

14 Privileged Identity Management

14.1 PIM for Entra Roles & Azure Resources 14.2 PIM for Groups, Approval & Audit 14.3 Break-Glass (Emergency Access) Accounts

15 Monitoring, Logs & Secure Score

15.1 Sign-in, Audit & Provisioning Logs 15.2 Diagnostics, KQL & Workbooks 15.3 Identity Secure Score

7.3 Auth Context, Protected Actions, Templates & Troubleshooting

Key Takeaways Explain This Topic AI

Authentication context is a Conditional Access target you define so sensitive applications or actions can demand step-up controls (for example stronger MFA or compliant device) without applying those controls to every sign-in.

Protected actions bind privileged directory tasks to Conditional Access policy so high-impact admin operations require satisfying CA before they execute.

Microsoft-provided Conditional Access templates accelerate baseline deployments (MFA for admins/users, block legacy auth, require compliant devices) that you still customize with exclusions and report-only pilots.

Troubleshoot CA with sign-in logs ( whicht policies applied, success/failure, grant requirements) and Conditional Access insights; What If helps simulate, but real failures need log evidence.

Common misconfigurations include missing break-glass exclusions, conflicting stacked policies, over-broad All cloud apps scopes, guest inclusion surprises, and enforcing device compliance before devices are ready.

Last updated: July 2026

Step-up access and privileged action protection

Sections 7.1 and 7.2 covered core policy anatomy and session behavior. This section completes Conditional Access for SC-300 with three high-yield features— authentication context , protected actions , and templates —plus a practical troubleshooting playbook. These topics show up when stems move beyond “require MFA for all users” into sensitivity-based step-up and admin operation guardrails .

Free practice: /practice/azure-sc-300 .

Authentication context

Authentication context (sometimes discussed as auth context values or CA authentication context) is a Conditional Access target resource type you create and name—for example c1 / “Require strong auth for payroll” or “Sensitive engineering repos.” Applications and services that support authentication context can demand that a user’s token include proof they satisfied the CA policies tied to that context.

Why auth context exists

Without authentication context, you often face a blunt choice:

Apply strong controls to entire apps (extra MFA for all of SharePoint), or

Leave sensitive actions under-protected inside a broadly allowed app.

Authentication context enables step-up authentication for sensitive data or actions inside apps that integrate with it—Microsoft 365 sensitivity label scenarios, certain application developments, and supported resource configurations can trigger “satisfy this auth context now.”

Piece Role

Define authentication context in Entra Conditional Access Creates the tag/target (id + display name + publish state)

CA policy targeting that authentication context Assigns who must meet which grants when the context is required

  • Application / label / resource configuration Requests the context when users open sensitive content or actions
  • User sign-in / step-up User completes MFA, device, or other grants; token carries satisfied context
  • SC-300 exam cues for auth context

Stem language Prefer

“Step-up MFA only when opening Highly Confidential SharePoint libraries” Authentication context + CA policy + sensitivity labeling integration (supported pattern)

“Same app, stronger controls for a sensitive action than for general use” Authentication context, not a second full-tenant MFA policy only

“Require compliant device solely for a custom app’s admin operations” App requests auth context; CA targets context with compliant device grant

Do not confuse authentication context with:

  • Authentication strengths (grant control defining method quality),
  • Authentication methods policy (which methods are enabled),
  • App roles / OAuth scopes (authorization inside the app API),

Privileged Identity Management (just-in-time role activation—complementary, not the same).

Auth context is about Conditional Access targeting for step-up ; strengths are about which factors count when CA challenges the user.

Design tips

Create a small number of well-named contexts (avoid dozens of near-duplicates).

Publish contexts only when apps are ready to request them.

Attach clear CA policies: include the right users, grant the right strength/device controls, exclude break-glass if those accounts must still perform emergency ops carefully.

Pilot with report-only where evaluation supports insight into impact.

Document which labels/apps request which context so helpdesk can interpret step-up prompts.

Protected actions

Protected actions associate certain high-impact privileged directory tasks with Conditional Access policy. The idea: even if someone already has a powerful Entra role, performing a sensitive admin action can require satisfying additional CA requirements first—reducing damage from a stolen admin session or standing privileged account misuse.

Conceptual model

Microsoft defines protected action catalog entries mapped to sensitive permissions/operations (for example changes that affect Conditional Access policies themselves, or other high-impact directory operations as documented).

You create a Conditional Access policy that targets protected actions (as the resource/action target model exposes).

When an admin attempts a covered action, Entra checks that the admin’s sign-in satisfies the policy (MFA, phishing-resistant strength, compliant device, named location, and so on).

If not satisfied, the action is blocked until step-up succeeds.

  • Goal Protected actions help by
  • Hardening Tier-0 admin operations Requiring strong auth right before sensitive configuration changes
  • Reducing “admin cookie theft” impact Forcing fresh strong auth for privileged tasks
  • Separating daily admin browsing from dangerous changes Policy can be tighter than general Azure portal MFA

Protected actions complement PIM, Privileged Access Workstations, and phishing-resistant admin CA—they do not replace least-privilege role design. On the exam, if the stem says “require Conditional Access before admins can modify Conditional Access policies / perform listed privileged directory actions,” think protected actions , not only a generic “MFA for all cloud apps” policy (though that may also exist).

Protected actions vs authentication context vs PIM

  • Feature Protects Trigger
  • Authentication context Sensitive app data/actions via apps that request context App/resource demands context
  • Protected actions Privileged directory operations in Entra Admin attempts protected operation
  • PIM Standing privileged roles Role activation eligible → active
  • CA on Azure Management Sign-in to admin portals/APIs broadly Sign-in to management apps

A mature Tier-0 design often uses all of the above : PIM for JIT roles, CA + phishing-resistant strength for admin sign-in, protected actions for sensitive directory tasks, and PAWs/compliant devices for admin endpoints.

Create policies from templates

Microsoft provides Conditional Access templates (sometimes described as template gallery / baseline policy templates) that pre-build common policies so you do not start from a blank form every time.

Common template themes:

  • Template theme Typical outcome
  • Require MFA for administrators Directory roles → MFA / stronger grants
  • Require MFA for all users Broad MFA baseline
  • Block legacy authentication Client apps legacy → block
  • Require compliant or hybrid joined device Device grant baselines
  • Require MFA for guests External identities
  • Secure security info registration User action protection
  • High-risk user / sign-in (P2) Identity Protection integrated policies
  • How to use templates the SC-300 way

Choose a template aligned to the requirement.

Customize assignments: exclude break-glass; adjust groups/roles.

Confirm cloud apps and conditions match the scenario.

Start in report-only when impact is uncertain.

Review insights; fix registration and device readiness gaps.

Enable for pilot, then broad enforcement.

Avoid enabling every template blindly—overlapping policies still stack , and users must satisfy all matching policies.

Templates are accelerators, not exemptions from planning. Wrong exam answer: “Templates automatically exclude emergency accounts and never need testing.” Right answer: templates + exclusions + report-only + monitoring.

  • Test and troubleshoot Conditional Access
  • Primary tools

Tool Best for

Sign-in logs (Entra monitoring) Real user failures: which policies applied, success/failure, MFA detail, device state, client app, IP

  • Conditional Access blade per sign-in Policy-by-policy result: not applied / report-only / success / failure
  • What If tool Simulating a hypothetical sign-in before or during design
  • Conditional Access insights and reporting Aggregate impact, report-only analytics, trend of would-block
  • Audit logs Who changed CA policies (configuration drift)
  • Identity Protection reports (P2) User/sign-in risk that feeds risk-based CA
  • Sign-in log reading order (practical)

Find the failed or unexpected sign-in by user and timestamp.

Confirm app , IP/location , device , client app , and authentication requirement .

Open Conditional Access details: list policies in scope.

Identify the policy that failed or forced an unexpected grant.

Check whether the user was included unintentionally (All users, dynamic group, directory role).

Check exclusions (break-glass should not appear in lockout scenarios as “missing exclusion”).

Validate grant feasibility: is MFA registered? Is device compliant? Is hybrid join detected?

If multiple policies apply, remember all must succeed —fixing one policy may not be enough if another still fails.

Common misconfigurations

Misconfig Symptom Fix direction

Break-glass not excluded Emergency accounts blocked; potential admin lockout Exclude emergency accounts; monitor them

Conflicting / stacked policies Users hit unexpected second MFA or blocks Simplify policy set; align grants; use report-only during redesign

All cloud apps + strict device grant too early Mass block including non-enrolled users Pilot groups; report-only; staged device enrollment

  • Guest scope surprises Partners blocked or not covered Explicit guest include/exclude; separate guest policies
  • Legacy auth still allowed MFA bypass via old protocols Block legacy authentication clients

Risk policies without P2 / Identity Protection Feature unavailable or misunderstood License and enable Identity Protection correctly

Auth strength without methods registered Users cannot satisfy phishing-resistant grant Enable methods + registration campaign + TAP recovery

Service accounts in interactive MFA policies Automation breaks Exclude carefully or use workload identity patterns

Report-only left forever False sense of security Move to On after validation

Wrong app targeted Portal still open while “M365 MFA” exists Include Microsoft Azure Management for portal admin scenarios

Guest and external identity troubleshooting

Guests often authenticate in their home tenant and are evaluated against resource tenant Conditional Access for the apps they access. Stems may include:

Guest MFA: home tenant may have satisfied MFA, but resource tenant CA might still require its own grants depending on configuration and cross-tenant access settings.

Cross-tenant access settings (trust MFA claims, trust compliant device) can reduce redundant prompts when trust is configured.

Excluding “All guests” accidentally leaves B2B users without baseline protection; including them in device compliance policies without a path to compliance locks them out.

When troubleshooting guests, always check cross-tenant access settings , CA include/exclude for external users , and the home vs resource authentication details in sign-in logs.

Conflicting policies: evaluation mental model

Conditional Access does not pick a single “winner” policy in the simple sense of firewall first-match for all cases. All applicable policies contribute requirements. If Policy A requires MFA and Policy B requires compliant device for the same user/app, the user typically must satisfy both . If any applicable policy blocks , access is blocked.

Therefore “conflicting policies” on SC-300 usually means operational conflict —overlapping designs that create unexpected friction or lockouts—not a silent random choice. Remediation is governance of the policy estate: fewer clearer policies, consistent grant combinations, documented owners, and change control via protected actions / privileged process.

End-to-end scenario synthesis

Scenario Build

New tenant hardening week 1 Templates: MFA admins, MFA users, block legacy; exclude break-glass; report-only then enforce

  • Step-up for confidential sites Authentication context + sensitivity labels + CA grants
  • Protect CA policy changes themselves Protected actions + phishing-resistant strength + compliant admin devices
  • Contractor disabled but token worries Disable account, revoke sessions, rely on CAE where supported

User claims “CA blocked me randomly” Sign-in log → policy list → failed grant → registration/device/guest cause

  • BYOD executives App protection policy grants + session controls; avoid requiring hybrid join
  • Chapter close: Conditional Access mastery checklist

Before you leave this chapter, you should be able to:

Draw a policy: assignments → conditions → grant → session.

Choose MFA vs authentication strength vs device vs MAM grants correctly.

Use report-only , What If , and sign-in logs for the right phase (design vs incident).

Exclude and monitor break-glass accounts.

Explain CAE critical events vs sign-in frequency .

Apply authentication context for step-up and protected actions for privileged directory tasks.

Deploy from templates without skipping exclusions and pilots.

Diagnose guest, device, and multi-policy failures systematically.

Conditional Access is the heaviest hands-on Domain 2 skill on SC-300. Lab it in a trial tenant: create a report-only MFA policy, run What If, enforce on a pilot group, add a device grant, configure a session frequency policy, and read the resulting sign-in log entries until the CA detail pane feels natural. Then continue into workload identities and app access topics in later chapters of this guide: /study-guides/azure-sc-300 .