Weekly Permissions sync 2026-08-13

[David (marabooy)]

Weekly Permissions sync 2026-08-13

[Copilot]

Pull request overview

Weekly permissions catalog sync updating Microsoft Graph permission-to-path mappings in permissions/new/permissions.json.

Changes:

• Refactors the Cloud PC organizationConfiguration endpoint mapping into a separate path set.
• Updates Lifecycle Workflows (AgentId) lifecycle policy routes (including deletedItems and rules/priority configuration routes).
• Adds multiple Planner/Tasks-related routes to Tasks permissions path sets.

Suppressed comments (18)

permissions/new/permissions.json:51181

• These newly added top-level Planner routes (/buckets and related) do not match the documented Microsoft Graph Planner URL space, which is rooted under /planner (for example, /planner/buckets). This risks publishing invalid endpoints for application permissions as well.
  permissions/new/permissions.json:51185
• The new /groups/{id}/plans path does not follow the existing Planner route pattern used elsewhere in the catalog (/groups/{id}/planner/plans). If this is intended to represent Planner plans, it should remain namespaced under /planner.
  permissions/new/permissions.json:51190
• The new /me/tasks path does not match existing task endpoints already present for application permissions (/me/todo/... and /me/outlook/...); for Planner tasks the established namespace is /me/planner/.... This entry is likely invalid and should be removed unless it’s backed by updated Graph metadata.
  permissions/new/permissions.json:51234
• The new top-level /plans and /tasks route family under application permissions does not align with the documented Planner route structure (/planner/plans, /planner/tasks, etc.). Keeping these entries alongside the existing /planner/* routes is inconsistent and may mislead consumers.
  permissions/new/permissions.json:51245
• The new /teams/{id}/channels/{id}/plans path does not follow the existing Planner channel route pattern (/teams/{id}/channels/{id}/planner/plans). This entry is likely invalid or should be /planner-scoped.
  permissions/new/permissions.json:51251
• The new /users/{id}/tasks endpoint introduces a non-/planner namespace for Planner tasks and doesn’t match existing task endpoints (/users/{id}/todo/..., /users/{id}/outlook/..., /users/{id}/planner/...). It should be removed unless it’s a confirmed Graph route.
  permissions/new/permissions.json:51324
• These newly added /buckets/{id} and /buckets/{id}/tasks routes (even with empty mapping values) do not match the documented Planner URL space, which is under /planner. Keeping them in the catalog risks advertising unsupported endpoints.
  permissions/new/permissions.json:51328
• The new /groups/{id}/plans path does not follow the existing Planner namespace used elsewhere in this file (/groups/{id}/planner/plans). This entry is likely invalid and should be removed or corrected to the /planner-scoped route.
  permissions/new/permissions.json:51353
• The new /teams/{id}/channels/{id}/plans route does not follow the existing Planner channel route pattern already present (/teams/{id}/channels/{id}/planner/plans). It should be removed unless it’s a confirmed Microsoft Graph route.
  permissions/new/permissions.json:51712
• The /plans/{id} and /tasks/{id} top-level route family does not align with the documented Planner route structure (/planner/plans/{id}, /planner/tasks/{id}, etc.). Keeping these entries risks publishing invalid endpoints in the permissions catalog.
  permissions/new/permissions.json:51721
• The new /users/{id}/tasks route introduces a non-/planner namespace for Planner tasks and doesn’t match existing task endpoints (/users/{id}/todo/..., /users/{id}/outlook/..., /users/{id}/planner/...). It should be removed unless it’s a confirmed Microsoft Graph route.
  permissions/new/permissions.json:51336
• The new /me/plans and /me/tasks entries don’t match existing task/planner endpoint patterns already present (for example, /me/planner/..., /me/todo/..., /me/outlook/...). If these are meant to be Planner resources, they should be /me/planner/*; otherwise they should be removed.
  permissions/new/permissions.json:51362
• The new /users/{id}/plans and /users/{id}/tasks entries introduce a second, non-/planner namespace for Planner resources. If unsupported, they should be removed; if supported, they should be aligned with the established /users/{id}/planner/... routes.
  permissions/new/permissions.json:51691
• These newly added /buckets/{id} and /buckets/{id}/tasks routes (even with empty mapping values) do not match the documented Planner URL space, which is under /planner. Keeping them risks advertising unsupported endpoints for application permissions.
  permissions/new/permissions.json:51694
• The new /groups/{id}/plans path does not follow the established Planner route pattern used elsewhere in this file (/groups/{id}/planner/plans). This entry is likely invalid and should be removed or corrected to the /planner-scoped route.
  permissions/new/permissions.json:51698
• The new /me/tasks entry does not match existing task endpoints already present for application permissions (/me/todo/... and /me/outlook/...) and does not align with the /me/planner/... namespace for Planner. This entry is likely invalid and should be removed unless confirmed by updated Graph metadata.
  permissions/new/permissions.json:51716
• The new /teams/{id}/channels/{id}/plans route does not match the existing Planner channel route pattern already present (/teams/{id}/channels/{id}/planner/plans). This entry is likely invalid and should be removed unless confirmed by Graph metadata.
  permissions/new/permissions.json:51349
• The /plans/{id} and /tasks/{id} top-level route family does not align with the documented Planner route structure (/planner/plans/{id}, /planner/tasks/{id}, etc.). Keeping these entries risks publishing invalid endpoints in the permissions catalog.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.