跳到主要内容

Restrict Microsoft Entra agent identity blueprint creation to approved creators

Implementation Effort: Low - Requires reviewing a tenant setting and establishing an approved creator-access model.
User Impact: Medium - Ordinary users may need a delegated creator role or an administrator-assisted route to create new blueprints.

Overview​

Microsoft Entra agent identity blueprints are reusable templates for creating agent identities. Restricting the default permission to create blueprints helps establish accountability before new agents are introduced.

This supports Use least privilege access by reserving creation for approved people and Verify explicitly through a defined authorization boundary. A delegated creator route avoids making broad administrator privileges a routine development prerequisite.

Prerequisites​

  • Cloud Application Administrator access to manage the relevant tenant setting.
  • An inventory of legitimate creators and an agreed onboarding route with development teams.
  • An authorized role-assignment process for approved creators, including the Agent ID Developer role where appropriate.
  • Ownership of existing blueprints and source-platform permissions is understood.

Limitations​

  • Users can create blueprints by default. Restricting that default leaves creation available to authorized administrators and users with the Agent ID Developer role.
  • Permission to change the tenant setting does not itself grant permission to assign roles.
  • The setting does not remove existing blueprint ownership or restrict every application-permission or source-platform creation path.
  • It does not approve agent publication, grant runtime permissions, or replace app-registration and consent governance.

Reference​