Scopes for a web API accepting v1.0 tokens

OAuth2 permissions are permission scopes that an Azure Active Directory (Azure AD) for developers (v1.0) web API (resource) application exposes to client applications. These permission scopes may be granted to client applications during consent. See the section about oauth2Permissions in the Azure Active Directory application manifest reference.

Scopes to request access to specific OAuth2 permissions of a v1.0 application

To acquire tokens for specific scopes of a v1.0 application (for example the Microsoft Graph API, which is, create scopes by concatenating a desired resource identifier with a desired OAuth2 permission for that resource.

For example, to access on behalf of the user a v1.0 web API where the app ID URI is ResourceId:

var scopes = new [] {  ResourceId+"/user_impersonation"};
var scopes = [ ResourceId + "/user_impersonation"];

To read and write with MSAL.NET Azure AD using the Microsoft Graph API (, create a list of scopes as shown in the following examples:

string ResourceId = "";
var scopes = new [] { ResourceId + "Directory.Read", ResourceID + "Directory.Write"}
var ResourceId = "";
var scopes = [ ResourceId + "Directory.Read", ResourceID + "Directory.Write"];

To write the scope corresponding to the Azure Resource Manager API (, request the following scope (note the two slashes):

var scopes = new[] {""};
var result = await app.AcquireTokenInteractive(scopes).ExecuteAsync();

// then call the API:


Use two slashes because the Azure Resource Manager API expects a slash in its audience claim (aud), and then there is a slash to separate the API name from the scope.

The logic used by Azure AD is the following:

  • For ADAL (Azure AD v1.0) endpoint with a v1.0 access token (the only possible), aud=resource
  • For MSAL (Microsoft identity platform) asking an access token for a resource accepting v2.0 tokens, aud=resource.AppId
  • For MSAL (v2.0 endpoint) asking an access token for a resource that accepts a v1.0 access token (which is the case above), Azure AD parses the desired audience from the requested scope by taking everything before the last slash and using it as the resource identifier. Therefore, if expects an audience of, you'll need to request a scope of See also GitHub issue #747: Resource url's trailing slash is omitted, which caused sql auth failure.

Scopes to request access to all the permissions of a v1.0 application

If you want to acquire a token for all the static scopes of a v1.0 application, append ".default" to the app ID URI of the API:

ResourceId = "someAppIDURI";
var scopes = new [] {  ResourceId+"/.default"};
var ResourceId = "someAppIDURI";
var scopes = [ ResourceId + "/.default"];

Scopes to request for a client credential flow/daemon app

For the standard client credentials flow, use /.default. For example,

Azure AD will automatically include all the app-level permissions the admin has consented to in the access token for the client credentials flow.