The solution could always improve its security measures with regard to access. 

I suppose a more detailed management interface that's not available in Azure, if made available, would be useful.

I'm not an active Azure Container Registry user, but I faced some issues, which Azure rectified after six months of usage. During the deployment, my company had a multi-stage pipeline, so whenever the team deploys via the Docker run command or generates an image, the issue arises. The problem is that whenever a new image is generated, that new Docker image isn't updated in Azure Container Registry, so that's an area for improvement.

As soon as the deployment is over, my team has to go to Azure Container Registry to delete the image and start the pipeline, and only then will the image be updated. The new image isn't reflected in Azure Container Registry after deployment. My team had to take extra steps for the new image to reflect.

Before 2020, Azure Container Registry didn't have the option to scan vulnerabilities, as I've heard from my team lead. After 2020, that feature was introduced in the tool, so as long as that feature is available, then Azure Container Registry is okay. I can't think of any other features to add to it in the next version.

From time to time, I've noticed some hiccups in Azure Container Registry. For example, the solution didn't work thrice, and the only solution Microsoft provided was to update Azure Container Registry. I've noticed that the IP address attached to the machine changed in the end.

The solution doesn't always work perfectly, so from time to time, you cannot pull or push the Docker images to the environment, which is an area for improvement. The only solution to this issue is to establish one more Azure Container Registry and attach the new IP address and DNS name to it.

The accessibility of Azure Container Registry also has room for improvement because the solution is not always accessible 24 x 7. I experienced this three times when the service wasn't responding, so I could not push or pull images, and I had to decommission Azure Container Registry and redeploy it. The only good thing is that I already have the infrastructure as a code, which makes it easier for me to set the solution up and create the environment from scratch. Still, the process will be annoying for people with manual operations around Azure Container Registry, mainly because the issue happens from time to time.

The only functionality I want to add to the service is the auto-scanning of images, which should tell me if there's any issue with the Docker images I need to address. The JFrog Artifactory has this functionality, but it would be an excellent feature to add to Azure Container Registry to scan the Docker images and check for possible vulnerabilities.

I haven't delved deep into the details, and I cannot add anything as of now, but they can improve their scalability.

The solution has become more popular in the last few years but I find that the technical support has not increased their knowledge base, so more knowledgeable support staff can help improve the solution.

The solution could provide more integration.

The solution has no areas that need improvement. 

The security, dashboards, and monitoring system could be improved.

It's not an open source, and we pay per hour to Microsoft Azure.

I don't have many issues with the solution but I would like it if the access keys could be stored in a master key vault. If they could be hashed and the value of that hash stored in the key vault so that it's not visible on the portal, would be a helpful addition. 

It's difficult to find areas of improvement. I have always found it to be better than any CI/CD pipeline.

The deployment is an area that needs improvement, as it can take some time to deploy.

We have found that it is sometimes difficult to pull images from the host application.

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. 

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.