Unauthorized error while pushing docker image to ACR

Hungry Panda 45 Reputation points
2025-07-21T12:09:22.47+00:00

Hi,

I've created a docker image in my Azure Virtual machine and trying to push the image to ACR. I was able to login successfully but the docker push is giving me authorization error.

I have tried with all the combo of the below fields while creating the ACR, :

  • Domain name label scope: Tenant Reuse/ Unsecure
  • Pricing Plan: Basic/ Standard
  • Role assignment permissions mode: RBAC + ABAC / RBAC

Once done, I've checked the "Admin user" under the Access keys and was able to login successfully using username and password. I've checked the Role Assignments from IAM and it's "Owner".

But getting this error while doing docker push:

unauthorized: {"errors":[{"code":"UNAUTHORIZED","message":"authentication required, visit https://aka.ms/acr/authorization for more information. CorrelationId: 14aa440f-e0f4-4473-b69e-62159e0d622a"}]}

I tried to check the logs (under Monitorin) using the CorrelationId, but keep getting error while trying to execute any query (following the demo video).What am I doing wrong?

Thanks and Regards

Azure Container Registry
Azure Container Registry
An Azure service that provides a registry of Docker and Open Container Initiative images.
0 comments No comments
{count} votes

Accepted answer
  1. Muskan Tomar 470 Reputation points Microsoft Employee
    2025-07-21T13:41:35.0933333+00:00

    Hey!

    If you're seeing an unauthorized error during docker push to ACR, even after a successful docker login, check the following:

    1. Correct image tag – Make sure your image is tagged with the ACR login server name: docker tag myimage <yourregistry>.azurecr.io/myimage
    2. Admin user enabled – Confirm that the Admin user toggle is ON under ACR → Access keys.

    Proper role assignment – Ensure your identity (user/VM) has AcrPush or Owner role on the ACR resource, not just at subscription/resource group level.

    Auth token issues – Try docker logout <yourregistry>.azurecr.io and login again to clear stale tokens.

    Also, worth checking/reconfirming ---- If using Managed Identity (e.g., from a VM), use az acr login --name <yourregistry> instead of docker login.

    Let me know if this helps!

    1 person found this answer helpful.

0 additional answers

Sort by: Most helpful

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.