Privileged Identity Management
Microsoft's edit ·
Microsoft's commit message in MicrosoftDocs/entra-docs · commit 2ddaa38 · +26 −8 lines · also on GitHub
⋯ 1 unchanged line
22
title: What is Privileged Identity Management?
33
description: Provides an overview of Microsoft Entra Privileged Identity Management (PIM).
44
ms.topic: overview
5
−ms.date: 04/23/2026
5
+ms.date: 10/26/2026
66
ms.reviewer: ilyal
7
−ms.custom: pim, azuread-video-2020, content-engagement, sfi-ga-nochange, sfi-image-nochange
7
+ms.custom: pim, azuread-video-2020, content-engagement, sfi-ga-nochange, sfi-image-nochange, msecd-doc-authoring-1031
8
+ai-usage: ai-assisted
89
#Customer Intent: As an IT administrator, I want to understand what Privileged Identity Management is and how it can help secure my organization's privileged access to critical resources.
910
---
1011
# What is Microsoft Entra Privileged Identity Management?
⋯ 5 unchanged lines
1617
1718
> [!VIDEO https://www.youtube.com/embed/f-0K7mRUPpQ]
1819
20
+PIM also supports eligible and active assignments for application-defined roles through [PIM for app roles (preview)](concept-pim-for-app-roles.md). Users can activate eligible app roles when they need them and deactivate them when they finish.
21
+
1922
## Reasons to use
2023
2124
Organizations want to minimize the number of people who have access to secure information or resources, because that reduces the chance of
⋯ 7 unchanged lines
2932
3033
[!INCLUDE [entra-id-license-pim.md](~/includes/entra-id-license-pim.md)]
3134
35
+PIM for app roles (preview) requires Microsoft Entra ID Governance licenses. Microsoft Entra ID P2 alone isn't sufficient.
3236
37
+License coverage is required for users with eligible or time-bound app role assignments and for request approvers.
38
+
3339
## What does it do?
3440
3541
Privileged Identity Management provides time-based and approval-based role activation to mitigate the risks of excessive, unnecessary, or misused access permissions on resources that you care about. Here are some of the key features of Privileged Identity Management:
⋯ 8 unchanged lines
4450
- Download **audit history** for internal or external audit
4551
- Prevent removal of the **last active Global Administrator** and **Privileged Role Administrator** role assignments
4652
53
+The available capabilities depend on the PIM provider. For the app roles preview's workflows, see [PIM for app roles (preview)](concept-pim-for-app-roles.md).
54
+
4755
## What can I do with it?
4856
4957
Once you set up Privileged Identity Management, you'll see **Tasks**, **Manage**, and **Activity** options in the left navigation menu. As an administrator, you can choose between options such as managing **Microsoft Entra roles**, managing **Azure resource** roles, or PIM for Groups. When you choose what you want to manage, you see the appropriate set of options for that option.
5058
59
+For app role assignments, select **App Roles (Preview)**, and then select an application. From the application, you can manage assignments and role settings, activate your eligible roles, and review requests.
60
+
5161
:::image type="content" source="./media/pim-configure/pim-quickstart.png" alt-text="Screenshot of Privileged Identity Management in the Azure portal.":::
5262
5363
## Who can do what?
⋯ 2 unchanged lines
5666
5767
For Azure resource roles in Privileged Identity Management, only a subscription administrator, a resource Owner, or a resource User Access Administrator can manage assignments for other administrators. Users who are Privileged Role Administrators, Security Administrators, or Security Readers don't by default have access to view assignments to Azure resource roles in Privileged Identity Management.
5868
69
+For app role assignments, owners of the target service principal and users with a supported administrative role can create, update, and remove assignments. For the supported roles, see [Permissions for app role assignments (preview)](app-roles-assign.md#permissions).
70
+
71
+<!-- TODO: Confirm permissions for viewing app role assignments without managing them. Don't assume that read-only visibility requires assignment-management permissions. -->
72
+
5973
## Terminology
6074
6175
To better understand Privileged Identity Management and its documentation, you should review the following terms.
⋯ 24 unchanged lines
86100
87101
### Assign
88102
89
−The assignment process starts by assigning roles to members. To grant access to a resource, the administrator assigns roles to users, groups, service principals, or managed identities. The assignment includes the following data:
103
+The assignment process starts by assigning roles to members. To grant access to a resource, the administrator assigns roles to users, groups, service principals, or managed identities. The supported assignment subjects depend on the PIM provider. The assignment includes the following data:
90104
91105
- The members or owners to assign the role.
92106
- The scope of the assignment. The scope limits the assigned role to a particular set of resources.
⋯ 7 unchanged lines
100114
:::image type="content" source="./media/pim-configure/role-assignment.png" alt-text="Screenshot of Privileged Identity Management role assignment.":::
101115
102116
103
−For more information, check out the following articles: [Assign Microsoft Entra roles](pim-how-to-add-role-to-user.md), [Assign Azure resource roles](pim-resource-roles-assign-roles.md), and [Assign eligibility for a PIM for Groups](groups-assign-member-owner.md).
117
+For more information, check out the following articles: [Assign Microsoft Entra roles](pim-how-to-add-role-to-user.md), [Assign Azure resource roles](pim-resource-roles-assign-roles.md), [Assign eligibility for a PIM for Groups](groups-assign-member-owner.md), and [Assign app roles (preview)](app-roles-assign.md).
104118
105119
### Activate
106120
⋯ 5 unchanged lines
112126
113127
If the role requires [approval](pim-resource-roles-approval-workflow.md) to activate, a notification appears in the upper right corner of the user's browser informing them the request is pending approval. If an approval isn't required, the member can start using the role.
114128
115
−For more information, check out the following articles: [Activate Microsoft Entra roles](pim-how-to-activate-role.yml), [Activate my Azure resource roles](pim-resource-roles-activate-your-roles.yml), and [Activate my PIM for Groups roles](groups-activate-roles.md)
129
+For app roles (preview), don't assume that completing PIM activation immediately changes application access. See the [app role activation considerations](app-roles-activate.md#overview).
116130
131
+For more information, check out the following articles: [Activate Microsoft Entra roles](pim-how-to-activate-role.md), [Activate my Azure resource roles](pim-resource-roles-activate-your-roles.md), [Activate my PIM for Groups roles](groups-activate-roles.md), and [Activate app roles (preview)](app-roles-activate.md).
132
+
117133
### Approve or deny
118134
119135
Delegated approvers receive email notifications when a role request is pending their approval. Approvers can view, approve, or deny these pending requests in PIM. After the request is approved, the member can start using the role. For example, if a user or a group was assigned with Contribution role to a resource group, they can manage that particular resource group.
120136
121
−For more information, check out the following articles: [Approve or deny requests for Microsoft Entra roles](./pim-approval-workflow.md), [Approve or deny requests for Azure resource roles](pim-resource-roles-approval-workflow.md), and [Approve activation requests for PIM for Groups](groups-approval-workflow.md)
137
+For app roles (preview), approval alone doesn't confirm that the application has started granting access. See the [app role activation considerations](app-roles-activate.md#overview).
122138
139
+For more information, check out the following articles: [Approve or deny requests for Microsoft Entra roles](./pim-approval-workflow.md), [Approve or deny requests for Azure resource roles](pim-resource-roles-approval-workflow.md), [Approve activation requests for PIM for Groups](groups-approval-workflow.md), and [Approve or deny app role requests (preview)](app-roles-approval-workflow.md).
140
+
123141
### Extend and renew assignments
124142
125143
After administrators set up time-bound owner or member assignments, the first question you might ask is what happens if an assignment expires? In this new version, we provide two options for this scenario:
⋯ 1 unchanged line
127145
- **Extend** – When a role assignment nears expiration, the user can use Privileged Identity Management to request an extension for the role assignment
128146
- **Renew** – When a role assignment expires, the user can use Privileged Identity Management to request a renewal for the role assignment
129147
130
−Both user-initiated actions require an approval from a Global Administrator or Privileged Role Administrator. Admins don't need to be in the business of managing assignment expirations. You can just wait for the extension or renewal requests to arrive for simple approval or denial.
148
+For Microsoft Entra role assignments, both user-initiated actions require an approval from a Global Administrator or Privileged Role Administrator. Admins don't need to be in the business of managing assignment expirations. You can just wait for the extension or renewal requests to arrive for simple approval or denial.
131149
132
−For more information, check out the following articles: [Extend or renew Microsoft Entra role assignments](pim-how-to-renew-extend.md), [Extend or renew Azure resource role assignments](pim-resource-roles-renew-extend.md), and [Extend or renew PIM for Groups assignments](groups-renew-extend.md)
150
+For more information, check out the following articles: [Extend or renew Microsoft Entra role assignments](pim-how-to-renew-extend.md), [Extend or renew Azure resource role assignments](pim-resource-roles-renew-extend.md), [Extend or renew PIM for Groups assignments](groups-renew-extend.md), and [Extend or renew app role assignments (preview)](app-roles-renew-extend.md).
133151
134152
## Scenarios
135153
⋯ 31 unchanged lines
Microsoft's Markdown source from MicrosoftDocs/entra-docs, © Microsoft Corporation, under MIT. Changed lines with up to 3 unchanged lines around each; ChangeIntel kept this copy 18 Nov 17:04 UTC. The commit date is when the source changed, which can be hours or days before Learn published it.