In Azure an agent's access is the RBAC roles granted to its Entra agent identity or managed identity, and a new identity starts with none
Facts read 10 Nov 2026. Page reviewed 16 Nov 2026.
Microsoft Foundry Agent Service gives each agent a Microsoft Entra agent identity that starts without roles. This guide covers agent identities, project and managed identities, the Foundry RBAC roles and their renaming, how tools authenticate, key-based access that bypasses roles, and the documented limits on deny assignments.
Each Foundry agent has an Entra agent identity that starts empty
Microsoft documents that each agent in Foundry Agent Service gets a Microsoft Entra agent identity, a special service principal created under an agent blueprint. Hosted agents get a dedicated agent identity at deploy time. Microsoft also documents that a newly created agent identity has no resource permissions and that Foundry does not automatically assign RBAC roles to it. An administrator grants access through the target service, such as a storage account or Key Vault. The practical result is that a Foundry agent's reach equals the role assignments someone made for its identity.
Shared project identities weaken the separation
A project-wide managed identity also exists. Microsoft documents that legacy agents sharing the project's managed identity have no per-agent separation, which means their access is pooled (check). Managed identities in general come in two kinds. A system-assigned identity is enabled on one resource and is deleted with it. A user-assigned identity is a standalone resource that you can assign to several resources. Microsoft documents that managed identities remove the need to manage credentials (check). For agents you run yourself on Container Apps or AKS, choose the identity type deliberately: the first ties access to one app, and the second makes the sharing visible.
Foundry roles were renamed and one role fits agent callers
Microsoft renamed its Foundry roles: Foundry User, Foundry Owner, Foundry Account Owner and Foundry Project Manager were previously called Azure AI User, Azure AI Owner, Azure AI Account Owner and Azure AI Project Manager. Role IDs and core permissions are unchanged, and the old names still appear in places. A person or service principal that only needs to call agents, for example through the Responses API, should hold Foundry Agent Consumer instead of Foundry User, which Microsoft calls the least-privilege access for agent consumers. You can assign Foundry roles at agent scope, so access to one agent's endpoints does not extend to all agents in the project (check).
Keys bypass the roles, and tools may use another identity
Microsoft documents that RBAC roles apply when you authenticate with Microsoft Entra ID, and that with key-based authentication the key grants full access without role restrictions. So the review must find out whether keys are in use. On the tools side, MCP and A2A tools receive a scoped agent identity token and the downstream resource checks that identity's role assignments. Tool connections can instead use keys, the agent's or the project's managed identity, or OAuth identity passthrough, and OpenAPI tools support anonymous, API key or project managed identity authentication. With function calling, your own application executes the function, under whatever identity your code holds. List each tool and the authentication it uses (check).
Logs and networks complete the Azure picture
Microsoft documents that Entra sign-in logs show which agent identity obtained a token for which resource, including on behalf of which user, and that Entra audit logs record blueprint and agent identity creation and deletion. Foundry tracing in Application Insights covers tool calls. For network access, Microsoft documents a Standard Setup with private networking and no public egress, and a private endpoint for the Foundry account and its projects. The network guide and the logging guide cover both in more detail, and the map lists the Foundry entry beside the AWS and Google Cloud ones.
Self-hosted agents use managed identities and Workload ID
An agent you run yourself on Azure Container Apps uses a managed identity, and Microsoft documents that you can control which managed identities are available to the app. On AKS, Microsoft Entra Workload ID is how pods authenticate to Entra-protected services such as Key Vault and Microsoft Graph, using the cluster's OIDC issuer. Microsoft documents that on AKS Automatic clusters workload identity is preconfigured, while on AKS Standard you enable it yourself. A default role grant for either platform was none found on 2026-11-10 in the pages read, so the role assignments someone made for the identity set its reach.
Scope assignments narrowly, and treat deny assignments as limited
Microsoft's RBAC guidance is to grant the least privilege needed and to avoid broader roles at broader scopes (check). Assign at resource or resource group scope, not subscription or management group scope. Azure role assignment conditions can filter a role by attributes (check). Deny assignments block listed actions even when a role grants them, but Microsoft documents customer-managed deny assignments as currently in private preview, so for now a ceiling comes from management group governance and from keeping the agent in its own subscription (check). Review role assignments on a schedule with Entra access reviews (check). Microsoft also documents that Azure Policy helps you audit and govern resource state for Foundry resources, which is a way to report when an agent project drifts.
Related pages
Sources
- Microsoft: agent identity in Foundry Agent Service, read 10 Nov 2026
- Microsoft: role-based access control for Microsoft Foundry, read 10 Nov 2026
- Microsoft: managed identities for Azure resources, read 10 Nov 2026
- Microsoft: Azure RBAC best practices, read 10 Nov 2026
- Microsoft: Azure deny assignments, read 10 Nov 2026
- Microsoft: managed identities in Azure Container Apps, read 10 Nov 2026
Last reviewed 16 Nov 2026.