Azure Containers built-in role
Container Apps SessionPools Contributor
Container Apps SessionPools Contributor creates, updates, deletes, reads, and performs supported actions on Container Apps session pool. The published role uses Azure control-plane Actions and has no DataActions. Its NotActions explicitly exclude fetching and rotating Session Pool MCP server credentials. Access to container registries, Key Vault, monitoring data, managed identities, networks, and application endpoints remains separately authorized.
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: f7669afb-68b2-44b4-9c5f-6d2a47fddda0
Control-plane actions (15)
Microsoft.Authorization/*/readMicrosoft.Insights/alertRules/*Microsoft.App/sessionPools/*/readMicrosoft.App/sessionPools/*/writeMicrosoft.App/sessionPools/*/deleteMicrosoft.App/sessionPools/*/actionmicrosoft.App/managedEnvironments/readMicrosoft.App/managedEnvironments/*/readMicrosoft.App/managedEnvironments/join/actionMicrosoft.App/managedEnvironments/checknameavailability/actionmicrosoft.App/connectedEnvironments/readMicrosoft.App/connectedEnvironments/*/readMicrosoft.App/connectedEnvironments/join/actionMicrosoft.App/connectedEnvironments/checknameavailability/actionMicrosoft.Resources/deployments/*
Data-plane actions (0)
None — this role grants no data-plane (data access) actions.
Excluded actions (2)
Microsoft.App/sessionPools/fetchMcpServerCredentials/actionMicrosoft.App/sessionPools/rotateMcpServerCredentials/action
Assignable scopes (1)
/
Practical scope
Assign on the individual Container Apps session pool resource when supported, or on its dedicated Container Apps resource group when the principal intentionally manages several related resources. Parent-scope assignments are inherited by every matching Container Apps resource below them.
Common use cases (1)
- Create and manage code-interpreter or custom-container session pools, including pool capacity, network access, image, and lifecycle configuration.
Prerequisites (2)
- The target Container Apps session pool and its Container Apps environment design, workload identity, image source, network boundary, and monitoring destination must be approved.
- Grant the workload identity separate access to registries, Key Vault, storage, messaging, and other dependencies used at runtime.
Best practices (2)
- Assign directly on the Container Apps session pool or a dedicated application resource group and keep environment, workload, and dependency administration separate.
- Review image, command, secrets, identity, ingress, scaling, and network changes through the deployment pipeline before applying them.
Security considerations (2)
- Session-pool configuration controls environments that can execute untrusted code; enabling egress or exposing sensitive environment variables, files, or secrets can let malicious code access or exfiltrate data.
- A broad Azure assignment is inherited by multiple Container Apps resources even though the role has no resource data-plane DataActions.
Assignment guidance
Assign Container Apps SessionPools Contributor at the narrowest Container Apps session pool or dedicated resource-group scope to the identity that needs to creates, updates, deletes, reads, and performs supported actions on Container Apps session pool. Grant connected-resource permissions separately and choose the reader, operator, or contributor variant that matches the documented workflow.
Common questions
When should I assign the Container Apps SessionPools Contributor Azure role?
Assign Container Apps SessionPools Contributor when you need to: Create and manage code-interpreter or custom-container session pools, including pool capacity, network access, image, and lifecycle configuration.. Practical scope: Assign on the individual Container Apps session pool resource when supported, or on its dedicated Container Apps resource group when the principal intentionally manages several related resources. Parent-scope assignments are inherited by every matching Container Apps resource below them.
What permissions does the Container Apps SessionPools Contributor Azure role grant?
The role definition grants 15 combined control-plane and data-plane actions. Representative operations include: Microsoft.Authorization/*/read; Microsoft.Insights/alertRules/*; Microsoft.App/sessionPools/*/read; Microsoft.App/sessionPools/*/write; Microsoft.App/sessionPools/*/delete; and Microsoft.App/sessionPools/*/action. Review the permission sections above for the complete definition and exclusions.
What are the security risks of the Container Apps SessionPools Contributor Azure role?
Key considerations when assigning Container Apps SessionPools Contributor: Session-pool configuration controls environments that can execute untrusted code; enabling egress or exposing sensitive environment variables, files, or secrets can let malicious code access or exfiltrate data.; and A broad Azure assignment is inherited by multiple Container Apps resources even though the role has no resource data-plane DataActions.. Follow the assignment guidance above and use the narrowest practical scope.
Editorial sources (7)
- Azure built-in roles for Containers - Azure RBAC | Microsoft Learn →
Supports: Description, Practical scope, Security considerations. Retrieved 2026-07-17.
- Understand Azure role definitions →
Supports: Description, Security considerations. Retrieved 2026-07-17.
- Steps to assign an Azure role →
Supports: Assignment guidance. Retrieved 2026-07-17.
- Understand scope for Azure RBAC →
Supports: Practical scope, Assignment guidance. Retrieved 2026-07-17.
- Best practices for Azure RBAC →
Supports: Best practices, Assignment guidance. Retrieved 2026-07-17.
- Use session pools in Azure Container Apps →
Supports: Description, Practical scope, Common use cases, Prerequisites, Best practices, Security considerations, Assignment guidance. Retrieved 2026-07-17.
- Azure permissions for Compute - Microsoft.App →
Supports: Description, Practical scope, Common use cases, Prerequisites, Best practices, Security considerations, Assignment guidance. Retrieved 2026-07-17.