Why I Turn Off “Users Can Create Agent Blueprints” in Entra ID

Microsoft is rolling out a new switch in Entra ID called Users can create agent blueprints. You’ll find it next to “Users can register applications” in the user settings, and it starts out set to Yes. In the tenants I manage, I set it to No, and unless your organization has a clear reason to leave it open, I recommend you do the same.

What an agent blueprint is

Entra Agent ID gives AI agents their own identities in your directory. An agent blueprint is the template behind those identities. It holds the name, owners, sponsors, permissions and authentication settings, and every agent identity you create from it inherits that setup. The docs and Microsoft Graph call it an agent identity blueprint, so you’ll see both names.

When a user creates a blueprint, Entra makes that user the owner of both the blueprint and its blueprint principal. As owner, they can create agent identities from it without holding any Agent ID role.

What Microsoft changed

Microsoft announced the setting in message center post MC1506733. The rollout began on November 4, 2026, and Microsoft expects to finish it worldwide by late November. With the default of Yes, any user without an admin role or custom role can create blueprints in your tenant.

When you set it to No:

• Default users lose the ability to create new blueprints.
• Admins and users with the Agent ID Developer role keep the ability.
• Existing blueprints stay as they are.
• Who can create agent identities from existing blueprints doesn’t change.

Users can register applications is a separate switch. Turning one off leaves the other untouched, so check both.

Why I turn it off

It repeats the app registration problem. Most of us restricted “Users can register applications” years ago. User-created app registrations piled up with no owner, no review and secrets nobody rotated. Agent blueprints open the same door for AI agents, and agents tend to ask for more data access than a typical internal app.

A compromised account gets a foothold. If an attacker signs in as a regular user, the default lets them create a blueprint, become its owner and create agent identities in your tenant. Those objects look legitimate, and few admins monitor agents today.

You haven’t built the process yet. Agent ID is new. Few organizations have decided who sponsors an agent, who reviews it or when it gets removed. Limiting creation to a small group buys you time to set up that process before agents spread across the tenant.

The people who need it keep access. Give the Agent ID Developer role to the developers who build agents. They keep working, and you know who creates what.

Turn it off in the Entra admin center

1. Sign in to the Microsoft Entra admin center as at least a Cloud Application Administrator.
2. Go to Entra ID > Users > User settings.
3. Under Default user role permissions, set Users can create agent blueprints to No.
4. Select Save.

If you can’t see the option, the rollout hasn’t reached your tenant. Check again in a few days.

Turn it off with PowerShell

The setting lives in the tenant’s authorization policy, under defaultUserRolePermissions. The property below comes from the Graph beta endpoint, so test it in a lab tenant before you script it into production.

Connect-MgGraph -Scopes "Policy.ReadWrite.Authorization"

$uri = "https://graph.microsoft.com/beta/policies/authorizationPolicy/authorizationPolicy"

# Check the current value
(Invoke-MgGraphRequest -Method GET -Uri $uri).defaultUserRolePermissions

# Turn it off
$body = @{
    defaultUserRolePermissions = @{
        allowedToCreateAgentIdentityBlueprints = $false
    }
} | ConvertTo-Json

Invoke-MgGraphRequest -Method PATCH -Uri $uri -Body $body -ContentType "application/json"

Run the GET command again afterwards. allowedToCreateAgentIdentityBlueprints should show False.

Give developers access the controlled way

Assign Agent ID Developer to the people who build agents. If you use Privileged Identity Management, make the assignment eligible so they activate it when they need it.

Agent ID Developer can create blueprints and configure federated identity credentials on them. Adding a client secret or certificate to a blueprint takes the Agent ID Administrator role, so keep that one for your identity team.

Check what users created before you changed it

If your tenant ran with the default for a few days, users may have created blueprints in that window. Turning the setting off doesn’t remove them.

Go to Entra ID > Agents > Agent blueprints and look at each one: who created it, who owns it and who sponsors it. Delete the ones nobody can explain, and assign a sponsor to the ones you keep.

My recommendation

Set Users can create agent blueprints to No, give Agent ID Developer to the few people who build agents, and look through the blueprint list once a month while Agent ID matures. If you haven’t checked Users can register applications in a while, set that to No while you’re on the same page.

Sources: MC1506733, Microsoft Learn: Restrict who can create applications and agents, Microsoft Learn: Create an agent identity blueprint