Conversation
There was a problem hiding this comment.
Pull request overview
Weekly sync updating permission metadata by adding new Entra App Role privileged access permission entries and normalizing privilegedAccess/group endpoint path casing.
Changes:
- Added provisioning metadata entries for several
*.EntraAppRoleprivileged access permissions. - Normalized
/identityGovernance/privilegedAccess/group/...path keys to Graph-style camelCase, includingfilterByCurrentUser.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| permissions/new/provisioningInfo.json | Adds provisioning entries for new EntraAppRole privileged access permissions. |
| permissions/new/permissions.json | Updates privilegedAccess/group paths to camelCase + filterByCurrentUser casing. |
Comments suppressed due to low confidence (1)
permissions/new/permissions.json:1
- These path keys use
assignmentscheduleInstances(lowercasesinschedule), which is inconsistent with other entries in the same file that useassignmentScheduleInstances. Since URL paths are generally case-sensitive and this file appears to rely on exact string keys, this likely creates incorrect/mismatched permission mappings. Rename these keys to/identityGovernance/privilegedAccess/group/assignmentScheduleInstances...for consistency with the rest of the document.
💡 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.
| "PrivilegedAssignmentSchedule.Read.EntraAppRole": [ | ||
| { | ||
| "scheme": "DelegatedWork", | ||
| "environment": "", | ||
| "isHidden": true, | ||
| "isEnabled": true, | ||
| "resourceAppId": "01fc33a7-78ba-4d2f-a4b7-768e336e890e" | ||
| }, | ||
| { | ||
| "scheme": "Application", | ||
| "environment": "", | ||
| "isHidden": true, | ||
| "isEnabled": true, | ||
| "resourceAppId": "01fc33a7-78ba-4d2f-a4b7-768e336e890e" | ||
| } | ||
| ], |
There was a problem hiding this comment.
These newly added provisioning entries don’t include an id field, while many adjacent permissions in this file include one. If provisioningInfo.json is schema-validated or consumed by tooling that expects id per scheme entry, this will fail or produce incomplete metadata. Align these objects with the established shape (add the appropriate id value(s) if required by the schema/tooling for DelegatedWork/Application).
Weekly Permissions sync 2026-03-11