You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/active-directory/privileged-identity-management/groups-activate-roles.md
+6-10Lines changed: 6 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,7 +10,7 @@ ms.topic: how-to
10
10
ms.tgt_pltfrm: na
11
11
ms.workload: identity
12
12
ms.subservice: pim
13
-
ms.date: 01/12/2023
13
+
ms.date: 3/15/2023
14
14
ms.author: amsliu
15
15
ms.reviewer: ilyal
16
16
ms.custom: pim
@@ -23,6 +23,11 @@ In Azure Active Directory (Azure AD), part of Microsoft Entra, you can use Privi
23
23
24
24
This article is for eligible members or owners who want to activate their group membership or ownership in PIM.
25
25
26
+
>[!IMPORTANT]
27
+
>When a group membership or ownership is activated, Azure AD PIM temporarily adds an active assignment. Azure AD PIM creates an active assignment (adds user as member or owner of the group) within seconds. When deactivation (manual or through activation time expiration) happens, Azure AD PIM removes user’s group membership or ownership within seconds as well.
28
+
>
29
+
>Application may provide access to users based on their group membership. In some situations, application access may not immediately reflect the fact that user was added to the group or removed from it. If application previously cached the fact that user is not member of the group – when user tries to access application again, access may not be provided. Similarly, if application previously cached the fact that user is member of the group – when group membership is deactivated, user may still get access. Specific situation depends on the application’s architecture. For some applications, signing out and signing back in may help to get access added or removed.
30
+
26
31
## Activate a role
27
32
28
33
When you need to take on a group membership or ownership, you can request activation by using the **My roles** navigation option in PIM.
@@ -76,15 +81,6 @@ You can view the status of your pending requests to activate. It is specifically
76
81
77
82
When you select **Cancel**, the request will be canceled. To activate the role again, you will have to submit a new request for activation.
78
83
79
-
## Troubleshoot
80
-
81
-
### Permissions are not granted after activating a role
82
-
83
-
When you activate a role in PIM, the activation may not instantly propagate to all portals that require the privileged role. Sometimes, even if the change is propagated, web caching in a portal may result in the change not taking effect immediately. If your activation is delayed, here is what you should do.
84
-
85
-
1. Sign out of the Azure portal and then sign back in.
86
-
1. In PIM, verify that you are listed as the member of the role.
87
-
88
84
## Next steps
89
85
90
86
-[Approve activation requests for group members and owners (preview)](groups-approval-workflow.md)
Copy file name to clipboardExpand all lines: articles/active-directory/privileged-identity-management/pim-how-to-activate-role.md
+8-10Lines changed: 8 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,14 +6,13 @@ documentationcenter: ''
6
6
author: amsliu
7
7
manager: amycolannino
8
8
editor: ''
9
-
10
9
ms.service: active-directory
11
10
ms.topic: how-to
12
11
ms.workload: identity
13
12
ms.subservice: pim
14
-
ms.date: 02/02/2022
13
+
ms.date: 3/15/2023
15
14
ms.author: amsliu
16
-
ms.reviewer: shaunliu
15
+
ms.reviewer: ilyal
17
16
ms.custom: pim
18
17
ms.collection: M365-identity-device-management
19
18
---
@@ -25,6 +24,11 @@ If you have been made *eligible* for an administrative role, then you must *acti
25
24
26
25
This article is for administrators who need to activate their Azure AD role in Privileged Identity Management.
27
26
27
+
>[!IMPORTANT]
28
+
>When a role is activated, Azure AD PIM temporarily adds active assignment for the role. Azure AD PIM creates active assignment (assigns user to a role) within seconds. When deactivation (manual or through activation time expiration) happens, Azure AD PIM removes the active assignment within seconds as well.
29
+
>
30
+
>Application may provide access based on the role the user has. In some situations, application access may not immediately reflect the fact that user got role assigned or removed. If application previously cached the fact that user does not have a role – when user tries to access application again, access may not be provided. Similarly, if application previously cached the fact that user has a role – when role is deactivated, user may still get access. Specific situation depends on the application’s architecture. For some applications, signing out and signing back in may help get access added or removed.
31
+
28
32
## Activate a role
29
33
30
34
When you need to assume an Azure AD role, you can request activation by opening **My roles** in Privileged Identity Management.
@@ -230,13 +234,7 @@ If you don't require activation of a role that requires approval, you can cancel
230
234
231
235
## Deactivate a role assignment
232
236
233
-
When a role assignment is activated, you'll see a **Deactivate** option in the PIM portal for the role assignment. When you select **Deactivate**, there's a short time lag before the role is deactivated. Also, you can't deactivate a role assignment within five minutes after activation.
234
-
235
-
## Troubleshoot portal delay
236
-
237
-
### Permissions aren't granted after activating a role
238
-
239
-
When you activate a role in Privileged Identity Management, the activation might not instantly propagate to all portals that require the privileged role. Sometimes, even if the change is propagated, web caching in a portal may cause a delay before the change takes effect. If your activation is delayed, sign out of the portal you're trying to perform the action and then sign back in. In the Azure portal, PIM signs you out and back in automatically.
237
+
When a role assignment is activated, you'll see a **Deactivate** option in the PIM portal for the role assignment. Also, you can't deactivate a role assignment within five minutes after activation.
Copy file name to clipboardExpand all lines: articles/active-directory/privileged-identity-management/pim-resource-roles-activate-your-roles.md
+7-11Lines changed: 7 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,7 +10,7 @@ ms.topic: how-to
10
10
ms.tgt_pltfrm: na
11
11
ms.workload: identity
12
12
ms.subservice: pim
13
-
ms.date: 3/1/2023
13
+
ms.date: 3/15/2023
14
14
ms.author: amsliu
15
15
ms.reviewer: rianakarim
16
16
ms.custom: pim
@@ -26,6 +26,11 @@ This article is for members who need to activate their Azure resource role in Pr
26
26
>[!NOTE]
27
27
>As of March 2023, you may now activate your assignments and view your access directly from blades outside of PIM in the Azure portal. Read more [here](pim-resource-roles-activate-your-roles.md#activate-with-azure-portal).
28
28
29
+
>[!IMPORTANT]
30
+
>When a role is activated, Azure AD PIM temporarily adds active assignment for the role. Azure AD PIM creates active assignment (assigns user to a role) within seconds. When deactivation (manual or through activation time expiration) happens, Azure AD PIM removes the active assignment within seconds as well.
31
+
>
32
+
>Application may provide access based on the role the user has. In some situations, application access may not immediately reflect the fact that user got role assigned or removed. If application previously cached the fact that user does not have a role – when user tries to access application again, access may not be provided. Similarly, if application previously cached the fact that user has a role – when role is deactivated, user may still get access. Specific situation depends on the application’s architecture. For some applications, signing out and signing back in may help get access added or removed.
33
+
29
34
## Activate a role
30
35
31
36
When you need to take on an Azure resource role, you can request activation by using the **My roles** navigation option in Privileged Identity Management.
@@ -215,7 +220,7 @@ If you do not require activation of a role that requires approval, you can cance
215
220
216
221
## Deactivate a role assignment
217
222
218
-
When a role assignment is activated, you'll see a **Deactivate** option in the PIM portal for the role assignment. When you select **Deactivate**, there's a short time lag before the role is deactivated. Also, you can't deactivate a role assignment within five minutes after activation.
223
+
When a role assignment is activated, you'll see a **Deactivate** option in the PIM portal for the role assignment. Also, you can't deactivate a role assignment within five minutes after activation.
219
224
220
225
## Activate with Azure portal
221
226
@@ -233,15 +238,6 @@ In Access control (IAM) for a resource, you can now select “View my access”
233
238
234
239
By integrating PIM capabilities into different Azure portal blades, this new feature allows you to gain temporary access to view or edit subscriptions and resources more easily.
235
240
236
-
## Troubleshoot
237
-
238
-
### Permissions are not granted after activating a role
239
-
240
-
When you activate a role in Privileged Identity Management, the activation may not instantly propagate to all portals that require the privileged role. Sometimes, even if the change is propagated, web caching in a portal may result in the change not taking effect immediately. If your activation is delayed, here is what you should do.
241
-
242
-
1. Sign out of the Azure portal and then sign back in.
243
-
1. In Privileged Identity Management, verify that you are listed as the member of the role.
244
-
245
241
## Next steps
246
242
247
243
-[Extend or renew Azure resource roles in Privileged Identity Management](pim-resource-roles-renew-extend.md)
0 commit comments