Conversation
There was a problem hiding this comment.
Pull request overview
Weekly permissions sync updating the permissions catalog for privileged access/role management scenarios, including new hidden provisioning entries and API path casing normalization for privilegedAccess group endpoints.
Changes:
- Added hidden provisioningInfo entries for several
*.EntraAppRolepermissions (DelegatedWork + Application). - Normalized several privilegedAccess/group API paths in
permissions.json(notablyfilterByCurrentUserand camelCase resource segments).
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 7 comments.
| File | Description |
|---|---|
| permissions/new/provisioningInfo.json | Adds hidden provisioning metadata for new EntraAppRole-scoped privileged access permissions. |
| permissions/new/permissions.json | Updates privilegedAccess/group path strings to corrected casing for instances/requests/schedules endpoints. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
You can also share your feedback on Copilot code review. Take the survey.
| "/identityGovernance/privilegedAccess/group/assignmentscheduleInstances": "", | ||
| "/identityGovernance/privilegedAccess/group/assignmentscheduleInstances/{id}": "", | ||
| "/identityGovernance/privilegedAccess/group/assignmentscheduleInstances/filterByCurrentUser(on={value})": "", |
There was a problem hiding this comment.
In this pathSet the assignmentScheduleInstances segment is still spelled as assignmentscheduleInstances (lowercase s), while the read-only permission just above uses /assignmentScheduleInstances. This inconsistency is likely to break path matching; update these three paths to use the same casing as the canonical endpoint.
| { | ||
| "scheme": "DelegatedWork", | ||
| "environment": "", | ||
| "isHidden": true, | ||
| "isEnabled": true, | ||
| "resourceAppId": "01fc33a7-78ba-4d2f-a4b7-768e336e890e" |
There was a problem hiding this comment.
These new provisioning entries omit the id field entirely. Elsewhere in this file each scheme entry includes an id key (sometimes as an empty string for hidden entries); omitting it may break consumers that expect a consistent schema. Add an id field (or explicitly set it to an empty string) for both scheme objects here and keep the usual key ordering.
| { | ||
| "scheme": "DelegatedWork", | ||
| "environment": "", | ||
| "isHidden": true, | ||
| "isEnabled": true, | ||
| "resourceAppId": "01fc33a7-78ba-4d2f-a4b7-768e336e890e" |
There was a problem hiding this comment.
These new provisioning entries omit the id field entirely. Elsewhere in this file each scheme entry includes an id key (sometimes as an empty string for hidden entries); omitting it may break consumers that expect a consistent schema. Add an id field (or explicitly set it to an empty string) for both scheme objects here and keep the usual key ordering.
| { | ||
| "scheme": "DelegatedWork", | ||
| "environment": "", | ||
| "isHidden": true, | ||
| "isEnabled": true, | ||
| "resourceAppId": "01fc33a7-78ba-4d2f-a4b7-768e336e890e" |
There was a problem hiding this comment.
These new provisioning entries omit the id field entirely. Elsewhere in this file each scheme entry includes an id key (sometimes as an empty string for hidden entries); omitting it may break consumers that expect a consistent schema. Add an id field (or explicitly set it to an empty string) for both scheme objects here and keep the usual key ordering.
| { | ||
| "scheme": "DelegatedWork", | ||
| "environment": "", | ||
| "isHidden": true, | ||
| "isEnabled": true, | ||
| "resourceAppId": "01fc33a7-78ba-4d2f-a4b7-768e336e890e" |
There was a problem hiding this comment.
These new provisioning entries omit the id field entirely. Elsewhere in this file each scheme entry includes an id key (sometimes as an empty string for hidden entries); omitting it may break consumers that expect a consistent schema. Add an id field (or explicitly set it to an empty string) for both scheme objects here and keep the usual key ordering.
| { | ||
| "scheme": "DelegatedWork", | ||
| "environment": "", | ||
| "isHidden": true, | ||
| "isEnabled": true, | ||
| "resourceAppId": "01fc33a7-78ba-4d2f-a4b7-768e336e890e" |
There was a problem hiding this comment.
These new provisioning entries omit the id field entirely. Elsewhere in this file each scheme entry includes an id key (sometimes as an empty string for hidden entries); omitting it may break consumers that expect a consistent schema. Add an id field (or explicitly set it to an empty string) for both scheme objects here and keep the usual key ordering.
| { | ||
| "scheme": "DelegatedWork", | ||
| "environment": "", | ||
| "isHidden": true, | ||
| "isEnabled": true, | ||
| "resourceAppId": "01fc33a7-78ba-4d2f-a4b7-768e336e890e" |
There was a problem hiding this comment.
These new provisioning entries omit the id field entirely. Elsewhere in this file each scheme entry includes an id key (sometimes as an empty string for hidden entries); omitting it may break consumers that expect a consistent schema. Add an id field (or explicitly set it to an empty string) for both scheme objects here and keep the usual key ordering.
Weekly Permissions sync 2026-03-10