Study guide
12.2 Access Requests & Terms of Use
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
12.2 Access Requests & Terms of Use
Key Takeaways Explain This Topic AI
Users discover and request access packages through the My Access experience; admins also assign packages directly when self-service is not appropriate.
Multi-stage approval chains sequential decisions (for example manager then resource owner) with justification, timeouts, and alternate approvers to prevent stalled requests.
Terms of Use (ToU) policies present legal or acceptable-use text that users must accept; entitlement management can require ToU acceptance as part of package policy before access is granted.
Conditional Access can also require Terms of Use as a grant control for targeted apps or all cloud apps, independent of or complementary to package-level ToU.
Request lifecycle states—pending approval, approved/delivered, denied, expired, and extended—should be monitored with audit signals; expired or denied assignments remove package resource access.
Last updated: July 2026
From package design to living requests
Section 12.1 built catalogs , access packages , and assignment policies . This section is the operational loop: request → approve (possibly multi-stage) → deliver → use → extend or expire , plus Terms of Use (ToU) so legal and security acceptance is recorded before access. SC-300 loves scenarios that mix “self-service package” with “manager then app owner must approve” and “accept ToU before the partner portal opens.”
Practice request and governance stems at /practice/azure-sc-300 .
My Access and the request experience
Eligible users open the My Access portal (often referenced as myaccess.microsoft.com in Microsoft documentation and training) to:
Discover access packages they are allowed to request.
Submit requests with business justification when required.
Track pending requests and existing assignments.
Request extensions when policy allows before expiration.
Review access when they are designated reviewers (access reviews overlap).
- Actor Typical actions
- Requestor Search package, justify need, accept ToU, request extension
- Approver Approve/deny stages; may add notes
- Admin / package manager Direct-assign, cancel, troubleshoot stuck requests
- Catalog owner Adjust resources/packages when delivery fails due to missing resources
Discovery depends on policy. If the user’s identity is outside the assignment policy’s requestor scope (wrong tenant, not in allowed group, not in connected org), the package will not appear as requestable—even if the package “exists” in the tenant.
- Managing access requests
- Happy path
User requests package (optional justification + ToU acceptance).
Policy evaluates auto-approve vs approval required .
Approvers complete stage(s).
Entitlement management delivers assignments: group membership, app assignment/role, SharePoint site access.
User signs in; Conditional Access and other controls still apply at authentication time.
Near expiration, user may request extension if allowed.
On expiry, denial, or admin removal, resources are revoked from the package assignment path.
Admin operations
- Operation When used
- Direct assign HR joiners, break-fix project adds, populations without self-service
- Approve / deny on behalf (where role allows) Stuck queues, executive escalations
- Remove assignment Offboarding mid-project, compromise, role change
- Update policy Change duration, approvers, requestor scope
- Monitor requests SLA for approvals, abandoned requests
Always prefer removing the package assignment (or letting it expire) over surgically deleting only one of three resources when the package is the system of record—partial manual cleanup causes drift.
Request states (conceptual)
- State Meaning
- Pending approval Waiting on one or more stages
- Approved / delivering / delivered Access should appear on resources
- Denied No resource grants from this request
- Expired Time box ended; access removed
- Extended New end date after approved extension
- Canceled / removed Admin or process ended assignment early
Troubleshooting “I was approved but cannot open the app” is not only entitlement management: check app assignment , licensing , SharePoint sharing , guest redemption , and Conditional Access failure in sign-in logs .
Multi-stage approval
Multi-stage approval sequences decisions so no single rubber stamp grants high-value access.
Typical stage designs
- Stage 1 Stage 2 Business intent
- Requestor’s manager Resource / application owner Cost/need check then technical least privilege
- Business sponsor Security / compliance group Partner access with risk review
- Project lead Data owner Project membership plus sensitive site
Configuration ideas SC-300 expects you to reason about:
Order matters — stage 2 does not run until stage 1 approves.
Approver sets — specific users, groups, manager, or other supported sponsor targets.
Justification — requestor must explain why access is needed.
Timeouts — unanswered requests should not hang forever; policies can escalate, deny, or follow configured timeout behavior.
Alternate approvers — coverage when primary is on leave.
No approval only when risk is truly low (rare for external high-value packages).
Multi-stage vs single-stage vs auto-approve
- Mode Friction Control
- Auto-approve Lowest Weakest governance; use for low-risk baselines only
- Single-stage Medium Good default for many internal packages
- Multi-stage Highest Partner, regulated data, or dual-control needs
Exam story: “Contractor requests Finance package; line manager confirms engagement; finance application owner confirms least-privilege app role” → two-stage approval , not auto-approve.
Extensions as a second control plane
Expiration without extension forces a conscious renewal. Best practice for external packages:
Short initial duration (for example 30–90 days).
Allow extension requests.
Require approval on extension (often same multi-stage or a simpler re-approval).
Optionally couple with access reviews so long-lived assignments face periodic attestation even between extension events.
Terms of Use (ToU) policies
Terms of Use are Microsoft Entra policies that present PDF/content for acceptable use, privacy, or legal conditions . Users must accept (and can be required to re-accept on a schedule) before access proceeds under the controls that reference the ToU.
Create and configure ToU (concepts)
Create a Terms of Use policy object in Entra (Identity Governance / Conditional Access related experiences depending on portal navigation).
Upload the PDF (or configured content) in required languages if multi-language is needed.
Configure options such as:
Require users to expand the terms / consent UI behaviors as offered.
Expire acceptances so users re-accept periodically (for example annually).
Record who accepted and when for audit.
Attach the ToU where enforcement is required:
Conditional Access grant control : Require terms of use.
Entitlement management access package assignment policy: require acceptance as part of requesting/receiving the package.
Attachment point When it fires Best for
Conditional Access At sign-in to targeted cloud apps when policy matches Tenant-wide or app-wide legal gate (all M365, specific SaaS)
Access package policy During package request / assignment workflow Project- or partner-specific acceptance tied to an entitlement
Both User may see ToU in package flow and again at sign-in if both require it Defense in depth for regulated partner access
ToU + Conditional Access deep dive
From the Conditional Access chapter, Require terms of use is a grant control . A CA policy can:
Target All users or selected groups/guests.
Target specific cloud apps (for example a partner portal or All cloud apps).
Grant access only if ToU is accepted (optionally combined with MFA, compliant device, etc. using require all / require one of).
Exam distinctions:
ToU in CA does not put the user in a security group by itself—it blocks or allows the sign-in until acceptance.
ToU on an access package is about completing the entitlement request path and recording acceptance in the governance workflow.
Company branding is not ToU. A custom sign-in background is not legal acceptance.
ToU + entitlement management deep dive
When a package policy requires ToU:
Requestor opens the package request.
Must accept the configured Terms of Use.
Only then can the request proceed to approval/delivery per policy.
Acceptance is auditable—useful when compliance asks “did partners agree to the data handling terms?”
Design tips:
Use a partner-specific ToU on external packages rather than relying only on a generic employee ToU.
Re-expire acceptances when legal language changes materially.
Do not assume ToU replaces DLP, sensitivity labels, or CA device controls—it is an acceptance gate , not data protection.
How the pieces stack in Zero Trust
A realistic partner access stack:
Connected organization defines which external tenant/domain is in scope (section 12.3).
Access package grants least-privilege group/app/site membership after multi-stage approval .
Package ToU records project-specific acceptance.
Conditional Access requires MFA / authentication strength / device / session controls for guests on those apps.
CA ToU (optional) enforces org-wide legal terms at sign-in.
Expiration + access reviews remove stale access; guest lifecycle settings clean directory objects when appropriate.
If an exam answer only enables ToU branding or only creates a PDF without binding it to CA or a package policy, it is incomplete.
Monitoring and audit cues
Identity admins should be able to answer:
Who requested which package and when?
Which approver approved stage 1 vs stage 2?
Did the user accept ToU version X?
When did the assignment expire and were resources removed?
Why is a request still pending (approver inactive)?
Use audit logs , entitlement management reporting experiences, and request history in the admin center. For sign-in failures after delivery, pivot to sign-in logs and Conditional Access results—not only the package blade.
Exam traps
Thinking My Access requests bypass Conditional Access after approval.
Auto-approving high-risk external packages “to reduce tickets.”
Confusing ToU grant in CA with access package resource assignment .
Single Global Administrator as the only approver for every package (operational bottleneck and poor separation of duties).
Forgetting extensions without approval recreate permanent access in slow motion.
Summary of section 12.2
Access requests turn designed packages into governed assignments through My Access , admin direct assignment, and multi-stage approval with justification and timeouts. Terms of Use provide an auditable acceptance gate that you attach to package policies and/or Conditional Access grant controls . Delivery still leaves authentication under CA and other controls, and expiration/extension rules keep access from becoming silent permanent privilege. Next, section 12.3 covers connected organizations and the external user lifecycle when packages end. Keep practicing at /practice/azure-sc-300 .