Study guide
11.3 OAuth App Policies & Catalog Management
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
11.3 OAuth App Policies & Catalog Management
Key Takeaways Explain This Topic AI
OAuth apps that users or admins consent to can obtain delegated or application-level access to Microsoft 365 and other data without being a full “shadow SaaS website” discovery problem—consent is the risk path.
Defender for Cloud Apps OAuth app policies help investigate permissions and automate approve/revoke style governance for risky OAuth apps (built-in policy patterns; SC-300 conceptual depth).
Identity admins must review and revoke risky OAuth grants, combining Entra enterprise-app permission views with MDCA OAuth inventories.
Cloud App Catalog management includes using scores, tagging sanctioned/unsanctioned apps, and keeping catalog metadata accurate for discovery and control.
Govern third-party app consent alongside Microsoft Entra consent settings, admin consent workflows, and Conditional Access—never as a silo.
Last updated: July 2026
OAuth apps: the consent attack surface
Not every cloud risk is a website users browse through a reverse proxy. Many threats arrive as “Sign in with Microsoft” buttons and OAuth consent prompts. A user (or an admin) grants a third-party application permissions to read mail, files, contacts, or calendar. The app then accesses data via Microsoft Graph or other APIs using tokens—often without continuous interactive browsing that session policies fully cover.
On SC-300, OAuth app governance sits at the intersection of:
Microsoft Entra app registrations, enterprise applications, user consent, admin consent, and permission classification.
Microsoft Defender for Cloud Apps OAuth app detection, investigation, and OAuth app policies .
Cloud App Catalog risk context for the apps behind those OAuth clients.
Practice: /practice/azure-sc-300 . Consent fundamentals live in the enterprise apps chapter of /study-guides/azure-sc-300 . Related posture: /practice/azure-az-500 .
- Risk pattern What happens
- Over-permissioned legitimate app App requests broad Graph scopes “for convenience”
- Malicious OAuth app Phishing leads user to consent; attacker reads mail/files via Graph
- Forgotten app Project ends; OAuth grant remains years later
- Admin consent to multi-tenant app Tenant-wide impact if application permissions are huge
- User consent to low-trust publisher Data leaves without a formal SaaS procurement
- OAuth app policies in Defender for Cloud Apps
OAuth app policies in MDCA focus on threat detection and governance for OAuth applications . At exam depth:
They help you investigate which permissions each OAuth app requested.
They support automated governance patterns such as marking apps authorized/unauthorized and revoking app authorization when risk thresholds match.
Microsoft documents OAuth app policies as built-in style policy capabilities in the MDCA policy family (you work with the OAuth app governance experiences rather than inventing a brand-new protocol).
- Policy family (MDCA context) Primary purpose
- OAuth app policy Detect/govern OAuth apps and their permission risk
- Access policy Real-time access allow/block under CA App Control
- Session policy In-session activity control under CA App Control
- App discovery policy Alerts on new discovered apps (shadow IT)
- Activity / anomaly policies Behavioral detections across connected apps
Exam cue phrases: “revoking OAuth permissions,” “unauthorized OAuth app,” “apps with high permission severity,” “users consenting to risky apps,” “OAuth app policy.”
Investigation workflow (conceptual)
Open OAuth apps inventory in Defender for Cloud Apps (product navigation evolves; concept is OAuth app governance ).
Sort/filter by permission severity , community use, publisher, or app name.
Drill into an app: who consented, which permissions, last used.
Compare with business ownership—does a team claim this integration?
Revoke app authorization if unjustified or malicious; require re-consent under tighter Entra consent policy if still needed.
Document sanctioned OAuth integrations (enterprise apps with admin consent and least-privilege scopes).
- Signal Why it matters
- High privilege Graph scopes (mail read/write all, files read/write all) Large blast radius
- Many users consented Wide organizational exposure
- Unknown publisher / suspicious name Possible phishing OAuth app
- No business owner Orphaned integration
- Application permissions with admin consent Tenant-wide daemon-style access
- Review and revoke risky OAuth grants
SC-300 expects you to act , not only list apps.
Where revocation and review happen
- Surface What you do
- Defender for Cloud Apps OAuth apps Investigate severity; revoke app; apply OAuth policies
- Microsoft Entra enterprise applications Review permissions, owners, user assignment, disable sign-in
- User consent settings Restrict what users can consent to without admin
- Admin consent workflow Route requests for review instead of ad-hoc global admin clicks
- Permission classifications Mark permissions low/medium/high to drive consent policy
- Access reviews / governance (Domain 4 themes) Periodically recertify who still needs app access
- Response playbooks
- Suspected malicious OAuth app
Revoke the app’s permissions / disable the enterprise application instance.
Revoke user sessions and refresh tokens for impacted users if compromise suspected.
Review sign-in logs and MDCA activity for data access patterns.
Reset credentials / require passwordless+phishing-resistant remediation as appropriate (Identity Protection chapter linkage).
Tighten user consent settings to prevent recurrence.
Legitimate but over-privileged app
Contact the app owner/vendor for least-privilege scopes.
Reconfigure app registration permissions; re-consent with reduced scopes.
Prefer application permissions only when a daemon truly needs them; otherwise delegated least privilege.
Assign owners on the enterprise app; tag as sanctioned in catalog processes.
Orphaned app after project ends
Confirm no production dependency.
Revoke OAuth grants; delete or disable enterprise app.
Remove related secrets/certificates from any app registration you own.
Update sanctioned app inventory.
- Do Don’t
- Revoke first when malice is likely Leave “temporary” high Graph permissions forever
- Pair revoke with session revocation for compromise Assume deleting a bookmark removes API grants
Align Entra consent policy with MDCA findings Govern only in MDCA while users can still consent freely in Entra
- Least privilege for new admin consent Grant *.ReadWrite.All “so it works” without review
- Cloud App Catalog management
Section 11.1 introduced the catalog for discovery. Catalog management is the ongoing governance of how your organization treats those apps.
Scores and evaluation
Use risk scores and security attributes when approving new SaaS.
Prefer lower-risk alternatives when business function is equal.
Revisit scores when a sanctioned app’s posture changes (vendor breaches, certification changes—process maturity, not daily busywork).
Organizational tagging / stance
- Stance Meaning Follow-on controls
- Sanctioned Approved for business use SSO, CA, connected app, MDCA policies, lifecycle owner
- Unsanctioned Not allowed Block at SWG/proxy where possible; educate; revoke OAuth; discovery alerts
- Monitored Conditionally observed Discovery/session monitoring while business case develops
- Catalog hygiene tasks identity admins touch
Ensure custom domains for customized/plugin apps map so discovery and CA App Control identify the right app.
Avoid duplicate “unknown” apps when a catalog entry already exists—normalize naming in investigations.
When onboarding CA App Control apps, catalog identity helps MDCA apply the correct heuristics.
Feed catalog decisions into procurement and security architecture reviews.
- Catalog task SC-300 linkage
- Evaluate risk score before sanction Domain 3 cloud app monitoring
- Mark unsanctioned high-risk apps Shadow IT response
- Support connected app decisions API connector readiness
- Align with OAuth app risk Same vendor may appear as web app + OAuth client
- Governance alongside Microsoft Entra consent
MDCA OAuth tools complement , they do not replace, Entra consent configuration. A complete SC-300 answer often stacks both.
Entra consent controls (recap for integration)
Control Effect
Allow user consent for apps (all / verified / none from low impact, depending on settings model) How freely users grant delegated permissions
- Allow group owner consent (where applicable) Narrower consent paths for group-owned apps
- Admin consent workflow Users request; reviewers approve
- Risk-based step-up / Conditional Access Stronger auth before accessing sensitive apps
- Assignment required on enterprise apps Only assigned users can get tokens for that app instance
- Permission classifications Drive which permissions need admin consent
- Integrated governance model
Prevent — tight Entra user consent defaults; admin consent workflow; verified publishers preferred.
Detect — MDCA OAuth inventory + policies; Entra permission grant audit logs.
Respond — revoke OAuth app; disable enterprise app; revoke sessions; investigate.
Recover / harden — least-privilege re-consent; owners; catalog sanctioned list; CA App Control for browser SaaS residual risk.
Review — periodic OAuth app reviews just like privileged role reviews (Domain 4 mindset).
Gap if you only use Entra Gap if you only use MDCA
Weaker continuous OAuth risk scoring/investigation UX for some SaaS-centric views Consent still possible if Entra settings remain wide open
- Harder shadow-IT + OAuth correlation Enterprise app assignment and CA grants still needed
- Less CASB session control Directory-wide admin consent still an Entra operation
- End-to-end scenarios
Stem Best combined answer
Users install a free OAuth app that reads all mail Revoke OAuth app; tighten user consent; investigate with MDCA/Entra logs
Need approved CRM with API visibility Sanction in catalog; connect API connector; CA for sign-in; OAuth least privilege
BYOD must use web CRM without downloads CA App Control + session policy (11.2); still review OAuth mobile clients
Leadership asks for shadow IT list Cloud Discovery (11.1); then OAuth inventory for API-centric apps
App has high catalog risk score but business insists Compensating CA + session controls + limited audience + owner + monitoring—or negotiate alternative
Domain 3 MDCA wrap-up
Across this chapter you can:
Discover shadow IT and evaluate apps with the Cloud App Catalog (11.1).
Connect sanctioned apps via API connectors for depth (11.1).
Control browser sessions with Conditional Access App Control and MDCA access/session policies , and distinguish app-enforced restrictions (11.2).
Govern OAuth apps, revoke risky grants, and manage catalog stance alongside Entra consent (11.3).
That combination is how identity administrators apply Zero Trust to SaaS—not only to Microsoft 365 portals. Continue into Domain 4 identity governance topics (entitlement management, access reviews, PIM) in the next chapters of /study-guides/azure-sc-300 , and reinforce Domain 3 app skills at /practice/azure-sc-300 .