Weekly Permissions sync 2026-08-31 - #1612
Open
David (marabooy) wants to merge 1 commit into
Open
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
Weekly permissions catalog sync updating the “new” permissions model by adding new permission deployments and expanding endpoint-to-permission mappings.
Changes:
- Added multiple new
permissionDeploymentsentries and adjusted visibility/resource app IDs inpermissions/new/provisioningInfo.json. - Added new endpoints and one new permission definition (
Device-CloudLicensing.*) inpermissions/new/permissions.json, plus removedLifecyclePolicies-AgentId.*permissions.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 3 comments.
| File | Description |
|---|---|
| permissions/new/provisioningInfo.json | Adds/updates permission deployment metadata (ids, schemes, environments, hidden/enabled flags, resourceAppId) for weekly sync. |
| permissions/new/permissions.json | Updates permission definitions and path mappings to reflect new/changed Graph endpoints and permissions. |
Suppressed comments (2)
permissions/new/provisioningInfo.json:9355
LifecyclePolicies-AgentId.Read.All/LifecyclePolicies-AgentId.ReadWrite.Allstill have deployment entries here, but these permissions do not exist inpermissions/new/permissions.json(and appear to have been removed there in this sync). Keeping them inprovisioningInfo.jsonwill leave these deployments out of sync / orphaned.
"LifecyclePolicies-AgentId.Read.All": [
{
"id": "3d09c9ee-9db9-4c84-85ec-f63a21b4ad2c",
"scheme": "DelegatedWork",
"environment": "public",
permissions/new/provisioningInfo.json:18265
ThreatHunting.ReadWrite.Allis present inprovisioningInfo.json, but there is no corresponding permission definition inpermissions/new/permissions.json(onlyThreatHunting.Read.Allexists). This makes the sync inconsistent: either add theThreatHunting.ReadWrite.Alldefinition to permissions.json or remove/disable this deployment entry.
"ThreatHunting.ReadWrite.All": [
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Comment on lines
+18265
to
+18280
| "ThreatHunting.ReadWrite.All": [ | ||
| { | ||
| "scheme": "DelegatedWork", | ||
| "environment": "public", | ||
| "isHidden": true, | ||
| "isEnabled": false, | ||
| "resourceAppId": "992136bc-5b57-425f-8d95-ac65975722cd" | ||
| }, | ||
| { | ||
| "scheme": "Application", | ||
| "environment": "public", | ||
| "isHidden": true, | ||
| "isEnabled": false, | ||
| "resourceAppId": "992136bc-5b57-425f-8d95-ac65975722cd" | ||
| } | ||
| ], |
Comment on lines
+2035
to
+2039
| "AutomationRules.Read.All": [ | ||
| { | ||
| "id": "", | ||
| "scheme": "DelegatedWork", | ||
| "environment": "public", |
| "resourceAppId": "ce79fdc4-cd1d-4ea5-8139-e74d7dbe0bb7" | ||
| }, | ||
| { | ||
| "id": "75d9ca3df-7017-4feb-baa0-06a339b6c338", |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Weekly Permissions sync 2026-08-31