Study guide

2.3 Microsoft Entra Privileged Identity Management (PIM)

Microsoft Azure Security Technologies AZ-500

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Exam Overview & Azure Security Architecture Foundation

1.1 Azure Security Engineer Role & Exam Logistics 1.2 Microsoft Cybersecurity Reference Architecture & Zero Trust Principles

2 Chapter 2: Secure Identity and Access - Authentication, MFA & PIM

2.1 Microsoft Entra ID Security, Users, and Groups 2.2 Authentication Methods, MFA, and Conditional Access Policy Design 2.3 Microsoft Entra Privileged Identity Management (PIM)

3 Chapter 3: Secure Identity and Access - RBAC & Workload Identity

3.1 Azure RBAC, Custom Roles, and Governance 3.2 Workload Identities and Managed Identities 3.3 External Identities and Cross-Tenant Collaboration

4 Chapter 4: Microsoft Entra Application Access & Consent Governance

4.1 Enterprise Applications, OAuth Permission Grants & Consent Governance 4.2 App Registrations, Permission Scopes & Service Principal Credentials

5 Chapter 5: Secure Azure Networking - Boundary & Perimeter Protection

5.1 Virtual Network Security & Micro-segmentation 5.2 Azure Firewall and Firewall Manager 5.3 Web Application Firewall (WAF) & Azure Front Door

6 Chapter 6: Secure Azure Networking - Private Access & Monitoring

6.1 Private Connectivity with Private Endpoints & Private Link 6.2 Azure Bastion & Remote Management Security 6.3 Network Perimeter Protection & Flow Monitoring

7 Chapter 7: Network Architecture, Routing & Hybrid Connectivity

7.1 Azure Virtual Network Manager, Network Groups & User-Defined Routes 7.2 VPN Gateway, ExpressRoute Encryption & Virtual WAN Secured Hub 7.3 Network Integration for App Service, Functions, App Service Environment & SQL Managed Instance

8 Chapter 8: Public and Edge Access Protection

8.1 Azure Application Gateway Security, TLS Policy & Mutual Authentication 8.2 Azure Front Door, CDN Caching & TLS for App Service and API Management

9 Chapter 9: Compute, Container & Registry Security

9.1 Azure Virtual Machine Hardening & Host Security 9.2 Azure Key Vault Deep Dive & Secrets Lifecycle 9.3 Container & Azure Kubernetes Service (AKS) Security 9.4 Azure Container Instances, Container Apps & Registry Access Control

10 Chapter 10: Storage Security, Access Methods & Data Protection

10.1 Storage Account Security & Access Controls 10.2 Selecting and Configuring Access to Azure Files 10.3 Selecting and Configuring Access to Azure Blob Storage 10.4 Storage Data Protection: Soft Delete, Versioning, Point-in-Time Restore & Backup

11 Chapter 11: Data Platform & Database Security

11.1 Azure SQL Database Security & Always Encrypted 11.2 Database Auditing & Vulnerability Assessment 11.3 Data Discovery, Classification, & Microsoft Purview Integration

12 Chapter 12: Cloud Governance, Key Lifecycle & Asset Protection

12.1 Azure Policy for Security Governance: Definitions, Initiatives, Effects & Remediation 12.2 Key Vault Backup, Recovery & Automated Key Rotation 12.3 Implementing Security Controls to Protect Backups 12.4 Security Controls for Asset Management: Locks, Tags, Resource Graph & Azure Arc

13 Chapter 13: Microsoft Defender for Cloud - Posture & Workload Protection

13.1 Microsoft Defender for Cloud & Secure Score 13.2 Defender Cloud Workload Protection (CWP) Plans 13.3 Defender for Cloud Inventory, Compliance Standards & Custom Standards 13.4 Connecting AWS and GCP Environments to Microsoft Defender for Cloud

14 Chapter 14: External Attack Surface & Vulnerability Management

14.1 Microsoft Defender External Attack Surface Management (EASM) 14.2 Agentless Scanning & Microsoft Defender Vulnerability Management for Azure VMs 14.3 Defender for Cloud DevOps Security: GitHub, Azure DevOps & GitLab

15 Chapter 15: Security Monitoring, Microsoft Sentinel & Automation

15.1 Azure Monitor Data Collection Rules & Network Security Event Monitoring 15.2 Microsoft Sentinel Data Connectors, Content Hub & Normalization 15.3 Microsoft Sentinel Workspace & KQL Threat Hunting 15.4 Sentinel Incident Management & SOAR Automation

2.3 Microsoft Entra Privileged Identity Management (PIM)

Key Takeaways Explain This Topic AI

Privileged Identity Management (PIM) implements a Just-In-Time (JIT) access model to achieve Zero Standing Privileges (ZSP) for high-privilege roles.

Eligible assignments require users to explicitly activate roles via MFA, justification, and optional approval; Active assignments grant continuous standing access.

PIM supports both Entra ID directory roles (tenant-wide scope) and Azure Resources RBAC roles (Management Group, Subscription, Resource Group scope).

PIM for Groups allows managing JIT membership or ownership of security groups that hold Azure RBAC or Entra roles via role-assignable groups.

Access Reviews automate periodic certification of privileged roles with auto-remediation, while PIM Alerts continuously monitor for stale accounts or insecure role rules.

Last updated: August 2026

2.3 Microsoft Entra Privileged Identity Management (PIM)

Privileged accounts represent the highest-value targets for cyber attackers. Holding permanent, standing administrative privileges (such as Global Administrator or Subscription Owner) creates severe risk: if an administrator falls victim to phishing or malware, attackers immediately gain unchecked control over cloud infrastructure. Microsoft Entra Privileged Identity Management (PIM) mitigates this risk by enforcing the Just-In-Time (JIT) access model and Zero Standing Privileges (ZSP) .

PIM Architecture & The Just-In-Time Model

Under traditional access management, users hold permanent active permissions. Under PIM's Just-In-Time model, users have zero standing permissions . Instead, administrators are granted eligibility for privileged roles. [ Standing State: Zero Privileges ]

  • |
  • v
  • [ User Initiates PIM Activation Request ]
  • |
  • v
  • [ Gate Checks: MFA + Business Justification + Ticket ID + Approval ]
  • |
  • v
  • [ Temporary Role Activation (e.g., 4-Hour Window) ]
  • |
  • v
  • [ Expiration Timer Triggered -> Automatic Revocation to Zero Privileges ]
  • Key Concepts

Eligible Assignment : The user is qualified to use the role, but does not possess active permissions continuously. To use the role, the user must initiate a time-bound activation request in PIM.

Active Assignment : The user possesses standing active permissions without needing to trigger activation. Active assignments can still be time-bound (e.g., active for 30 days during a contractor engagement, after which access automatically expires).

Permanent vs. Time-Bound Eligibility : Eligibility can be granted indefinitely or bounded to specific start and end dates.

Activation Settings & Workflow Rules

Administrators configure custom settings for each role managed by PIM:

Maximum Activation Duration : Restricts how long a single activation window can last (configurable from 1 to 24 hours; recommended 4 to 8 hours max).

Require Multi-Factor Authentication : Forces the user to complete an MFA prompt during activation, even if their current session already completed MFA.

Require Business Justification & Ticket Information : Enforces entering a mandatory text justification and ticket reference number from an IT Service Management (ITSM) system (e.g., ServiceNow ticket ID).

Require Approval : Routes activation requests to designated individual approvers or approval groups.

Multi-Stage Approval Workflows

For critical roles (such as Global Administrator or Key Vault Contributor ), PIM supports Multi-Stage Approval :

Stage 1 Approver (e.g., Team Lead) reviews and approves -> Stage 2 Approver (e.g., Security Operations Lead) reviews and approves -> Activation granted.

If an approver fails to respond within the approval timeout window (default: 24 hours), the request automatically cancels.

PIM for Entra Roles vs. PIM for Azure Resources

PIM governs two distinct identity and permission structures across Microsoft Azure:

Architectural Feature PIM for Microsoft Entra Roles PIM for Azure Resources (RBAC)

Permission Framework Entra Directory Roles (Global Admin, User Admin, Exchange Admin). Azure RBAC Built-in & Custom Roles (Owner, Contributor, Reader, Custom).

Resource Scope Tenant-wide Directory level. Management Group, Subscription, Resource Group, or Individual Resource level.

Target Managed Objects Directory settings, User accounts, Domains, Licenses. Virtual Machines, Storage Accounts, Key Vaults, Virtual Networks, SQL Databases.

Scope Inheritance Applies across the entire Entra ID tenant. Inherits down the Azure resource hierarchy (Management Group -> Subscription -> RG -> Resource).

Activation Token Effect Injects temporary directory role claims into user identity token. Provisions temporary RBAC Role Assignment object at target resource scope.

PIM for Groups (Privileged Access Groups)

Managing PIM activation settings independently for dozens of separate Azure RBAC and Entra roles creates heavy administrative complexity. PIM for Groups (formerly Privileged Access for Groups) simplifies this by allowing organizations to manage eligibility and activation for membership or ownership of a security group. +---------------------------------------+

  • | Role-Assignable Security Group |
  • | "Cloud Architecture Admins" |
  • +---------------------------------------+
  • / | \
  • / | \
  • v v v
  • [ Entra Role: ] [ Azure RBAC: ] [ Azure RBAC: ]
  • User Administrator Sub Contributor Key Vault Admin
  • How PIM for Groups Operates

An administrator creates a Security Group or Microsoft 365 Group with the property isAssignableToRole = true ( Role-Assignable Group ).

Entra Directory roles and Azure RBAC roles are assigned to the group.

Users are assigned Eligible Member or Eligible Owner status on the PIM Group.

When a user activates their eligibility in PIM for Groups, they are temporarily added as an active member of the group, instantly acquiring all underlying RBAC and Entra permissions assigned to that group.

Access Reviews Setup & Governance Lifecycle

To prevent "access creep" (users retaining eligible access long after changing job roles), PIM includes automated Access Reviews .

Access Review Lifecycle Phases

Scope Definition : Select target roles or groups to review (e.g., all users eligible for Global Administrator ).

Reviewer Assignment : Assigned to Self-Review, Specific Users/Groups, Group Owners, or Managers (utilizing the manager attribute from Entra ID).

Recurrence : Configured as One-time, Monthly, Quarterly, Semi-annually, or Annually.

System Recommendations : Machine learning insights display user activity (e.g., "Has not signed in within 30 days") to guide reviewers.

Auto-Remediation Execution : Configures automatic actions if reviewers deny access or fail to respond before the review period closes:

Remove Access : Revokes role assignment immediately (Best practice for Zero Trust).

Approve Access : Retains existing role assignment.

Take Recommendations : Executes the system's machine learning recommendation.

PIM Audit History & Alerts Engine

PIM logs all role assignments, activation requests, approvals, denials, and configuration changes into a non-repudiable audit log. Audit logs can be streamed directly to Log Analytics workspaces and Microsoft Sentinel.

The PIM Alerts Engine continuously monitors tenant role configurations and flags security risks:

Potential Stale Accounts : Identifies accounts holding eligible roles that have not signed in recently.

Roles Not Requiring MFA : Flags high-privilege roles configured to activate without MFA.

Excessive Active Assignments : Alerts when administrators create standing active assignments instead of eligible JIT assignments.

Step-by-Step PIM Role Activation Flow

Step # Flow Phase Actor / Engine Actions & Security Checks

Step 1 Request Initiation User Navigates to Entra PIM -> My Roles , selects eligible role, and clicks Activate .

Step 2 Parameter Entry User Configures requested activation duration (e.g., 4 hours), enters mandatory business justification and ticket ID.

Step 3 Step-Up MFA Check Entra ID Engine Verifies user session contains a fresh MFA claim; prompts for MFA if claim is missing or expired.

Step 4 Approval Routing PIM Workflow If approval is required, pauses request and sends notification to assigned approvers via email and portal.

Step 5 Approval Decision Designated Approver Reviews justification and ticket reference; approves or denies request within the 24-hour timeout window.

Step 6 Role Provisioning PIM Engine Provisions temporary active role assignment in Entra directory or Azure RBAC hierarchy; logs audit event.

Step 7 Token Refresh User User signs out and back in (or refreshes token context) to receive updated authorization claims.

Step 8 Auto-Expiration PIM Engine Duration timer expires (e.g., at 4 hours); PIM automatically revokes active assignment, restoring Zero Standing Privileges.