What is Microsoft Entra Agent ID?

The rise of AI agents requires new security strategies. Microsoft Entra is addressing this with its new feature that has just appeared in the Microsoft Entra admin centre, Agent Identity (Agent ID), currently in public preview.

This feature provides a specialised identity for AI agents, similar to the existing identities for users, applications (service principals) and devices, allowing them to securely access resources. In this article, I will explore the new blade in Microsoft Entra as well as some of the components which have appeared in the Microsoft Graph API documentation.

What is Agent ID in Microsoft Entra?

As of November 17th 2025, Agent ID (preview) has just appeared in the Microsoft Entra admin center, providing all new controls for admins to manage identities relating to their AI agents. The image below depicts what the new admin center features look like:

Agent ID preview
Agent ID preview

The Overview tab provide you high-level information, such as the number of agents created in the last 30 days, which agents do not have owners or sponsors, which agents are active and which agents do not have identities. Your view of Agents is also broken down by agent type, where:

  • Agent identities (with no user)
  • Agent identities (with user)
  • Agents with service principals
  • Agents with no identities

The All agent identities (Preview) tab, shows you a list of all agent identities in your tenant, including the Name, date created, status and Object ID (so it can be queried with code). I don’t have any agent identities in my tenant, but as you can see from the below image, you can also apply filters to this list.

All agents list
All agents list

The Agent Registry (Preview) tab shows you a list of all agents in your tenant and what data they have access to. Think if it like an agent directory… one agent can utilise the Agent registry to look up all agents and understand what data they can access, then it can use that information to dynamically choose the most appropriate agent for the task at hand.

Agent Registry Entra
Agent Registry Entra

The Agent collections (Preview) tab shows a list of all Agents that have been grouped into predefined collections based on their trust level and visibility. These agents can be manually added to predefined or custom collections. I presume additional filtering can be done by collection and that collections can be used by other agents to determine which agents can be utilised by them agents. Custom role assignments can also be granted to these collections which can be assigned to also all principals types, include users, groups and Enterprise applications.

Agent collections Entra
Agent collections Entra

Some of the Microsoft Graph API documentation was also updated to include these Agent Identities, Agent Identity Blueprints and Agent Identity Blueprint principals, which I will explore below.

Microsoft Graph Agent updates

What are Agent Identities?

Something core that needs address is, what are Agent Identities? Well, an Agent Identity is a new type of identity in Microsoft Entra specifically designed for AI agents. Think of it as a dedicated account that an AI agent can use to authenticate and be granted permissions within the Microsoft Entra ecosystem.

According to the Microsoft Graph documentation, the “agentIdentity” resource represents this account in your Entra ID directory. Technically, it inherits from the familiar “servicePrincipal” object, but it’s distinguished by its “servicePrincipalType” property, which is set to “ServiceIdentity“. This specialisation allows for tailored management and governance of your AI agents, separate from standard application service principals.

Interestingly… a key property of an “agentIdentity” is the “agentIdentityBlueprintId“. This property seems to link the agent identity back to the template that was used to create it, which brings us to our next component.

What is an Agent Identity Blueprint?

An Agent Identity Blueprint (or agentIdentityBlueprint as seen in Microsoft Graph) is the template used to create new agent identities. It centralises the configuration and defines the common properties for all agent identities that will be stamped out from it. Liken it to an App Registration, that serves as the blueprint for Enterprise applications…

This resource inherits from the application object in Microsoft Graph. Which is logical, as like I said, it acts much like an “app registration” does for a traditional application, but in this case, it’s defining the model for AI agents.

By using a blueprint, an organisation can ensure that all agent identities created for a specific purpose (e.g., “Invoice Processing Bots”) share the same base configuration, roles, and properties. This template-based approach is crucial for maintaining consistency and security at scale.

What is an Agent Identity Blueprint Principal?

This is where the concepts of Agents and Blueprints tie together. The Agent Identity Blueprint Principal (or agentIdentityBlueprintPrincipal) is the implementation of the blueprint (on the “backend”) within your tenant.

If the agentIdentityBlueprint is the template (like an app registration), the agentIdentityBlueprintPrincipal is the instance of that template in your directory (again like the enterprise application or service principal).

This resource also inherits from servicePrincipal. Its job is to act as the managing entity or “principal” within your tenant. You use this blueprint principal to actually create the individual agent identities (agentIdentity resources) in your directory. It will also allows you to perform identity management operations that can affect all agent identities that were created from it, providing a centralised point of control.

In short, the workflow is:

  1. You define a Blueprint (the template).

  2. This creates a Blueprint Principal (the instance) in your tenant.

  3. You use the Blueprint Principal to create and manage multiple Agent Identities (the individual accounts for your AI agents).

Final points

As of writing this post, the Agent ID (preview) section of the Microsoft Entra admin center has only been available for a few hours and I feel like I am only scratching the surface. I have yet to deep dive into many of these capabilities, but I’ll been keeping a close eye on further announcements at Microsoft Ignite 2025 as well as changes in the Microsoft documentation on msdocstracker.com

Daniel Bradley

Daniel Bradley is a UK-based technical architect and Microsoft MVP in Security. He specialises in Microsoft Entra, Intune, and Microsoft Graph PowerShell and is the author of Microsoft Graph PowerShell for Administrators. He writes and edits Our Cloud Network using experience gained from working with Microsoft cloud environments.

Leave a Reply