Azure Container Registry Overview

Azure Container Registry is the #2 ranked solution in our list of top Container Registry tools. It is most often compared to Amazon ECR: Azure Container Registry vs Amazon ECR

What is Azure Container Registry?

Azure Container Registry allows you to build, store, and manage container images and artifacts in a private registry for all types of container deployments. Use Azure container registries with your existing container development and deployment pipelines. Use Azure Container Registry Tasks to build container images in Azure on-demand, or automate builds triggered by source code updates, updates to a container's base image, or timers.

Azure Container Registry is also known as Microsoft Azure Container Registry.

Azure Container Registry Customers

DNV GL, Alaska Airlines, Finastra

Azure Container Registry Video

Pricing Advice

What users are saying about Azure Container Registry pricing:
  • "Azure is a bit expensive."

Azure Container Registry Reviews

Filter by:
Filter Reviews
Industry
Loading...
Filter Unavailable
Company Size
Loading...
Filter Unavailable
Job Level
Loading...
Filter Unavailable
Rating
Loading...
Filter Unavailable
Considered
Loading...
Filter Unavailable
Order by:
Loading...
  • Date
  • Highest Rating
  • Lowest Rating
  • Review Length
Search:
Showingreviews based on the current filters. Reset all filters
Hardeep-Singh
DevOps Consultant at GP Coders
Consultant
Leaderboard
Dec 13, 2020
Easy to use, private, secure, and it performs well

What is our primary use case?

I am a DevOps consultant. I provide the architecture, assessments, and optimization of the services that we use to build a better infrastructure, and other services. We are basically using Azure Container Registry for a project that we have in the healthcare domain. There, we use the container registry and as well as Azure DevOps, apart from the Azure Cloud and the built release pipeline, along with this container registry and the self-hosted server. I would say that this allows us to build, store, and manage the container images and the artifact in the private registry that Azure provides… more »

Pros and Cons

  • "One of the benefits of this solution is that it's private and secure."
  • "The deployment is an area that needs improvement, as it can take some time to deploy."

What other advice do I have?

Overall, this solution is very beneficial. If my infrastructure or our services are within the Azure Cloud, and if I'm using the ECR, it's very helpful to maintain the images that we use for the web services or the microservices for the ATS and the dockers. We don't have to maintain those images for other third parties or other repositories. It's very good and for those who don't use it, you must look into it, and just go for it. I would rate this solution a ten out of ten.
reviewer1394685
New Technologies Adoption Director at a tech services company with 11-50 employees
Real User
Leaderboard
Nov 12, 2020
It has great support and valuable features like portability and elasticity

What is our primary use case?

We use it for some specific machine learning models to take advantage of the elasticity of the containers. This is the main use of containers. Around 80% of our implementation is on the public cloud, but in some cases, we use a hybrid model. Our clients are large businesses.

What is most valuable?

The portability and elasticity features are the most valuable. 

What needs improvement?

It should be easier to use. It can have more graphical interfaces to manage containers. At present, the handling or management of the containers is very basic.

For how long have I used the solution?

I have been using Azure Container Registry for two years.

How are customer service and technical support?

We get great support from Microsoft. I would rate them a…
reviewer1441002
Sr. SDET at a tech services company with 201-500 employees
Real User
Leaderboard
Nov 12, 2020
Has reasonable pricing

What is our primary use case?

I work for a logistics business, so we have a few applications and we apply them to Azure. We pull the codes, stop at the Docker images, and then we push it to the Container for tracking.

What needs improvement?

Implementation needs improvement. We have a lot of open, online sources. Doing a deployment is easy for us. The only issue is when we have VPN connections and we try to pull the images from Container images to the local Dockers, it slows down. The images are slow when we have a VPN setup. 

For how long have I used the solution?

I have been using Azure Container Registry for three years. 

What do I think about the stability of the solution?

It's hard for us to do a customer partition piece update. The indexing always crashes. 

What's my