Weekly Permissions sync 2026-09-06 - #1619
Open
David (marabooy) wants to merge 1 commit into
Open
Conversation
Contributor
There was a problem hiding this comment.
🟡 Changes recommended
It introduces TeamworkTag.*.Group deployment keys without corresponding permission definitions and removes all least=Application mappings for Teams tag endpoints, risking inconsistent/ambiguous least-permission resolution.
Once you've addressed the issues Copilot identified, you can request another Copilot review.
Pull request overview
Weekly permissions catalog sync updating the permissions/new datasets that drive Microsoft Graph permission metadata (deployments/visibility and endpoint-to-permission mappings).
Changes:
- Updated deployment visibility for
CrossTenantContentMigration.*inprovisioningInfo.json. - Added
CrossTenantContentMigration.Read.All/CrossTenantContentMigration.ReadWrite.Allpermission definitions and endpoint mappings inpermissions.json. - Adjusted Teams tag (
/teams/{id}/tags*) least-permission mappings for application permissions and introduced new Teams tag “*.Group” deployment entries.
File summaries
| File | Description |
|---|---|
| permissions/new/provisioningInfo.json | Updates permission deployment metadata (visibility + new Teams tag *.Group deployment entries). |
| permissions/new/permissions.json | Adds CrossTenantContentMigration permissions and updates least-permission mappings for Teams tags endpoints. |
Review details
Suppressed comments (6)
permissions/new/provisioningInfo.json:18091
TeamworkTag.ReadWrite.Groupis introduced inpermissionDeployments, but this permission key is not defined anywhere inpermissions/new/permissions.json(repo search only finds it here). This inconsistency can cause tooling to misreport availability / least-permission mappings for Teams tag endpoints.
"TeamworkTag.ReadWrite.Group": [
{
"id": "0e5a377d-5652-4345-949e-8b29ca8e8059",
"scheme": "Application",
"environment": "public",
"isHidden": true,
"isEnabled": true,
permissions/new/permissions.json:57067
- These application POST endpoints were changed from
least=Applicationto an empty string, leaving noleast=Applicationmapping for app-only operations on Teams tags. If a different permission is intended to be least (e.g., the newly-addedTeamworkTag.*.Group), it should be represented inpermissions/new/permissions.json; otherwise keep these asleast=Application.
permissions/new/permissions.json:57079 - This application PATCH/DELETE path was changed from
least=Applicationto an empty string. With no otherleast=Applicationmapping for Teams tag endpoints, least-permission resolution for app-only callers can become ambiguous.
permissions/new/permissions.json:57090 - This application DELETE path was changed from
least=Applicationto an empty string. With no otherleast=Applicationmapping for Teams tag endpoints, least-permission resolution for app-only callers can become ambiguous.
permissions/new/permissions.json:13639 - The delegated display/description text is ungrammatical ("your tenant's all") and inconsistent with the existing "cross-tenant" hyphenation used elsewhere in this file. Consider updating these strings for clarity.
permissions/new/permissions.json:13645 - The application description text is ungrammatical ("your tenant's all") and inconsistent with the "cross-tenant" hyphenation used elsewhere in this file. Updating improves catalog quality for consumers.
- Files reviewed: 2/2 changed files
- Comments generated: 4
- Review effort level: Lite
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Comment on lines
+56956
to
+56959
| "/teams/{id}/tags": "", | ||
| "/teams/{id}/tags/{id}": "", | ||
| "/teams/{id}/tags/{id}/members": "", | ||
| "/teams/{id}/tags/{id}/members/{id}": "" |
Comment on lines
+18055
to
+18060
| "TeamworkTag.Read.Group": [ | ||
| { | ||
| "id": "5df3a8db-6cc6-454c-b68a-659a8e76ea66", | ||
| "scheme": "Application", | ||
| "environment": "public", | ||
| "isHidden": true, |
Comment on lines
+13597
to
+13600
| "adminDisplayName": "Read all cross tenant content migration job details", | ||
| "adminDescription": "Allows the app to read your tenant's all cross tenant content migration job details on behalf of the signed-in user.", | ||
| "userDisplayName": "Read all cross tenant content migration job details", | ||
| "userDescription": "Allows the app to read your tenant's all cross tenant content migration job details on behalf of the signed-in user.", |
Comment on lines
+13605
to
+13606
| "adminDisplayName": "Read all cross tenant content migration job details", | ||
| "adminDescription": "Allows the app to read your tenant's all cross tenant content migration job details without a signed-in user.", |
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-09-06