top of page

Who Can Create AI Agents in Microsoft 365? The Entra Setting to Turn Off

Writer: Dane Gray
Dane Gray
1 day ago
4 min read

Quick answer: Since November 4, 2026, any regular user in your Microsoft 365 tenant can create a Microsoft Entra agent blueprint, the starting point for an AI agent's identity, unless an administrator turns it off. The setting is called "Users can create agent blueprints," and it's on by default. It stays on even if you already blocked users from registering apps, so turn off both "Users can register applications" and "Users can create agent blueprints." 24uNet turns off agent blueprint creation by default in the Microsoft 365 tenants we manage.

Microsoft announced the change in Message Center notice MC1506733 (public mirror), "Review who can create agents in Microsoft Entra." Rollout started in early November and is expected to finish by late November 2026.

What an agent blueprint is

AI agents that act inside Microsoft 365 need their own identity in Microsoft Entra, the same directory that holds your users' sign-ins. An agent blueprint is the template that agent identities are created from. Per Microsoft Learn's page on creating an agent identity blueprint, the person who creates a blueprint can become its owner, and owners can create agent identities from it.

In plain words: with the setting on, any employee can start creating identities for AI agents in your tenant, without an admin approving it.

What changed on November 4

Microsoft changed who can create agent blueprints by default. According to MC1506733:

  • Default users, meaning users without a built-in or custom Entra role, can create new agent blueprints.

  • If you set the toggle to No, default users can't create new agents. Supported administrators and users assigned the Agent ID Developer role still can.

  • Turning it off doesn't remove agent blueprints that already exist, and it doesn't change who can create agent identities from existing blueprints.

  • It also doesn't block an app or an agent from creating identities.

  • The setting is independent of "Users can register applications." Microsoft says to review both settings separately.

That last point is the one most businesses miss. Plenty of tenants already block users from registering apps. That doesn't block agent blueprints.

How to turn it off

Microsoft Learn's page on restricting who can create applications and agents gives these steps:

  1. Sign in to the Microsoft Entra admin center as at least a Cloud Application Administrator.

  2. Browse to Entra ID > Users > User settings.

  3. Set Users can create agent blueprints to No.

  4. On the same page, set Users can register applications to No.

  5. Save the change.

With agent blueprints off, creation is limited to administrators and users assigned the Agent ID Developer role. If someone on your team has a real need to build agents, an admin can assign that role to that person instead of leaving it open to everyone.

For the technical reader: so far the setting shows only in Microsoft's beta Graph API, as allowedToCreateAgentIdentityBlueprints on the authorization policy. Setting it to false is the same org-wide change as the admin center toggle.

Check what already exists

Turning the setting off stops new blueprints. It doesn't clean up anything created since November 4. After you change it, look in Entra ID > Agents > Agent blueprints in the Entra admin center for blueprints nobody expected, and ask who created them and why.

This fits with the other app access checks we've written about. If you haven't reviewed which apps already have access to your company data, start with Check Apps With Microsoft 365 Access. If anything looks like someone else is using an account, work through the Microsoft 365 compromised account checklist. For this month's other Microsoft 365 items, see Microsoft 365 outage: what to check and patch.

What 24uNet does

24uNet turns off "Users can create agent blueprints" by default in the Microsoft 365 tenants we manage, and new tenants get the same setting at onboarding.

That's part of how 24uNet BusinessCare handles identity: separate admin accounts and standard-user access, and MFA enforced on every account by default; any exception is documented in writing. BusinessCare is built for Microsoft 365 Business Premium or equivalent, licensed by your business.

If your business handles client financial data, see cybersecurity for RIAs and financial services businesses.

Find your next step

Book the $299 BusinessCare Walkthrough: about an hour on what's in place, what's missing and what closing each gap would involve, with nothing installed. You keep the written findings, and the $299 is credited to your first month of service.

Not sure yet? Talk to our team.

Frequently asked questions

Can regular users create AI agents in Microsoft 365?

Yes, by default. Since November 4, 2026, users without an Entra admin role can create Microsoft Entra agent blueprints and the agent identities that come from them, unless an administrator sets "Users can create agent blueprints" to No.

Where is the "Users can create agent blueprints" setting?

In the Microsoft Entra admin center, under Entra ID > Users > User settings. Sign in as at least a Cloud Application Administrator, set "Users can create agent blueprints" to No, and save.

If we already blocked app registration, are agent blueprints blocked too?

No. Microsoft says the agent blueprint setting is independent of "Users can register applications." Turn off both settings.

Who can still create agents after we turn the setting off?

Administrators and users assigned the Agent ID Developer role. Existing agent blueprints stay in place, so review them after you change the setting.

Does 24uNet turn this setting off for clients?

Yes. 24uNet turns off "Users can create agent blueprints" by default in the Microsoft 365 tenants we manage, and new tenants get the same setting at onboarding.

Sources

 
 
 

Comments


bottom of page