ACR Permissions Issue

Hello Adam,

Thank you for reaching out regarding the issue with accessing your Azure Container Registry (ACR).

Based on your description, it appears that you are unable to view or access container images in your registry, which is preventing you from configuring your Container App. This behavior is typically related to authentication, RBAC permissions, or networking restrictions.

To help resolve the issue, please review the following checks:

1. Verify RBAC Permissions on ACR:

Ensure that the identity you are using (user account, service principal, or managed identity) has the appropriate role assigned on the ACR resource. At minimum, the AcrPull role is required to view and pull images.

Additionally, if your registry is configured with “RBAC Registry + ABAC Repository Permissions”, make sure the identity also has repository-level permissions.

Reference: Azure Container Registry Entra permissions and role assignments overview

2. Validate Authentication (CLI / Docker):

Please verify that you are authenticated to the correct tenant and subscription:

az login
az account set --subscription <subscription-id> 
az acr login --name <acr-name>

You can also validate access by listing repositories:

az acr repository list --name <acr-name> --output table 
az acr repository show-tags --name <acr-name> --repository <repository-name>

Reference: Authenticate with Azure Container Registry

Push your first image to your Azure container registry by using the Docker CLI

3. Check Admin User Visibility (Azure Portal):

If you are accessing ACR via the Azure Portal and no repositories are visible, this may be because the Admin user is disabled. Please verify:

• Go to your ACR → Settings → Access keys
• Check whether Admin user is toggled Enabled

Note: Enabling the Admin user is acceptable for dev/test environments. For production workloads, RBAC role assignments are recommended over admin credentials.

Reference: https://learn.microsoft.com/en-us/azure/container-registry/container-registry-authentication?tabs=azure-cli#admin-account

4. Container App Managed Identity (if applicable):

If you are configuring an Azure Container App, ensure that its managed identity is enabled and assigned the AcrPull role on the ACR.

Reference: Azure Container Apps image pull with managed identity

5. Networking / Firewall Restrictions:

If your ACR is configured with private endpoints, firewall rules, or public access disabled, ensure that your client environment has proper network access.

You may also run a health check:

az acr check-health --name <acr-name> --ignore-errors --yes

Reference: Connect privately to an Azure container registry by using Azure Private Link

Check the health of an Azure container registry

Additional documentations for reference:

Troubleshoot Azure Container Registry authentication issues

"Authentication required" error when trying to access Azure Container Registry

To assist further, could you please provide the following details:

• How are you accessing ACR (Azure Portal / CLI / Container App deployment)?
• What exact error message are you encountering?
• Which identity are you using (user / service principal / managed identity)?
• At what scope is the role assigned (subscription / resource group / ACR)?
• Is your ACR configured with public access or private endpoints?

Hope this helps! Please let me know if you have any queries. Also, could you please check the private message.