ACR Tasks requests for the registry <REGISTRY NAME> and <SUBSCRIPTION ID> are not permitted. Why not?

Question

ACR Tasks requests for the registry <REGISTRY NAME> and <SUBSCRIPTION ID> are not permitted. Why not?

668 0

I'm learning my way in Azure. I'm following a tutorial to upload a Dockerfile into my container registry in Azure from VSCode.

As far as I can tell, I have met all of the requirements:

Active Azure subscription (Free Trial fwiw)
Container Registry has been created
I have added Admin User and Contributor to my user.
VSCode is logged in to Azure, it can see my Subscription and Container Registry.

But when I try to Build Image in Azure, I just get the old ACR Tasks for the registry <REGISTRY NAME> and <SUBSCRIPTION ID> are not permitted.
The Registry name is correct, and so is the Subscription ID.

Other similar posts in here have not been too helpful, apart from assisting in confirming the above.

What am I missing?

It's probably something small, but maybe that's why I can't see it...

Aslam Mohammad 405 Reputation points Microsoft External Staff Moderator

2025-06-26T08:11:47.28+00:00

Hi 668

Just checking in to see if you had a chance to review the response provided to your question.

Feel free to reach out if you have any further queries.

If you found the information helpful, please click "Upvote" on the post to let us know and consider accepting the answer as the token of appreciation.

Thank You.
668 0 Reputation points

2025-06-27T07:10:47.1933333+00:00

Hi Aslam

Thanks for the input, it it seem to do the trick after a bit of scratching - I'm very new to Docker so I don't really know what I'm doing (YET!).
The real problem turned out to be tagging the image correctly.
After I got that done the push command worked perfectly.
Now to see if the webapp will work...

Thanks!

668

1 answer

Your answer

Aslam Mohammad 405 Reputation points Microsoft External Staff Moderator

2025-06-26T08:11:47.28+00:00

Hi 668

Just checking in to see if you had a chance to review the response provided to your question.

Feel free to reach out if you have any further queries.

If you found the information helpful, please click "Upvote" on the post to let us know and consider accepting the answer as the token of appreciation.

Thank You.
668 0 Reputation points

2025-06-27T07:10:47.1933333+00:00

Hi Aslam

Thanks for the input, it it seem to do the trick after a bit of scratching - I'm very new to Docker so I don't really know what I'm doing (YET!).
The real problem turned out to be tagging the image correctly.
After I got that done the push command worked perfectly.
Now to see if the webapp will work...

Thanks!

668

Answer 1

Hi 668

I understood that when trying to use ACR Tasks from a subscription where it is not enabled or allowed, especially with a Free Trial subscription.

Use Local Build Instead of ACR Tasks

Login to your ACR

az acr login --name <yourRegistryName>

Build the Docker image locally

docker build -t <yourRegistryName>.azurecr.io/your-image-name:tag .

Push it to ACR

docker push <yourRegistryName>.azurecr.io/your-image-name:tag

Use Azure CLI Instead of VSCode Extension and Upgrade to a Pay-As-You-Go Subscription

Ensure Permissions Are Correct, and user should be assigned at least AcrPush or Contributor role on the registry.

If you have any further queries, let me know. If the information is helpful, please click on Upvote.

Thank you.

Share via

ACR Tasks requests for the registry <REGISTRY NAME> and <SUBSCRIPTION ID> are not permitted. Why not?

1 answer

Your answer