Microsoft Entra Agent ID
Developer

Configure inheritable permissions for agent identity blueprints

In brief

The article now documents delegated scope inheritance through the Microsoft Graph beta API, including eligibility requirements, Graph permissions, and three inheritance patterns. Application-role inheritance and a numeric resource-app limit are no longer defined in the public Graph guidance.

What Entra admins need to know

Administrators implementing inheritance should verify that resource apps are configured as inheritable, scopes are granted to the blueprint principal, and the required Graph permissions are used.

This editorial summary was generated by AI from the documentation changes. Verify important details in the full Microsoft Learn article.

Documentation change

The comparison below shows only the changed extract. Use the full-page view for complete context.

Configure inheritable permissions for agent identity blueprints

Configure inheritable permissions on an agent identity blueprint to preauthorize a base set ofspecify which delegated scopes can be inherited by agent identities. A scope is eligible for inheritance only when the resource app is configured as inheritable and application roles. Agent identities created fromthe scope is granted to the blueprint automatically inherit those permissions without interactive consent prompts.principal.

For conceptual background on how inheritable permissions relate to required resource access and direct permission grants, see Inheritable permissions and required resource access.

Prerequisites

  • An existing agent identity blueprint already createdblueprint.
  • For Microsoft Graph requests, the AgentIdentityBlueprint.Create permission to add an entry and configuredAgentIdentityBlueprint.ReadWrite.All to update or delete an entry.
  • Either ofFor delegated requests by a nonowner, the following permissions:
    • Agent ID Developer role for managing agent identity blueprints owned by the user
    • Agent ID Administrator role for managing agent identity blueprints
    role. Blueprint owners can manage their own blueprints.

How inheritable permissions work

During token issuance forThe public Microsoft Graph beta inheritablePermission resource documents delegated scope inheritance through inheritableScopes. The broader Agent ID permission model also describes application-role inheritance, but the public Graph reference doesn't define an agent identity,application-role property or payload. Confirm the platform merges eligible inherited scopes with the agent's requested delegated scopes. Inherited scopes appear in the access token's scp claim and inherited roles appear in the roles claim. supported Graph API contract before relying on application-role inheritance.

For details on inheritance conditions and the relationshipdistinction between declarations,declarations and grants, and effective permissions, see Inheritable permissions and required resource access and the Microsoft Graph inheritablePermission resource.

Inheritance patterns

The concept article describes inheritanceGraph beta API supports these patterns at a high level. The following table shows the specific kind values used in the API when you configure inheritance per resource app:for delegated permission scopes:

InheritancePattern KindGraph type Description
All Allowedallowed scopes allAllowedallAllowedScopes InheritMake all available delegated scopes or application rolespublished by the resource app eligible for the specified resource app. Newly granted scopes or roles on the agent identity blueprint principal are automatically included.inheritance.
NoneEnumerated scopes noneenumeratedScopes Inherit noMake only the listed delegated scopes or roleseligible for inheritance.
No scopesnoScopesDisable delegated scope inheritance for the specified resource app. Use this to explicitly disable inheritance for scopes (noScopes) or roles (noRoles) independently.

You can configure scopes and roles independently on the same resource. For example, you can inherit all scopes while inheriting no roles, or vice versa.

Inheritable permissions limitations

  • Maximum of 50 resource apps per agent identity blueprint (for example, up to 50 entries in the inheritablePermissions collection). If you exceed this limit, reduce the

    The public Microsoft Graph reference doesn't specify a maximum number of resource apps or inheritablePermissions entries for a blueprint. Don't rely on a numeric limit unless Microsoft publishes or confirms it.

    The public Graph reference also doesn't document how application roles are configured for inheritance. The API examples in this article are limited to stay within the supported boundary.

delegated scopes.

Regularly review and monitor your inheritable permissions configuration. Reevaluate inheritedthe scopes and roles to ensure they remain appropriate for your use case. Audit which inherited scopes and roles are being used by agents and remove any unused permissions from both the agent identityconfigured on each blueprint principal and the inheritablegrants on its blueprint principal. Remove permissions list to maintain security hygiene.that are no longer needed.

Configure inheritable permissionsscope inheritance (using Microsoft Graph)

To configure inheritable permissions,These examples use the Microsoft Graph beta API. Beta APIs are subject to change and aren't supported for production applications. For details, see the Microsoft Graph create, update, and delete operations.

Use the inheritablePermissions navigation property on the agentIdentityBlueprint application resource. Each entry specifies the scopes and rolesscope inheritance configuration for a singleone resource app. Document your configuration decisions by tracking why each scope or role is inheritable and who approved it for audit purposes.

When specifying the resourceAppId, use the resource app's application ID in your requests, ensure you provide a valid GUID format. Invalid GUIDs result in 400 Bad Request errors.

Add all delegated scopes and roles inheritance for Microsoft Graph

Request

POST https://graph.microsoft.com/v1.0/beta/applications/microsoft.graph.agentIdentityBlueprint/bc057821-f236-49d6-9f2c-1ebf43e9437a/microsoft.graph.agentIdentityBlueprint/inheritablePermissions
Content-Type: application/json
OData-Version: 4.0

{
  "resourceAppId": "00000003-0000-0000-c000-000000000000",
  "inheritableScopes": {
    "@odata.type": "#microsoft.microsoft.graph.allAllowedScopes",
    "kind": "allAllowed"
  },
  "inheritableRoles": {
    "@odata.type": "#microsoft.graph.allAllowedRoles",
    "kind": "allAllowed"
  }
}

ResponseThe request returns 201 Created. The response includes the configured resource app and inheritance pattern:

HTTP/1.1 201 Created
Content-Type: application/json

{
  "@odata.context": "https://graph.microsoft.com/v1.0/$metadata#applications('bc057821-f236-49d6-9f2c-1ebf43e9437a')/inheritablePermissions/$entity",
  "resourceAppId": "00000003-0000-0000-c000-000000000000",
  "inheritableScopes": {
    "@odata.type": "microsoft.graph.allAllowedScopes",
    "kind": "allAllowed"
  },
  "inheritableRoles": {
    "@odata.type": "microsoft.graph.allAllowedRoles",
    "kind": "allAllowed"
  }
}

Add allenumerated scopes and roles inheritance for multiple resourcesa resource app

You can configure inheritable permissions for multiple resource apps onTo allow only selected delegated scopes, use the same blueprint. Each resource requires a separate POST request. The following example adds inheritance for both Microsoft Graph and SharePoint Online.

Request (Microsoft Graph)enumeratedScopes pattern:

POST https://graph.microsoft.com/v1.0/beta/applications/microsoft.graph.agentIdentityBlueprint/bc057821-f236-49d6-9f2c-1ebf43e9437a/microsoft.graph.agentIdentityBlueprint/inheritablePermissions
Content-Type: application/json
OData-Version: 4.0

{
  "resourceAppId": "00000003-0000-0000-c000-000000000000",
  "inheritableScopes": {
    "@odata.type": "#microsoft.microsoft.graph.allAllowedScopesenumeratedScopes",
    "kindscopes": [
      "allAllowed"
  },
  "inheritableRoles": {
    "@odata.type": "#microsoft.graph.allAllowedRolesUser.Read",
      "kindMail.Read": "allAllowed"
    ]
  }
}

Add scopes for multiple resource apps

Response

Create a separate entry for each resource app, using its application ID as HTTP/1.1 201 Created
Content-Type: application/json

{
  "@odata.context": "https://graph.microsoft.com/v1.0/$metadata#applications('bc057821-f236-49d6-9f2c-1ebf43e9437a')/inheritablePermissions/$entity",
  "resourceAppId": "00000003-0000-0000-c000-000000000000",
  "inheritableScopes": {
    "@odata.type": "microsoft.graph.allAllowedScopes",
    "kind": "allAllowed"
  },
  "inheritableRoles": {
    "@odata.type": "microsoft.graph.allAllowedRoles",
    "kind": "allAllowed"
  }
}

Request (SharePoint Online). For example, change the ID to the SharePoint Online resource app ID for a separate request:

POST https://graph.microsoft.com/v1.0/beta/applications/microsoft.graph.agentIdentityBlueprint/bc057821-f236-49d6-9f2c-1ebf43e9437a/microsoft.graph.agentIdentityBlueprint/inheritablePermissions
Content-Type: application/json

OData-Version: 4.0

{
  "resourceAppId": "00000003-0000-0ff1-ce00-000000000000",
  "inheritableScopes": {
    "@odata.type": "#microsoft.graph.allAllowedScopes",
    "kind": "allAllowed"
  },
  "inheritableRoles": {
    "@odata.type": "#microsoft.graph.allAllowedRoles",
    "kind": "allAllowed"
  }
}

Response

HTTP/1.1 201 Created
Content-Type: application/json

{
  "@odata.context": "https://graph.microsoft.com/v1.0/$metadata#applications('bc057821-f236-49d6-9f2c-1ebf43e9437a')/inheritablePermissions/$entity",
  "resourceAppId": "00000003-0000-0ff1-ce00-000000000000",
  "inheritableScopes": {
    "@odata.type": "microsoft.graph.allAllowedScopes",
    "kind": "allAllowed"
  },
  "inheritableRoles": {
    "@odata.type": "microsoft.graph.allAllowedRoles",
    "kind": "allAllowed"
  }
}

Add scopesDisable scope inheritance only (no roles)

To inherit delegated scopes but not application roles, setUse inheritableRolesPATCH to noRoles.

Requestupdate an existing entry. This example disables delegated scope inheritance for Microsoft Graph:

POSTPATCH https://graph.microsoft.com/v1.0/beta/applications/microsoft.graph.agentIdentityBlueprint/bc057821-f236-49d6-9f2c-1ebf43e9437a/inheritablePermissionsmicrosoft.graph.agentIdentityBlueprint/inheritablePermissions/00000003-0000-0000-c000-000000000000
Content-Type: application/json

OData-Version: 4.0

{
  "resourceAppId": "00000003-0000-0000-c000-000000000000",
  "inheritableScopes": {
    "@odata.type": "#microsoft.graph.allAllowedScopes",
    "kind": "allAllowed"
  },
  "inheritableRoles": {
    "@odata.type": "#microsoft.graph.noRoles",
    "kind": "none"
  }
}

Response

HTTP/1.1 201 Created
Content-Type: application/json

{
  "@odata.context": "https://graph.microsoft.com/v1.0/$metadata#applications('bc057821-f236-49d6-9f2c-1ebf43e9437a')/inheritablePermissions/$entity",
  "resourceAppId": "00000003-0000-0000-c000-000000000000",
  "inheritableScopes": {
    "@odata.type": "microsoft.graph.allAllowedScopes",
    "kind": "allAllowed"
  },
  "inheritableRoles": {
    "@odata.type": "microsoft.graph.noRoles",
    "kind": "none"
  }
}

Add roles inheritance only (no scopes)

To inherit application roles but not delegated scopes, set inheritableScopes to noScopes.

Request

POST https://graph.microsoft.com/v1.0/applications/microsoft.graph.agentIdentityBlueprint/bc057821-f236-49d6-9f2c-1ebf43e9437a/inheritablePermissions
Content-Type: application/json
OData-Version: 4.0

{
  "resourceAppId": "00000003-0000-0000-c000-000000000000",
  "inheritableScopes": {
    "@odata.type": "#microsoft.graph.noScopes",
    "kind": "none"
  },
  "inheritableRoles": {
    "@odata.type": "#microsoft.graph.allAllowedRoles",
    "kind": "allAllowed"
  }
}

Response

HTTP/1.1 201 Created
Content-Type: application/json

{
  "@odata.context": "https://graph.microsoft.com/v1.0/$metadata#applications('bc057821-f236-49d6-9f2c-1ebf43e9437a')/inheritablePermissions/$entity",
  "resourceAppId": "00000003-0000-0000-c000-000000000000",
  "inheritableScopes": {
    "@odata.type": "microsoft.graph.noScopes",
    "kind": "none"
  },
  "inheritableRoles": {
    "@odata.type": "microsoft.graph.allAllowedRoles",
    "kind": "allAllowed"
  }
}

Update to disable roles inheritance

IfThe update operation returns 204 No Content when successful. To remove an entry already exists for a resourceAppId,entry, use PATCH to update it rather than attempting to create a duplicate entry, which would result in a 409 Conflict error. The following example disables role inheritance while keeping scope inheritance enabled.

Request

PATCH https://graph.microsoft.com/v1.0/applications/microsoft.graph.agentIdentityBlueprint/bc057821-f236-49d6-9f2c-1ebf43e9437a/inheritablePermissions/00000003-0000-0000-c000-000000000000
Content-Type: application/json
OData-Version: 4.0

{
  "inheritableRoles"DELETE: {
    "@odata.type": "#microsoft.graph.noRoles",
    "kind": "none"
  }
}

Response

HTTP/1.1 200 OK
Content-Type: application/json

{
  "@odata.context": "https://graph.microsoft.com/v1.0/$metadata#applications('bc057821-f236-49d6-9f2c-1ebf43e9437a')/inheritablePermissions/$entity",
  "resourceAppId": "00000003-0000-0000-c000-000000000000",
  "inheritableScopes": {
    "@odata.type": "microsoft.graph.allAllowedScopes",
    "kind": "allAllowed"
  },
  "inheritableRoles": {
    "@odata.type": "microsoft.graph.noRoles",
    "kind": "none"
  }
}

Update to disable scopes inheritance

The following example disables scope inheritance while keeping role inheritance enabled.

Request

PATCH https://graph.microsoft.com/v1.0/applications/microsoft.graph.agentIdentityBlueprint/bc057821-f236-49d6-9f2c-1ebf43e9437a/inheritablePermissions/00000003-0000-0000-c000-000000000000
Content-Type: application/json
OData-Version: 4.0

{
  "inheritableScopes": {
    "@odata.type": "#microsoft.graph.noScopes",
    "kind": "none"
  }
}

Response

HTTP/1.1 200 OK
Content-Type: application/json

{
  "@odata.context": "https://graph.microsoft.com/v1.0/$metadata#applications('bc057821-f236-49d6-9f2c-1ebf43e9437a')/inheritablePermissions/$entity",
  "resourceAppId": "00000003-0000-0000-c000-000000000000",
  "inheritableScopes": {
    "@odata.type": "microsoft.graph.noScopes",
    "kind": "none"
  },
  "inheritableRoles": {
    "@odata.type": "microsoft.graph.allAllowedRoles",
    "kind": "allAllowed"
  }
}

Delete existing inheritable permissions

Request

DELETE https://graph.microsoft.com/v1.0/beta/applications/microsoft.graph.agentIdentityBlueprint/bc057821-f236-49d6-9f2c-1ebf43e9437a/microsoft.graph.agentIdentityBlueprint/inheritablePermissions/00000003-0000-0000-c000-000000000000
OData-Version: 4.0

Response

HTTP/1.1 204 No Content

Related content

Daily Entra.News

Get daily email updates

Get a concise summary of the latest Microsoft Entra updates delivered straight to your inbox.

Loading the secure signup form…