Publish Workbooks permissions and /security/workbooks permission mappings for Graph Explorer
Les mainteneurs répondent en général sous 1 jour
Personne n'a encore pris cette issue.
Évaluation
- Difficulté
- 4/5
- Temps estimé
- 3-5 jours
- Accessibilité débutants
- 48/100
- Type d'issue
- Fonctionnalité
- Clarté
- Plutôt claire
- Activité
- Active
- Stack technique
- json
- Domaine
- api, developer-experience
Piste de recherche
Start by reading permissions/new/permissions.json, permissions/permissions-descriptions.json, and the weekly sync referenced in the issue to identify the authoritative input and how mappings are exported. Then inspect azure-pipelines/publishSamples.yml for the reviewed publication workflow. Done means both permissions, consent metadata, and the requested delegated/application path mappings survive a subsequent sync and appear correctly in the public lookups.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Description
Summary
Please include the existing Workbooks.Read.All and Workbooks.ReadWrite.All permissions in the DevX permission catalog and its request-to-permission mappings, so Microsoft Graph Explorer can display and request the appropriate permissions for the beta Security Workbooks APIs.
Routing to the repository CODEOWNERS: @microsoftgraph/msgraph-devx-api-write.
This is a catalog/publication request, not a request to create new OAuth permissions, change API authorization, or grant tenant consent.
Evidence
Checked on 2026-11-03 at approximately 08:34 UTC:
- The live beta resource tree now includes
security/workbooksandsecurity/workbooks/{workbook-id}. The public API documentation is also published. - The delegated permission catalog does not contain either Workbooks permission.
- The DevX GET /security/workbooks permission lookup returns HTTP 404. This is the permission-helper endpoint, not a claim that the Graph Workbooks API itself returns 404.
- At commit
3f9d57368bae13aade91c37bd48c81ff2cee4bb6, neither permission nor the/security/workbookspaths appears inpermissions/new/permissions.json. The permission description catalog also lacks both names. - That commit is the November 2 weekly permissions sync, #1678, so the missing source entries cannot be resolved by refreshing the consumer cache alone.
Required mappings
For both DelegatedWork and Application, following the existing published API permission requirements:
| Method | Path | Least-privileged permission | Higher-privileged alternative |
|---|---|---|---|
| GET | /security/workbooks |
Workbooks.Read.All |
Workbooks.ReadWrite.All |
| GET | /security/workbooks/{workbook-id} |
Workbooks.Read.All |
Workbooks.ReadWrite.All |
| POST | /security/workbooks |
Workbooks.ReadWrite.All |
None |
| PATCH | /security/workbooks/{workbook-id} |
Workbooks.ReadWrite.All |
None |
| DELETE | /security/workbooks/{workbook-id} |
Workbooks.ReadWrite.All |
None |
Use the permission model's normal path-parameter convention. No DelegatedPersonal support is requested. Please preserve the existing authoritative consent descriptions and admin-consent requirements rather than inventing new permission text or identifiers.
Requested resolution
- Identify and correct the authoritative input to the weekly permission export so these definitions and path sets are included and survive subsequent syncs. Please advise if an owner-reviewed manual content PR is the supported route instead.
- Publish the complete permission definitions, consent metadata, and API mappings through the normal reviewed content workflow. Adding display names alone is insufficient to fix the missing request mappings.
- Confirm the production permission-content deployment through
azure-pipelines/publishSamples.yml, and account for consumer caching before verifying the public endpoints.
Acceptance criteria
- Both permissions appear in the public DevX permission catalog for their supported delegated/application schemes.
- The collection and item lookups above return the expected permissions and least-privilege markings instead of a missing-mapping response.
- Graph Explorer's Modify permissions view displays the correct permissions for the beta Workbooks requests.
- A subsequent weekly sync preserves the entries.
Catalog publication is separate from tenant-admin consent; no consent or authorization change is requested by this issue.
- Langage dominant
- JavaScript
- Étoiles
- 36
- Forks
- 54
- Merge moyen
- 14 h 11 min
- PR mergées (30 j)
- 13
Préparer son environnement
- Aucun Dockerfile ni fichier Docker Compose
- Propose un modèle de pull request
- Lire le guide de contribution
Par où commencer
- Lisez l'issue en entier, puis le guide de contribution du projet.
- Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
- Forkez le dépôt et travaillez sur une branche.
- Ouvrez une pull request qui référence le numéro de l'issue.
Autres issues de microsoftgraph/microsoft-graph-devx-content
-
No PowerShell snippets generatedOuverte
Difficulté 4/5 3-5 jours Accessibilité débutants 45/100
microsoftgraph/microsoft-graph-devx-content#1564 · 2 commentaires ·
Les mainteneurs répondent en général sous 1 jour
-
Difficulté 5/5 Plus d'une semaine Accessibilité débutants 15/100
microsoftgraph/microsoft-graph-devx-content#1293 ·
Les mainteneurs répondent en général sous 1 jour
-
Difficulté 4/5 3-5 jours Accessibilité débutants 35/100
microsoftgraph/microsoft-graph-devx-content#1290 ·
Les mainteneurs répondent en général sous 1 jour
-
Difficulté 3/5 1-2 jours Accessibilité débutants 35/100
microsoftgraph/microsoft-graph-devx-content#423 · 1 commentaire ·
Les mainteneurs répondent en général sous 1 jour
-
bug
Difficulté 3/5 1-2 jours Accessibilité débutants 35/100
microsoftgraph/microsoft-graph-devx-content#361 · 3 commentaires ·
Les mainteneurs répondent en général sous 1 jour
Toutes les issues de microsoftgraph/microsoft-graph-devx-content
Issues similaires
-
Difficulté 2/5 1-3 heures Accessibilité débutants 78/100
fb55/htmlparser2#2579 ·
Les mainteneurs répondent en général sous 1 jour
-
Difficulté 2/5 1-3 heures Accessibilité débutants 66/100
Les mainteneurs répondent en général sous 1 jour
-
Docker images: plain X.Y.Z tag (e.g. 7.2.3) is never updated after the initial release buildOuverteneeds verification
Difficulté 2/5 1-3 heures Accessibilité débutants 74/100
Les mainteneurs répondent en général sous 13 jours
-
bug
Difficulté 2/5 1-3 heures Accessibilité débutants 83/100
swc-project/swc-next-issues#532 ·
-
domain/checkout Platform(Default) priority/low testing/acceptance
Difficulté 2/5 1-3 heures Accessibilité débutants 76/100
Les mainteneurs répondent en général sous 1 jour