# Azure OpenAI Assistants has no identity of its own: callers use a key or an Entra role on the resource, and the API is retired

Facts read 16 Nov 2026. Page reviewed 16 Nov 2026.

Azure OpenAI Assistants (Preview) is documented by Microsoft as retired in favor of Foundry Agent Service. The quickstart authenticates with an API key; Entra ID with the Cognitive Services OpenAI User role is the documented alternative. The assistant itself holds no cloud role, so its reach is its tools. Read 16 Nov 2026.

## Status first: the Assistants API is retired

Microsoft's page on getting started with Azure OpenAI Assistants (Preview) carries the note that the Assistants API is retired, that the generally available Microsoft Foundry Agents service replaces it, and that a migration guide exists ([Microsoft: getting started with Azure OpenAI Assistants (classic)](https://learn.microsoft.com/en-us/azure/ai-foundry/openai/how-to/assistant), read 16 Nov 2026). The page applies only to the Foundry (classic) portal. Accounts that still run assistants should treat the access below as something to move or remove. The replacement is on [the Foundry Agent Service page](/agent-platforms/foundry-agent-service/).

## The identity: the caller's, because the assistant has none

In the documented quickstart the application creates the client with an API key read from an environment variable. An assistant object is created through the API with instructions, a model deployment and tools. Nothing in the pages read describes a managed identity or service principal assigned to the assistant. Microsoft documents that the Azure OpenAI resource can instead be called with Microsoft Entra ID: your code requests a short-lived token for an identity that holds a role on the resource, which can be your developer account, a system-assigned or user-assigned managed identity, or a service principal ([Microsoft: Entra ID authentication for Azure OpenAI](https://learn.microsoft.com/en-us/azure/ai-foundry/openai/how-to/managed-identity)). An assistant-specific role: none found on 16 Nov 2026.

## What the defaults let a caller do

| Credential | What it allows on the resource | Documented limit |
| --- | --- | --- |
| Resource API key | Calls to the resource's endpoints, including the Assistants API; the quickstart authenticates this way | Microsoft lists viewing and copying keys as a permission separate from the OpenAI User and Contributor roles |
| Cognitive Services OpenAI User role | Chat, completions and inference API calls with Entra ID; view deployments | Cannot create resources or deployments, copy keys, or create customized guardrails |
| Cognitive Services OpenAI Contributor role | Everything in the User role, plus fine-tuning, stored completions and creating or editing deployments | Cannot create resources, view keys or access quota |
| Cognitive Services Contributor role | Create resources in the resource group; view and regenerate keys | Typically granted at the resource group with other roles |

## What the assistant's tools reach

Microsoft documents that an individual assistant can access up to 128 tools, including code interpreter and file search, and custom functions. Code interpreter gives the model a sandboxed Python environment. Custom functions are tools you define, so what they reach depends on the code and the identity behind them. The cloud reach of an assistant is therefore the files you attach plus whatever those functions' identity can reach. See [the identity guide](/guides/the-identity-an-agent-runs-as/) for that second identity.

## How to narrow it

- Call the resource with Microsoft Entra ID and a role of Cognitive Services OpenAI User, assigned at the resource scope rather than the subscription ([check: narrowest scope](/checklist/narrowest-scope/)).
- Microsoft notes that subscription-level Owner and Contributor roles are inherited and take priority over the custom Azure OpenAI roles applied at the resource group, so check for them first.
- Give each application its own managed identity so calls can be traced ([check: attribute actions to the agent](/checklist/attribute-actions-to-the-agent/)).
- Give any function host its own role limited to what that function does ([check: a role per tool](/checklist/tool-own-role/)).
- Plan the migration to Foundry Agent Service, where a new agent identity starts with no roles, as [the Azure agent permissions guide](/guides/ai-agent-permissions-in-azure/) describes.

## Related pages

- [Conversational Agents (Dialogflow CX) default permissions](/default-permissions/conversational-agents/)
- [The identity an AI agent runs as in AWS, Google Cloud and Azure](/guides/the-identity-an-agent-runs-as/)
- [Why an AI agent's permissions are not its user's permissions](/guides/why-an-agents-permissions-are-not-its-users/)
- [All of them](/guides/)

## Sources

- Microsoft: getting started with Azure OpenAI Assistants (classic): https://learn.microsoft.com/en-us/azure/ai-foundry/openai/how-to/assistant (read 16 Nov 2026)
- Microsoft: Azure RBAC for Azure OpenAI (classic): https://learn.microsoft.com/en-us/azure/ai-foundry/openai/how-to/role-based-access-control (read 16 Nov 2026)
- Microsoft: Microsoft Entra ID authentication for Azure OpenAI (classic): https://learn.microsoft.com/en-us/azure/ai-foundry/openai/how-to/managed-identity (read 16 Nov 2026)
- Microsoft: agent identity concepts in Foundry: https://learn.microsoft.com/en-us/azure/ai-foundry/agents/concepts/agent-identity (read 16 Nov 2026)

Last reviewed 16 Nov 2026. Canonical: https://aiagentaccesscontrol.com/default-permissions/azure-openai-assistants/
