Azure AI + machine learning built-in role

Foundry User

Provides reader access to a Foundry account and project plus project DataActions for building and testing AI applications. It has no Foundry account or project management writes and no role-assignment authority. Plane reconciliation is required: the canonical definition also includes resource-key listing and Resource Manager deployment Actions, but the current Foundry matrix still marks model management unavailable.

Role-definition permissions are imported from Microsoft Learn. Practical scope, use cases, prerequisites, best practices, security considerations, assignment guidance, and relationships have been reviewed against the official sources below.

Role definition ID: 53ca6127-db72-4b80-b1b0-d745d6d5456d

Control-plane actions (14)

Data-plane actions (1)

Excluded actions (0)

None

Assignable scopes (1)

Practical scope

For one project, assign Foundry User on that project and Reader on the parent Foundry resource. Assign Foundry User on the Foundry resource only when the principal needs inherited builder access to its projects. For a published Agent Application, assign Foundry User on that application resource; direct agent endpoints instead use Foundry Agent Consumer at project or agent scope.

Common use cases (2)

Prerequisites (3)

Best practices (3)

Security considerations (3)

Assignment guidance

Assign Foundry User on the specific project plus Reader on the parent Foundry resource for developers or testers that build applications. Use Foundry-resource scope only for intended inherited project access. For endpoint-only access, use Foundry Agent Consumer on a direct agent or Foundry User on a published Agent Application, as documented. Prefer Microsoft Entra authentication and elevate only for documented publishing or model-management duties.

Related roles (3)

Common questions

When should I assign the Foundry User Azure role?

Assign Foundry User when you need to: Build and test agents or applications against predeployed models in a Foundry project.; and Perform project development DataActions without creating Foundry accounts or projects, publishing agents, assigning roles, or managing models.. Practical scope: For one project, assign Foundry User on that project and Reader on the parent Foundry resource. Assign Foundry User on the Foundry resource only when the principal needs inherited builder access to its projects. For a published Agent Application, assign Foundry User on that application resource; direct agent endpoints instead use Foundry Agent Consumer at project or agent scope.

What permissions does the Foundry User Azure role grant?

The role definition grants 15 combined control-plane and data-plane actions. Representative operations include: Microsoft.Authorization/*/read; Microsoft.CognitiveServices/*/read; Microsoft.CognitiveServices/accounts/listkeys/action; Microsoft.Insights/alertRules/read; Microsoft.Insights/diagnosticSettings/read; and Microsoft.Insights/logDefinitions/read. Review the permission sections above for the complete definition and exclusions.

What are the security risks of the Foundry User Azure role?

Key considerations when assigning Foundry User: The role has broad Foundry project DataActions and can process project data even though the current product matrix withholds Foundry account and project management and model management.; Its canonical listKeys Action can expose API keys. Foundry security documentation states that keys provide full resource access, cannot express user identity or granular scope, are harder to audit, and are not recommended for production.; and Canonical Resource Manager deployment Actions remain effective control-plane permissions even though they do not make this a Foundry model-management role; review them when a custom role is needed.. Follow the assignment guidance above and use the narrowest practical scope.

Editorial sources (9)

Official Microsoft Learn documentation →