Microsoft 365 tenant · Applications, consent & AI agents

Restrict creation of agent identity blueprints to administrators

When it fails: Any user can create agent identity blueprints. Users can create the templates that AI agent identities are built from, outside any review by identity administrators.

CB-M365-APPS-020mediumactivemanualprofile baseline

Description

In Microsoft Entra Agent ID, an agent identity blueprint defines how AI agent identities are created: their credentials, the permissions they can request and the redirect URIs used during consent. The default user role permission Users can register agent identity blueprints lets every member user create one. It is separate from Users can register applications (CB-M365-APPS-001): turning that one off does not block blueprints.

Set the permission to No, so that only administrators and holders of the Agent ID Developer or Agent ID Administrator roles create blueprints.

The Graph property is defaultUserRolePermissions.allowedToCreateAgentIdentityBlueprints on the beta endpoint of /policies/authorizationPolicy; v1.0 does not return it yet. During the rollout, the toggle may not appear in every tenant.

Rationale

A blueprint created by an ordinary user can request broad permissions, carry long-lived secrets and spawn agent identities that nobody in identity administration knows about. Limiting creation to a small set of roles keeps AI agents inside the same review process as applications. Microsoft enables the permission for all users by default in November 2026.

Impact

Developers who build agents must request the Agent ID Developer role or go through an administrator. Existing blueprints are not removed by the change.

Setting

LocationMicrosoft Entra admin center > Entra ID > Users > User settings > Default user role permissions
DefaultYes
RecommendedNo

Audit

  1. Sign in to the Microsoft Entra admin center (https://entra.microsoft.com) as at least a Global Reader.
  2. Browse to Entra ID > Users > User settings.
  3. Under Default user role permissions, read Users can register agent identity blueprints.
  4. Alternative (read-only): Invoke-MgGraphRequest -Method GET -Uri 'https://graph.microsoft.com/beta/policies/authorizationPolicy' and read defaultUserRolePermissions.allowedToCreateAgentIdentityBlueprints.
  5. Fail if the setting is Yes (or true).

Remediation

  1. Sign in to the Microsoft Entra admin center as at least a Privileged Role Administrator.
  2. Browse to Entra ID > Users > User settings.
  3. Set Users can register agent identity blueprints to No and select Save.
  4. Grant the Agent ID Developer role to the people who build agents.

Rollback

Set Users can register agent identity blueprints back to Yes.

References

Mappings

FrameworkIDRelation
NIST SP 800-53 Rev. 55.1.1CM-11related
NIST SP 800-53 Rev. 55.1.1AC-6related

How this control relates to the other framework's: equivalent, stricter, looser, partial or related.

People and lifecycle

Authors
Introduced inv0.1.0
Created, updated2026-10-24, 2026-10-24
Translationsfr