M365 Graph Permissions Lookup

Decode Microsoft Graph permission GUIDs, scope names, and Entra role IDs into clear descriptions, permission types, and admin consent requirements.

Lookup Graph Permissions Easily

Turn cryptic Microsoft Graph permission GUIDs and scope names into clear, readable descriptions. Search for a single permission by name, GUID, or keyword, or use Bulk decode to paste multiple entries from an app manifest, consent grant, or token—including a token’s wids array. The results identify each permission or Entra role, distinguish delegated from application access, and show when admin consent is required. Everything is processed locally in your browser, so nothing you paste is uploaded or sent elsewhere.

Data from Microsoft's Graph permissions reference and Entra built-in roles. Not affiliated with or endorsed by Microsoft.

How the Graph Permissions Lookup Tool Works

App manifests, consent grants, and tokens identify Microsoft Graph permissions by GUID or by terse scope names. This tool translates them into what they actually allow, using Microsoft's published permission definitions (598 delegated scopes and 534 application permissions), and flags which ones need admin consent.

It also decodes Entra built-in role template IDs (135 roles), so you can paste the wids array from a token and see which directory roles the user holds.

Delegated permissions act on behalf of a signed-in user; application permissions let an app act on its own with no user present, which is why the application variants are the ones to scrutinize. Everything runs in your browser from data embedded in this page. Nothing you paste is sent anywhere.

How to use the Graph permissions lookup

  1. Type a permission name like Mail.Read, a GUID, or a keyword like "calendar" into the search box.
  2. Each result shows what the permission allows, whether it's delegated or application, and whether it needs admin consent.
  3. To decode a list, switch to Bulk decode and paste GUIDs or scope names, one per line. This works well for the requiredResourceAccess section of an app manifest or the wids array from a token.
  4. Use Copy as CSV to keep the results for an app review or a change ticket.

Where you'll find Graph permission GUIDs

  • App registration manifests. The requiredResourceAccess section lists each permission as a GUID with a type of Scope (delegated) or Role (application).
  • Access tokens. A decoded token lists delegated permissions in the scp claim, application permissions in the roles claim, and the user's Entra directory roles as role template IDs in the wids claim.
  • Audit logs. Entries like "Add app role assignment to service principal" record the permission that was granted by its ID.
  • Microsoft Graph itself. Every permission is defined on the Microsoft Graph service principal (app ID 00000003-0000-0000-c000-000000000000). Application permissions live in its appRoles and delegated permissions in its oauth2PermissionScopes.

Frequently asked questions

Which permissions should I look at most closely?

Application permissions, especially anything ending in .ReadWrite.All or covering mail, files, or directory data. An app with application permissions can act across the whole tenant with no user signed in, so a single grant like Mail.Read as an application permission means it can read every mailbox. Delegated permissions are limited to what the signed-in user can already access.

Yes. Application permissions always require an administrator to consent. Some delegated permissions also require admin consent, and the lookup flags those so you know before you request them.

Where does the permission data come from?

From Microsoft's Microsoft Graph permissions reference and the Entra built-in roles list. Microsoft adds new permissions regularly, so if one is missing, the reference page will have it first.

Is it safe to paste a token or manifest?

The lookup runs entirely in your browser and nothing you paste is uploaded. That said, treat real access tokens like passwords. Decode the claims you need and avoid pasting live tokens into any site you don't control.

If you're reviewing what Copilot connectors and agents can reach in your tenant, Managing Microsoft 365 Copilot Connectors covers the admin controls side.