Azure Containers built-in role

Azure Container Instances Contributor Role

Creates, updates, deletes, starts, stops, and restarts Azure Container Instances container groups. The containerGroups wildcard also permits interactive exec into a running container, attachment to its output stream, reading build and application logs, refreshing delegated resource identity, and writing container-group diagnostic settings. Access to external registries, storage, networks, and managed identities 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: 5d977122-f97e-4b4d-a52f-6b43003ddb4d

Control-plane actions (5)

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 dedicated resource group containing the approved container groups. A subscription or management-group assignment is inherited by every ACI resource below it and permits container execution across those scopes.

Common use cases (1)

Prerequisites (2)

Best practices (2)

Security considerations (3)

Assignment guidance

Assign Azure Container Instances Contributor on a dedicated ACI resource group only to an identity trusted with deployment, lifecycle, exec, attach, logs, and diagnostic settings. Authorize external registries, storage, networks, and managed identities separately and avoid subscription-wide human assignment.

Editorial sources (9)

Official Microsoft Learn documentation →