implementing-azure-ad-privileged-identity-management

name	implementing-azure-ad-privileged-identity-management
description	Configure Microsoft Entra Privileged Identity Management (PIM) to convert standing privileged assignments into eligible, time-bound roles requiring justification, MFA, and approval, covering Entra roles, Azure resource roles, and PIM for Groups, plus access reviews. Use for role-assignment audits, just-in-time admin activation, or Zero Trust identity governance in Entra/Azure AD.
domain	cybersecurity
subdomain	identity-access-management
tags	["azure-ad","pim","entra-id","just-in-time","privileged-roles","identity-governance","zero-trust"]
version	1.0
author	mahipal
license	Apache-2.0
nist_csf	["PR.AA-01","PR.AA-02","PR.AA-05","PR.AA-06"]
mitre_attack	["T1078","T1110","T1556","T1098"]
mitre_f3	{"version":"1.1","tactics":["initial-access","positioning","defense-impairment"],"techniques":[{"id":"F1006","name":"Account Takeover","tactic":"initial-access","source":"f3"},{"id":"T1110.003","name":"Brute Force: Password Spraying","tactic":"initial-access","source":"attack"},{"id":"F1005","name":"Account Manipulation","tactic":"positioning","source":"f3"},{"id":"F1005.002","name":"Account Manipulation: Add Authorized User","tactic":"defense-impairment","source":"f3"}]}

Implementing Azure AD Privileged Identity Management

Overview

Microsoft Entra Privileged Identity Management (PIM) provides time-based and approval-based role activation to mitigate risks from excessive, unnecessary, or misused access to critical resources. PIM replaces permanent (standing) privilege assignments with eligible assignments that require users to explicitly activate their role before use, with configurable duration, MFA enforcement, approval workflows, and justification requirements. This is a core component of Zero Trust identity governance in Microsoft environments.

When to Use

• When deploying or configuring implementing azure ad privileged identity management capabilities in your environment
• When establishing security controls aligned to compliance requirements
• When building or improving security architecture for this domain
• When conducting security assessments that require this implementation

Prerequisites

• Microsoft Entra ID P2 or Microsoft Entra ID Governance license
• Global Administrator or Privileged Role Administrator role
• Azure subscription for Azure resource role management
• MFA configured for all privileged users
• Microsoft Authenticator or FIDO2 key for admin accounts

Core Concepts

Assignment Types

Type	Behavior	Use Case
Eligible	User must activate the role before use; expires after configured duration	Day-to-day admin work
Active	Role is always active; no activation needed	Service accounts, break-glass accounts
Time-Bound	Either type with explicit start/end dates	Temporary project access, contractor access

PIM Activation Flow

User with Eligible Assignment
        │
        ├── Opens PIM portal → My Roles
        │
        ├── Clicks "Activate" on the desired role
        │
        ├── Provides justification and optional ticket number
        │
        ├── Completes MFA challenge (if required)
        │
        ├── [If approval required] → Notification sent to approvers
        │       │
        │       ├── Approver reviews and approves/denies
        │       └── User notified of decision
        │
        ├── Role activated for configured duration (e.g., 8 hours)
        │
        └── Role automatically deactivated when duration expires

Supported Resource Types

1. Microsoft Entra Roles: Global Admin, Exchange Admin, Security Admin, etc.