Skip to content

Who Can Create AI Agents in Your Tenant? The Microsoft Entra Change Texas SMBs Should Review

By Donovan Brown
November 16, 2026
8 sections
Who Can Create AI Agents in Your Tenant? The Microsoft Entra Change Texas SMBs Should Review — IT Services article cover card from LayerLogix, with a user identity icon

Microsoft Entra now lets regular users create AI agent identities by default. Here is the identity security setting Texas SMBs should review and how to govern agents.

01

Introduction

Starting in November 2026, Microsoft changed a default inside Microsoft Entra that most small businesses never think about: who is allowed to create AI agents in your Microsoft 365 tenant. Unless an administrator turns it off, ordinary users can now create agent blueprints, the identity templates that AI agents use to sign in and act on your data. For a Texas SMB that has spent the last two years locking down identity, that is a new door opening quietly. This guide explains what changed, why it matters, and the exact settings to review this week.

02

What Microsoft Changed in Entra

Microsoft announced two related changes through the Microsoft 365 Message Center (MC1506733 and MC1506728), with rollout beginning in early November 2026 and expected to finish by late November:

  • Default users can create agent blueprints. From November 4, 2026, any user without an admin or custom role can create agent blueprints unless the new tenant setting "Users can create agent blueprints" is set to No. Administrators and users holding the Agent ID Developer role keep that ability either way.
  • Agents no longer get identity-creation rights automatically. Entra is stopping the automatic grant of the Microsoft Graph permission AgentIdentity.CreateAsManager to agent blueprints. Going forward, an administrator has to grant it explicitly to the agents that need to create their own identities.

The first change widens who can build agents. The second tightens what those agents can do on their own. Both land on your tenant whether or not anyone at your company is paying attention, which is why they belong on your IT checklist now.

03

Why Agent Identities Are a Security Issue

An AI agent is not just a chatbot. Once it has an identity in Entra, it can be granted permissions to read mailboxes, SharePoint sites, Teams chats, or line-of-business data, and it can act without a person signing in each time. That makes agents a new class of non-human identity, the same category as service accounts and app registrations that attackers love because they rarely have MFA and are rarely reviewed.

When any employee can create one, you risk the same pattern we saw with shadow IT: well-meaning staff wiring an agent to client files or financial data with no review, no owner of record, and no plan for when that employee leaves. We cover the broader risk in is your AI agent a security risk, and the governance side in our shadow AI governance playbook for Texas SMBs.

04

Decide Who Should Be Allowed to Build Agents

There is no single right answer, but there should be a deliberate one. For most Houston-area businesses under 250 employees, we recommend:

  1. Set "Users can create agent blueprints" to No. You will find it in the Entra admin center under Entra ID, then Users, then User settings, in the Default user role permissions section.
  2. Assign the Agent ID Developer role to the small number of people who actually build agents, such as an internal IT lead or a named power user, instead of leaving it open to everyone.
  3. Review "Users can register applications" at the same time. Microsoft notes it is a separate toggle. Leaving app registration open while closing agent creation leaves a similar gap.
  4. Write the rule down. Add agent creation to your AI acceptable use policy so staff know how to request one. Our guide to a Texas TRAIGA-aligned AI acceptable use policy shows where it fits.

This follows the same principle as least-privilege access control: give the ability to the few who need it, and make everyone else ask.

05

Check Existing Agents Before They Break

The second change can cause outages. If you already run agents that create identities on their own (an app-only process, with no signed-in user), and they relied only on the automatic AgentIdentity.CreateAsManager grant, those requests will start failing with a 403 authorization error once enforcement reaches your tenant. Agents that use a directory role to create identities are not affected, and existing blueprints and identities are not removed.

To find agents at risk:

  • In Entra, open Audit Logs and filter Category to ApplicationManagement and Activity to Add Service Principal. Look for entries where the initiator is an application and the target is an agent identity.
  • For each, open Agent blueprints, find the blueprint, and check Granted permissions. If nothing else there allows identity creation, it depends on the old automatic grant.
  • Grant the permission explicitly through admin consent only for agents you have reviewed and still want, then test identity creation.

Treat this as a free inventory exercise. Every agent you find should have a business owner, a purpose, and a review date, just like any other account in your Entra Conditional Access design.

06

Govern Agents Like Any Other Identity

Once creation is controlled, keep the agents you approve on a short leash:

  • Scope data access narrowly. An agent that summarizes help desk tickets does not need the finance SharePoint site. Fixing broad permissions first matters here exactly as it does for Microsoft 365 Copilot readiness.
  • Log and review. Keep agent sign-ins and permission grants in your audit trail, and fold them into the log retention and SIEM data sources you already collect.
  • Offboard agents too. When the employee who owned an agent leaves, reassign or remove it as part of employee offboarding and deprovisioning.
  • Review quarterly. Add agent count and permissions to your quarterly IT review so growth is visible to leadership.

If your firm builds agents in Copilot Studio, the same discipline applies there; see governing Copilot Studio agents.

07

Where to Start

This week, have whoever administers your Microsoft 365 tenant answer three questions: Is "Users can create agent blueprints" set the way you intend? Who holds the Agent ID Developer role? Do any existing agents rely on the automatic permission that is going away? That review takes under an hour for most small tenants. If you do not have a dedicated admin, our Microsoft 365 managed services team handles these Entra changes for Houston-area businesses, and our cybersecurity services team can fold agent identities into your broader security program. For a view of where Texas companies stand on identity controls, see the Texas SMB IT and cybersecurity benchmark report.

Back to Blog
Keep Reading

Related Articles

Need Expert IT Support?

Let our team help your Houston business with enterprise-grade IT services and cybersecurity solutions.

Call NowBook a Call