Azure Containers built-in role
Container Apps ConnectedEnvironments Contributor
Container Apps ConnectedEnvironments Contributor creates, updates, deletes, reads, and performs supported actions on Container Apps connected environment. The published role uses Azure control-plane Actions and has no DataActions. It can invoke Microsoft.App/connectedEnvironments/daprComponents/listSecrets/action to list secrets of connected-environment Dapr components; secret listing is an Azure Action and must not be mistaken for an absence of secret-bearing authority merely because the role has no secret DataAction. 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: 6f4fe6fc-f04f-4d97-8528-8bc18c848dca
Control-plane actions (9)
Microsoft.Authorization/*/readMicrosoft.Insights/alertRules/*Microsoft.App/connectedEnvironments/*Microsoft.App/connectedEnvironments/*/readMicrosoft.App/connectedEnvironments/*/writeMicrosoft.App/connectedEnvironments/*/deleteMicrosoft.App/connectedEnvironments/*/actionMicrosoft.App/connectedEnvironments/daprComponents/listSecrets/actionMicrosoft.Resources/deployments/*
Data-plane actions (0)
None — this role grants no data-plane (data access) actions.
Excluded actions (0)
None
Assignable scopes (1)
/
Practical scope
Assign on the individual Container Apps connected environment 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 the Container Apps connected-environment Azure resources used to host Container Apps on an approved Arc-enabled Kubernetes cluster.
Prerequisites (2)
- The target Container Apps connected environment 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 connected environment 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 (3)
- Connected-environment changes can alter or remove the Azure control-plane representation and configuration for Container Apps workloads hosted on the Arc-connected cluster.
- The role can invoke Microsoft.App/connectedEnvironments/daprComponents/listSecrets/action to list secrets of connected-environment Dapr components, which can disclose credentials or other sensitive configuration to the assignee.
- 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 ConnectedEnvironments Contributor at the narrowest Container Apps connected environment or dedicated resource-group scope to the identity that needs to creates, updates, deletes, reads, and performs supported actions on Container Apps connected environment. 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 ConnectedEnvironments Contributor Azure role?
Assign Container Apps ConnectedEnvironments Contributor when you need to: Create and manage the Container Apps connected-environment Azure resources used to host Container Apps on an approved Arc-enabled Kubernetes cluster.. Practical scope: Assign on the individual Container Apps connected environment 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 ConnectedEnvironments Contributor Azure role grant?
The role definition grants 9 combined control-plane and data-plane actions. Representative operations include: Microsoft.Authorization/*/read; Microsoft.Insights/alertRules/*; Microsoft.App/connectedEnvironments/*; Microsoft.App/connectedEnvironments/*/read; Microsoft.App/connectedEnvironments/*/write; and Microsoft.App/connectedEnvironments/*/delete. Review the permission sections above for the complete definition and exclusions.
What are the security risks of the Container Apps ConnectedEnvironments Contributor Azure role?
Key considerations when assigning Container Apps ConnectedEnvironments Contributor: Connected-environment changes can alter or remove the Azure control-plane representation and configuration for Container Apps workloads hosted on the Arc-connected cluster.; The role can invoke Microsoft.App/connectedEnvironments/daprComponents/listSecrets/action to list secrets of connected-environment Dapr components, which can disclose credentials or other sensitive configuration to the assignee.; 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.
- Azure Container Apps on Azure Arc-enabled Kubernetes →
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.