Publish Workbooks permissions and /security/workbooks permission mappings for Graph Explorer

Ouverte
#1,680 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

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

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:

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

  1. 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.
  2. 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.
  3. 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

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de microsoftgraph/microsoft-graph-devx-content

Toutes les issues de microsoftgraph/microsoft-graph-devx-content

Issues similaires

Plus d'issues JavaScript

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.