Study guide

4.5 Access Reviews and Privileged Identity Management

Azure SC-900 Study Guide Exam

Track your progress as you read

Finished sections get a check mark.

1 Orientation: SC-900 Audience, Format, Scoring, Retakes, and Study Map

1.1 Credential Purpose and Audience 1.2 Exam Duration, Seat Duration, and Experience 1.3 Scoring, Scaled Score, and Pass-Rate Myths 1.4 Retake Policy and Certification Lifecycle 1.5 Scheduling, Price, and Delivery Options 1.6 Skills Measured and Study Map

2 Security, Compliance, and Identity Concepts: Zero Trust, Shared Responsibility, and GRC

2.1 Shared Responsibility Model 2.2 Defense in Depth and the CIA Triad 2.3 Zero Trust Model 2.4 Encryption, Hashing, and Data States 2.5 Governance, Risk, and Compliance 2.6 Identity Perimeter, Authentication, Authorization, and Federation

3 Microsoft Entra ID: Identities, Hybrid Identity, and Authentication

3.1 Microsoft Entra ID Foundations 3.2 Identity Types and Directory Objects 3.3 Hybrid Identity and Entra Connect Concepts 3.4 Authentication Methods and Sign-in Assurance 3.5 Multifactor Authentication 3.6 Password Protection, Self-Service Password Reset, and External Identities

4 Microsoft Entra Access Management, Governance, PIM, and Identity Protection

4.1 Conditional Access Purpose 4.2 Signals and Controls 4.3 Microsoft Entra Roles and Role-Based Access Control 4.4 Identity Governance, Entitlement Management, and Lifecycle Governance 4.5 Access Reviews and Privileged Identity Management 4.6 Microsoft Entra ID Protection and Risk

5 Azure Infrastructure Security: DDoS, Firewall, WAF, NSGs, Bastion, and Key Vault

5.1 Choose the Right Infrastructure Security Control 5.2 Azure DDoS Protection for Availability 5.3 Azure Firewall for Centralized Network Policy 5.4 Web Application Firewall for HTTP Workloads 5.5 Virtual Networks, Subnets, and Network Security Groups 5.6 Bastion and Key Vault for Administration and Secrets

6 Defender for Cloud: CSPM, Cloud Workload Protection, and Secure Score

6.1 Defender for Cloud Purpose and Exam Role 6.2 CSPM, Foundational Posture, and Defender CSPM 6.3 Policies, Standards, and Security Recommendations 6.4 Secure Score and Remediation Priority 6.5 Regulatory Compliance and Multicloud Posture 6.6 Cloud Workload Protection and Defender Plans

7 Microsoft Sentinel: SIEM, SOAR, Analytics, Hunting, Workbooks, and Playbooks

7.1 Sentinel as SIEM and SOAR 7.2 Data Connectors and Security Signals 7.3 Analytics Rules, Incidents, and Detection 7.4 Workbooks for Visual Review 7.5 Hunting, KQL Awareness, and Notebooks 7.6 Automation Rules and Logic Apps Playbooks

8 Microsoft Defender XDR: Office, Endpoint, Cloud Apps, Identity, Vulnerability, and Threat Intelligence

8.1 Defender XDR Suite and Microsoft Defender Portal 8.2 Defender for Office 365 8.3 Defender for Endpoint 8.4 Defender for Cloud Apps 8.5 Defender for Identity 8.6 Vulnerability Management and Threat Intelligence

9 Microsoft Purview, Service Trust, Privacy, Compliance Manager, and Compliance Score

9.1 Service Trust Portal and Assurance Resources 9.2 Privacy Principles and Microsoft Priva 9.3 Microsoft Purview Portal 9.4 Compliance Manager Assessments 9.5 Compliance Score and Improvement Actions 9.6 Scenario Selection for Trust, Privacy, and Compliance Manager

10 Microsoft Purview Data Classification, Labels, DLP, Retention, eDiscovery, and Audit

10.1 Data Classification Foundations 10.2 Content Explorer and Activity Explorer 10.3 Sensitivity Labels and Label Policies 10.4 Data Loss Prevention 10.5 Retention, Records Management, and Label Policies 10.6 eDiscovery, Audit, and Insider Risk Management

11 SC-900 Product Selection Playbooks and Common Microsoft Rebrand Traps

11.1 Read the Scenario Before Picking a Product 11.2 Entra Playbook for Identity, Access, and Governance 11.3 Defender Playbook for Protection, Detection, and Posture 11.4 Sentinel Playbook for SIEM, SOAR, and Hunting 11.5 Purview Playbook for Compliance, Data, and Risk 11.6 Renamed Products and Similar-Name Traps 11.7 Microsoft Learn Practice Assessment Review Loop

12 Final SC-900 Review, Timed Practice, Exam Day, and Next Certification Path

12.1 Domain-Weighted Final Review Plan 12.2 Timed Practice and Pacing 12.3 Exam Sandbox and Question Experience 12.4 Exam-Day Logistics and Boundaries 12.5 Scoring, Retakes, and After-Exam Decisions 12.6 Final Memory Check and Scenario Drills 12.7 Next Certification Path After SC-900

4.5 Access Reviews and Privileged Identity Management

Key Takeaways Explain This Topic AI

Access reviews periodically recertify whether users still need access to groups, apps, or roles, and can auto-remove access that is not approved.

Privileged Identity Management (PIM) provides just-in-time, time-bound, approval-based activation of privileged roles to reduce standing administrative access.

An eligible assignment requires the user to activate the role before use; an active assignment grants the privilege permanently with no activation step.

PIM activation can require MFA, justification, approval, and a time limit, and every activation is logged for audit.

Access reviews and PIM are both Entra ID Governance (P2/Governance) capabilities that enforce least privilege but solve different problems.

Last updated: June 2026

Access reviews recertify continued need

Access reviews answer one governance question: should this identity still have this access? Access that was appropriate when granted often becomes stale as people change roles, projects close, and guests linger. An access review campaign asks designated reviewers — managers, resource owners, or the users themselves (self-review) — to confirm or deny each person's continued access.

Reviews can target group memberships , access package assignments , application assignments , and Microsoft Entra and Azure role assignments (including PIM-eligible roles). Key automation features the exam may reference:

Auto-apply results — denied or unreviewed access is automatically removed when the review ends.

"If reviewers don't respond" — admins choose to leave access unchanged, remove it, or take system recommendations.

Recommendations — the system suggests removing access for users who have not signed in recently.

Access reviews are part of Entra ID Governance / P2 and directly support least privilege by trimming accumulated access over time.

PIM and just-in-time privileged access

Microsoft Entra Privileged Identity Management (PIM) manages, controls, and monitors access to privileged roles . Standing admin rights are dangerous: an always-on Global Administrator is a permanent high-value target. PIM's answer is just-in-time (JIT) access — administrators hold a role potentially but must activate it only when needed, for a limited time.

When a user activates an eligible role, PIM can require:

  • Activation requirement Effect
  • Multifactor authentication Re-prove identity at elevation time
  • Justification Record a business reason
  • Approval A Global Admin or Privileged Role Admin must approve
  • Maximum duration Access auto-expires (e.g., after 8 hours)
  • Ticket information Tie activation to a change ticket

Every activation, approval, and deactivation is logged , giving a full audit trail. PIM applies to Entra roles , Azure resource (RBAC) roles , and PIM for Groups . It requires Microsoft Entra ID P2 (or the Governance add-on).

Eligible versus active assignments

The single most-tested PIM concept is the difference between eligible and active assignments:

An eligible assignment means the user is allowed to use the role but must perform an action — activation (and possibly approval) — before the privilege applies. This delivers just-in-time access.

An active assignment means the user has the role's privileges permanently , with no activation step required. This is standing access.

Both eligible and active assignments can additionally be permanent or time-bound (with a start/end date). The least-privilege ideal is eligible + time-bound : the admin activates only when needed, and even the eligibility expires on a date.

  • Activation needed? Privilege state
  • Eligible Yes — activate (JIT) Available on demand, time-limited
  • Active No Standing/always-on

If a question describes "the admin must request and be approved before gaining the role," that is eligible . "The admin always has the privilege" is active .

Comparing the two governance jobs

Access reviews and PIM both serve least privilege but attack different problems. Access reviews look backward at existing access and ask if it should continue. PIM controls how privileged access is obtained and held , reducing standing power through JIT activation. They are complementary — PIM can even generate access reviews of who is eligible for privileged roles.

"Recertify whether users still need their group/app access" → access reviews .

"Reduce always-on admin rights with on-demand, approved, time-limited elevation" → PIM .

"Require stronger proof at sign-in" → MFA / authentication (not these).

"Decide access based on network or device context" → Conditional Access.

Both are Entra ID Governance capabilities, not Defender or Purview features.

The PIM activation lifecycle and why JIT matters

Walk through what actually happens with PIM, because the exam likes the sequence. An administrator is assigned eligible for, say, the Global Administrator role with a maximum activation of eight hours and approval required. Day to day, that admin has no Global Administrator privileges — their account is a low-value target. When they genuinely need to perform an admin task, they open PIM, activate the role, complete MFA , type a justification , and submit. A designated approver (a Privileged Role Administrator or another Global Admin) approves the request, and the role becomes active for the time window.

When the window expires, PIM deactivates automatically and the privilege disappears. Every step is recorded in the audit log and can generate alerts.

This just-in-time pattern directly attacks the biggest risk of privileged accounts: standing access . An always-active admin credential, if phished, hands an attacker permanent control. With PIM, even a stolen credential is usually eligible-only — useless without passing activation, MFA, and approval. That is why "reduce standing administrative access" is the single clearest PIM clue on the exam.

PIM also supports access reviews of privileged roles (who should remain eligible), alerts (e.g., "too many Global Admins," "admins not using PIM"), and PIM for Groups to put role-assignable groups under the same JIT model. Remember the licensing gate: PIM and ID Protection both require Microsoft Entra ID P2 , whereas plain Conditional Access needs only P1 — a distinction the exam tests directly.

Eligible → activate → MFA + justification → approval → time-limited active → auto-deactivate.

JIT removes standing access, shrinking the blast radius of stolen credentials.

PIM can review eligibility and alert on risky privileged-access patterns.

PIM and ID Protection need P2 ; Conditional Access needs P1 .