Skip to content
AI Agent Access Control

What an AI agent can access in Azure, and the controls that bound it

In Azure, an AI agent runs as a managed identity or an Entra agent identity, and can reach whatever that identity's permissions and the network allow. The map covers 2 ways to run one: Microsoft Foundry Agent Service; Self-hosted agent on Azure Container Apps or AKS.

The map ยท The checklist

In Azure the agent is a Microsoft Entra agent identity in Foundry Agent Service, or a managed identity on Container Apps and AKS. Foundry gives a new agent identity no resource permissions, so access is whatever you assign with Azure RBAC. The checklist asks for assignment at resource or resource group scope rather than subscription scope (ab-10) and deny assignments as the ceiling (ab-07, ab-08), noting that customer-managed deny assignments are in private preview.

Network and logs need deliberate setup. Foundry's Standard Setup with private networking removes public egress (ab-15); Container Apps and AKS are open by default. Entra sign-in logs show which agent identity got a token and for which user (ab-29), and resource logs are not collected until you create a diagnostic setting (ab-28). Restricting who can attach a managed identity: none found on 2026-11-10 (ab-03).

Agent platformRuns asNetwork
Microsoft Foundry Agent Service (formerly Azure AI Foundry Agent Service)Each agent gets a Microsoft Entra agent identity, a special service principal created under an agent blueprint.Microsoft documents a Standard Setup with private networking: no public egress and a delegated subnet from your virtual network.
Self-hosted agent on Azure Container Apps or AKSA container app can have a system-assigned managed identity (tied to the app) or user-assigned identities (standalone resources).By default Container Apps is publicly accessible and can communicate only with internet-accessible endpoints; supplying your own virtual network adds control over outbound traffic and access to private endpoints.

The checklist, Azure column

Where Act is behind

Act draws the boundary at the access layer (cloud IAM and network controls, and the gateways or MCP servers in front of agents); it does not inspect prompts or model outputs, which needs a different tool. Your team applies the boundaries it proposes, and its customer evidence for AI boundaries is less mature than for its core access control.

Sources

  1. learn.microsoft.com/en-us/azure/ai-foundry/agents/overview, read 10 Nov 2026
  2. learn.microsoft.com/en-us/azure/ai-foundry/concepts/rbac-foundry, read 10 Nov 2026
  3. learn.microsoft.com/en-us/azure/ai-foundry/agents/concepts/agent-identity, read 10 Nov 2026
  4. learn.microsoft.com/en-us/azure/ai-foundry/agents/concepts/hosted-agents, read 10 Nov 2026
  5. learn.microsoft.com/en-us/azure/ai-foundry/agents/how-to/tools/openapi, read 10 Nov 2026
  6. learn.microsoft.com/en-us/azure/ai-foundry/agents/how-to/tools/function-calling, read 10 Nov 2026
  7. learn.microsoft.com/en-us/azure/ai-foundry/agents/how-to/virtual-networks, read 10 Nov 2026
  8. learn.microsoft.com/en-us/azure/ai-foundry/how-to/azure-policy, read 10 Nov 2026
  9. learn.microsoft.com/en-us/azure/container-apps/managed-identity, read 10 Nov 2026
  10. learn.microsoft.com/en-us/azure/aks/workload-identity-overview, read 10 Nov 2026

Last reviewed 16 Nov 2026.