Diagram
A nested hierarchy showing Azure Container Registry access control scopes from broadest to narrowest: Subscription, Resource Group, Registry, and Repository. It illustrates how permissions narrow at each level down to specific token-based repository actions like push, pull, and delete.
Identity Integration and Scopes
When assigning these roles, you must choose the scope to limit where the permissions apply. You can apply access controls at different levels of the Azure resource hierarchy depending on your management needs:
If the built-in roles do not meet your security requirements, you can design custom roles to define precise permission boundaries.
Domain 7 of 9
2 practice questions
Practice this DomainLast updated