Study guide
14.2 PIM for Groups, Approval & Audit
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
14.2 PIM for Groups, Approval & Audit
Key Takeaways Explain This Topic AI
PIM for Groups provides just-in-time activation of membership (and ownership) in privileged access groups, commonly role-assignable groups that carry directory roles or feed privileged access.
Activation follows a request workflow: user requests elevation, satisfies MFA/justification/ticket, optional approvers decide, then membership is active for the configured duration.
Notifications inform requestors, approvers, and administrators about eligibility changes, pending requests, activations, denials, and expiring access.
PIM audit history records assignments, activations, approvals, and setting changes so security teams can investigate privileged activity.
Access reviews of privileged roles and privileged group membership close the loop so eligibility does not silently accumulate; the JIT admin model is incomplete without review and audit.
Last updated: July 2026
From role eligibility to group-based privileged access
Section 14.1 covered eligible vs active assignments and PIM for Entra roles vs Azure resources . Real enterprises rarely assign every privileged role to individuals one-by-one forever. They use groups —especially role-assignable groups —and PIM for Groups so membership itself becomes just-in-time. This section covers PIM for Groups , the request/approval workflow , notifications , audit history , access reviews of privileged access , and the full JIT admin model .
Practice governance stems at /practice/azure-sc-300 .
PIM for Groups explained
PIM for Groups (often discussed with privileged access groups ) lets you make users eligible for group membership or group ownership , then activate that membership for a limited time under MFA, justification, ticket, and approval settings—parallel to role activation.
Why groups matter for privilege
Pattern How privilege is granted PIM angle
Role-assignable group assigned a directory role Members receive the Entra role JIT membership via PIM for Groups reduces standing role holders
Security group nested into operational access Members get app/Azure access indirectly Activate membership only when needed
Azure RBAC via group Group assigned Owner/Contributor at a scope Combine group JIT with Azure least privilege
Approval-bound admin cohort Only activated members are in “Prod Subscription Owners” Dual control on who can even be in the group
Role-assignable groups are special: they can be assigned Microsoft Entra roles and have tighter creation controls (isAssignableToRole). SC-300 expects you to know that privileged directory roles are often assigned to a group , and that controlling membership of that group is as important as controlling the role assignment itself.
Eligible membership vs standing membership
Membership style Risk Prefer when
Permanent member of a role-assignable Global Admin group Standing privilege for all members Almost never for humans; avoid
Eligible member with PIM activation Membership (and thus role) only during activation Human privileged cohorts
Eligible owner of a privileged group Temporary ability to manage group membership Delegated group management with JIT
Active time-bound member Standing for a fixed project window Short projects when activation UX is not required but end date is
Exam cue: “Users should not permanently belong to the group that is assigned Security Administrator” → PIM for Groups eligible membership + activation settings, not permanent group adds.
Configure PIM for Groups (conceptual workflow)
Create or identify a role-assignable security group (if directory roles will be assigned to it).
Assign the directory role (or Azure RBAC) to the group , not to dozens of individuals, when that is your operating model.
Bring the group under PIM for Groups / privileged access group management.
Configure member and owner activation settings: max duration, MFA, justification, ticket, approval, notifications.
Add users as eligible members (and eligible owners if delegated management is required).
Remove standing permanent members who should be JIT only.
Test: eligible user activates → appears as member → role effective → activation ends → membership removed.
Ownership activation matters because a permanent group owner can add permanent members and bypass the spirit of JIT. Treat privileged group ownership as carefully as the role itself.
Request and approval workflow
Whether activating an Entra role , an Azure resource role , or group membership , the human flow is a request → (optional) approve → activate → expire pipeline.
End-to-end activation request
Discover eligibility — User opens PIM My roles / My groups and sees eligible roles or groups.
Request activation — Chooses duration (up to max), enters justification , optional ticket number .
Satisfy authentication — Completes MFA (and any CA authentication context requirements if configured).
Approval gate (if required):
Request enters pending state.
Approvers receive notification.
Approver approves or denies with reason.
On denial, no privilege; on approval, activation proceeds.
Active window — User performs privileged tasks; still subject to Conditional Access on sign-ins.
Expiration — Automatic removal of role/membership at end of duration; user may request again if still eligible.
Extend (if allowed by product behavior and settings) — Treated as a governed re-authorization, not silent infinite access.
Approver design patterns
Pattern Stage idea Use
No approval Activate after MFA + justification Lower-risk roles (for example limited Helpdesk variants) when residual risk is accepted
Single approver group Security ops or identity ops queue Most privileged operational roles
Dual control Sensitive Tier-0 roles require approval by a group that is not the requestor alone Global Administrator, Privileged Role Administrator, root MG Owner
Manager-style (where supported by process) Business approval plus security Less common for Tier-0; more for business-privileged groups
Anti-pattern: only one Global Administrator who is both the sole eligible admin and the sole approver with no monitoring—approval theater without separation.
Pending requests and operations
- Admin action When
- Approve / deny Normal dual-control path
- Cancel request Requestor no longer needs access
- Force remove activation / end assignment early Compromise, mistaken approval, role change
- Adjust settings mid-flight Tighten duration or require approval after an incident
- Add alternate approvers Vacation coverage so requests do not stall
Stalled approvals are an operational risk: users escalate for standing permanent access “because PIM is too slow.” Fix the approver roster and SLAs , not by disabling approval on Global Admin.
Notifications
PIM notification settings keep humans in the loop so privilege is never silent.
- Event class Who typically is notified Why it matters
- Assignment granted (eligible/active) Assignee, admins Confirms who became eligible
- Activation request pending Approvers Dual control can respond
- Activation approved/denied Requestor Closes the loop
- Activation successful Requestor, optionally admins/security Awareness of live privilege
- Activation nearing expiration Requestor Finish work or re-request deliberately
- Role setting changes Privileged role admins Detect weakening of controls (approval turned off)
Exam design answers often include configure alerts/notifications for privileged activations—not only “set eligible.” Pair notifications with SIEM/export of audit logs in larger environments (monitoring chapter).
Analyze PIM audit history
PIM audit history (and related Microsoft Entra audit logs for role assignment activities) answers investigatory questions:
Who was made eligible or active for Global Administrator last quarter?
Who activated Privileged Role Administrator at 02:00 UTC, and what justification did they enter?
Which approver approved a subscription Owner activation?
When were role settings changed to remove the approval requirement?
Did a contractor’s eligible assignment end on the contract date?
- Signal Use
- Assignment history Joiner/mover/leaver of privilege eligibility
- Activation history When privilege was actually used
- Approval history Dual-control evidence
- Setting change history Detect control degradation
- Export / Log Analytics (broader monitoring) Long-term retention and correlation with sign-ins
SC-300 cue: “Investigate who elevated last night” → PIM audit / activation history , not company branding and not only Secure Score.
Correlate with sign-in logs when the question is about how they authenticated (MFA method, location, risk) after or during elevation. Audit tells you privilege state changes ; sign-in logs tell you authentication context .
Access reviews of privileged roles and groups
Just-in-time activation does not remove the need to ask: should this person still be eligible at all? That is access reviews applied to privileged access.
What to review
Review target Question reviewers answer
Microsoft Entra role assignments (eligible and active) Does this user still need eligibility for Security Administrator?
Azure resource role assignments under PIM Does this engineer still need Owner eligibility on Subscription X?
Privileged group membership / eligibility Should they remain eligible for the Tier-0 admin group?
- Guest privileged access (if ever present) Guests almost never need standing directory admin eligibility
- Review outcomes
- Decision Effect
- Approve Keep assignment/eligibility
- Deny / remove Lose standing or eligible privileged access
- Don’t know / escalate Follow review policy (often remove or second-stage)
- Require re-activation hygiene Even if eligibility remains, activations stay time-boxed
Recommended cadence for exam-level design: frequent reviews for Global Administrator and Privileged Role Administrator eligibility (for example monthly), slightly longer for lower-privilege admin roles, always with multi-stage or fallback reviewers so reviews complete. Link this to the access reviews chapter: same engine, higher criticality population.
Why reviews fix “eligible forever” drift
Without reviews, every project leaves behind eligible Global Admins “just in case.” Eligibility still expands the set of people who can request elevation (and who might be phished into approving or social-engineering approvers). JIT + reviews beats JIT alone .
The just-in-time admin model (end-to-end)
Assemble the full SC-300 story:
Inventory standing privileged assignments (Entra + Azure + privileged groups).
Reduce permanent active human admins; convert to eligible .
Harden role settings — short duration, MFA, justification, ticket, approval on Tier-0.
Use groups thoughtfully — role-assignable groups + PIM for Groups for cohort management.
Operate workflow — request, approve, activate, expire; monitor stalled requests.
Notify security on elevations and setting changes.
Audit activations and assignment changes; export for retention.
Review eligibility on a schedule; remove movers/leavers.
Complement with Conditional Access for admin portals, Identity Protection risk, and break-glass design (next section).
Never use entitlement-management employee packages as a substitute for PIM on Global Administrator.
- Control Primary job
- PIM eligibility Who may elevate
- Activation settings How elevation happens
- Approval Dual control
- Notifications + audit Visibility
- Access reviews Who should remain eligible
- Conditional Access Authentication quality for admin sessions
- Break-glass Emergency when JIT/CA paths fail
- Common exam traps
- Permanent members of a group that is assigned Global Administrator “because groups are best practice.”
Turning on PIM but never reviewing eligibility lists.
Approvers who never receive notifications and ignore pending requests until business demands permanent access.
Investigating privilege only in sign-in logs while ignoring PIM activation audit .
Using entitlement management alone for temporary Global Admin.
Forgetting group owner eligibility can undermine member JIT controls.
Summary of section 14.2
PIM for Groups extends just-in-time control to membership and ownership of privileged access groups, including role-assignable groups that carry directory roles. Activations follow a request and approval workflow with MFA, justification, tickets, and notifications. PIM audit history provides evidence of assignments, elevations, approvals, and setting changes. Access reviews of privileged roles and groups prevent eternal eligibility. Together they implement a complete just-in-time admin model with dual control and continuous attestation. Next, section 14.3 covers break-glass emergency access accounts —the controlled exception path when normal admin systems fail. Keep practicing at /practice/azure-sc-300 .