Skip to content

Commit b4d6853

Browse files
committed
address build report feedback
1 parent bbcaa82 commit b4d6853

File tree

2 files changed

+2
-2
lines changed

2 files changed

+2
-2
lines changed

articles/active-directory/privileged-identity-management/concept-pim-for-groups.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -52,7 +52,7 @@ Azure AD role-assignable group feature is not part of Azure AD Privileged Identi
5252

5353
Groups can be role-assignable or non-role-assignable. The group can be enabled in PIM for Groups or not enabled in PIM for Groups. These are independent properties of the group. Any Entra ID security group and any Microsoft 365 group (except dynamic groups and groups synchronized from on-premises environment) can be enabled in PIM for Groups. The group doesn't have to be role-assignable group to be enabled in PIM for Groups.
5454

55-
If you want to assign an Entra ID role to a group, it has to be role-assignable. Even if you don't intend to assign an Entra ID role to the group but the group provides access to sensitive resources, it is still recommended to consider creating the group as role-assignable. This is because of extra protections role-assignable groups have – see [“What are Azure AD role-assignable groups?”](#what-are-azure-ad-role-assignable-groups) in the section above.
55+
If you want to assign an Entra ID role to a group, it has to be role-assignable. Even if you don't intend to assign an Entra ID role to the group but the group provides access to sensitive resources, it is still recommended to consider creating the group as role-assignable. This is because of extra protections role-assignable groups have – see [“What are Entra ID role-assignable groups?”](#what-are-entra-id-role-assignable-groups) in the section above.
5656

5757
<!IMPORTANT>
5858
> Up until January 2023, it was required that every Privileged Access Group (former name for this PIM for Groups feature) had to be role-assignable group. This restriction is currently removed. Because of that, it is now possible to enable more than 500 groups per tenant in PIM, but only up to 500 groups can be role-assignable.

articles/active-directory/privileged-identity-management/pim-apis.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -31,7 +31,7 @@ Find more details about APIs that allow to manage assignments in the documentati
3131
- [PIM for Azure AD roles API reference](/graph/api/resources/privilegedidentitymanagementv3-overview)
3232
- [PIM for Azure resource roles API reference](/rest/api/authorization/privileged-role-eligibility-rest-sample)
3333
- [PIM for Groups API reference](/graph/api/resources/privilegedidentitymanagement-for-groups-api-overview)
34-
- [PIM Alerts for Azure AD Roles API reference](/graph/api/resources/privilegedidentitymanagementv3-overview?view=graph-rest-beta#building-blocks-of-the-pim-alerts-apis)
34+
- [PIM Alerts for Azure AD Roles API reference](/graph/api/resources/privilegedidentitymanagementv3-overview?view=graph-rest-beta#building-blocks-of-the-pim-alerts-apis&preserve-view=true)
3535
- [PIM Alerts for Azure Resources API reference](/rest/api/authorization/role-management-alert-rest-sample)
3636

3737

0 commit comments

Comments
 (0)