Skip to content

Commit 610dbb2

Browse files
committed
Clarify IAM page for scope update 2
1 parent ffa33d7 commit 610dbb2

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/role-based-access-control/pim-integration.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ This article describes the integration of Azure role-based access control (Azure
1616

1717
## PIM functionality
1818

19-
If you have PIM, you can create eligible and time-bound role assignments using the **Access control (IAM)** page in the Azure portal. You can create eligible role assignments for users, but you can't create eligible role assignments for applications, service principals, or managed identities because they can't perform the activation steps. You can create eligible role assignments at management group, subscription, and resource group scope, but not at resource scope.
19+
If you have PIM, you can create eligible and time-bound role assignments using the **Access control (IAM)** page in the Azure portal. You can create eligible role assignments for users, but you can't create eligible role assignments for applications, service principals, or managed identities because they can't perform the activation steps. On the Access control (IAM) page, you can create eligible role assignments at management group, subscription, and resource group scope, but not at resource scope.
2020

2121
Here's an example of the **Assignment type** tab when you add a role assignment using the **Access control (IAM)** page. This capability is being deployed in stages, so it might not be available yet in your tenant or your interface might look different.
2222

0 commit comments

Comments
 (0)