Microsoft Azure Cdn · OAuth Scopes

Microsoft Azure Cdn OAuth Scopes

OAuth 2.0 searched

Microsoft Azure Cdn publishes 2 OAuth 2.0 scopes via the implicit flow. Scopes are the fine-grained permissions an application requests at authorization time to act against the Microsoft Azure Cdn API on a user’s behalf.

This index is generated from the provider’s OpenAPI security definitions (and, where available, its documented scope reference) and refreshes on every APIs.io network build. Browse every provider’s scopes at scopes.apis.io.

CDNEdgeCachingCloud InfrastructureNetworkingWeb PerformanceAzureContent DeliveryWeb Application Firewall
Scopes: 2 Flows: implicit Method: searched

OAuth endpoints

Authorization URL
https://login.microsoftonline.com/common/oauth2/authorize
Flows
implicit

Scopes (2)

ScopeDescriptionFlows
user_impersonation impersonate your user account implicit
https://management.azure.com/.default The resource scope a service principal or managed identity requests for any Azure Resource Manager call, Microsoft.Cdn included. Documented by Microsoft, not declared in the contract. client_credentials

Source

OAuth Scopes

Raw ↑
generated: '2026-09-17'
method: searched
source: >-
  openapi/microsoft-azure-cdn-management-openapi.json,
  https://learn.microsoft.com/en-us/azure/role-based-access-control/built-in-roles/networking
docs: https://learn.microsoft.com/en-us/azure/role-based-access-control/built-in-roles/networking
provider: microsoft-azure-cdn
note: >-
  Two different things are called a "scope" on this API and conflating them is the usual integration
  mistake. (1) The OAUTH SCOPE is coarse: the contract declares exactly one, user_impersonation, and
  the real-world token request asks for https://management.azure.com/.default — neither expresses what
  the caller may do. (2) The AUTHORIZATION SCOPE is an Azure RBAC role assigned at an ARM resource
  scope, and that is what actually gates each of the 115 operations. Both are recorded below; the RBAC
  block is the one that matters.
schemes:
- name: azure_auth
  source: openapi/microsoft-azure-cdn-management-openapi.json
  flows:
  - flow: implicit
    authorizationUrl: https://login.microsoftonline.com/common/oauth2/authorize
  description: Azure Active Directory OAuth2 Flow.
scopes:
- scope: user_impersonation
  description: impersonate your user account
  flows:
  - implicit
  declared_in: contract
  sources:
  - openapi/microsoft-azure-cdn-management-openapi.json
- scope: https://management.azure.com/.default
  description: >-
    The resource scope a service principal or managed identity requests for any Azure Resource Manager
    call, Microsoft.Cdn included. Documented by Microsoft, not declared in the contract.
  flows:
  - client_credentials
  declared_in: docs
rbac_roles:
- role: CDN Profile Contributor
  id: ec156ff8-a8d1-4d15-830c-5b80698ca432
  description: Can manage CDN profiles and their endpoints, but can't grant access to other users.
  grants: [Microsoft.Cdn/*]
- role: CDN Profile Reader
  id: 8f96442b-4075-438f-813d-ad51ab4019af
  description: Can view CDN profiles and their endpoints, but can't make changes.
  grants: [Microsoft.Cdn/*/read]
- role: CDN Endpoint Contributor
  id: 426e0c7f-0c7e-4658-b36f-ff54d6c29b45
  description: Can manage CDN endpoints, but can't grant access to other users.
  grants:
  - Microsoft.Cdn/edgenodes/read
  - Microsoft.Cdn/operationresults/*
  - Microsoft.Cdn/profiles/endpoints/*
- role: CDN Endpoint Reader
  id: 871e35f6-b5c1-49cc-a043-bde969a0f2cd
  description: Can view CDN endpoints, but can't make changes.
  grants:
  - Microsoft.Cdn/edgenodes/read
  - Microsoft.Cdn/operationresults/*
  - Microsoft.Cdn/profiles/endpoints/*/read
  - Microsoft.Cdn/profiles/afdendpoints/validateCustomDomain/action
assignable_scopes:
- /subscriptions/{subscriptionId}
- /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}
- /subscriptions/{subscriptionId}/resourceGroups/{rg}/providers/Microsoft.Cdn/profiles/{profileName}

Work with this as data

Every scope set here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for oauth scopes

4 MCP tools reach this
  • find_scopesBrowse and filter every scope set in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This scope set
curl "https://apis.io/api/v1/scopes/microsoft-azure-cdn-scopes"
All oauth scopes
curl "https://apis.io/api/v1/scopes?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.