Azure Container Registry service tiers
Azure Container Registry is available in multiple service tiers (also known as SKUs). These tiers provide predictable pricing and several options for aligning to the capacity and usage patterns of your private Docker registry in Azure.
|Basic||A cost-optimized entry point for developers learning about Azure Container Registry. Basic registries have the same programmatic capabilities as Standard and Premium (such as Azure Active Directory authentication integration, image deletion, and webhooks). However, the included storage and image throughput are most appropriate for lower usage scenarios.|
|Standard||Standard registries offer the same capabilities as Basic, with increased included storage and image throughput. Standard registries should satisfy the needs of most production scenarios.|
|Premium||Premium registries provide the highest amount of included storage and concurrent operations, enabling high-volume scenarios. In addition to higher image throughput, Premium adds features such as geo-replication for managing a single registry across multiple regions, content trust for image tag signing, private link with private endpoints to restrict access to the registry.|
The Basic, Standard, and Premium tiers all provide the same programmatic capabilities. They also all benefit from image storage managed entirely by Azure. Choosing a higher-level tier provides more performance and scale. With multiple service tiers, you can get started with Basic, then convert to Standard and Premium as your registry usage increases.
Service tier features and limits
The following table details the features and registry limits of the Basic, Standard, and Premium service tiers.
|Included storage1 (GiB)||10||100||500|
|Storage limit (TiB)||20||20||20|
|Maximum image layer size (GiB)||200||200||200|
|ReadOps per minute2, 3||1,000||3,000||10,000|
|WriteOps per minute2, 4||100||500||2,000|
|Download bandwidth2 (Mbps)||30||60||100|
|Upload bandwidth 2 (Mbps)||10||20||50|
|Private link with private endpoints||N/A||N/A||Supported|
|• Private endpoints||N/A||N/A||10|
|Service endpoint VNet access||N/A||N/A||Preview|
|• Scope maps||N/A||N/A||20,000|
|• Repositories per scope map||N/A||N/A||500|
1 Storage included in the daily rate for each tier. Additional storage may be used, up to the registry storage limit, at an additional daily rate per GiB. For rate information, see Azure Container Registry pricing. If you need storage beyond the registry storage limit, please contact Azure Support.
2ReadOps, WriteOps, and Bandwidth are minimum estimates. Azure Container Registry strives to improve performance as usage requires.
3A docker pull translates to multiple read operations based on the number of layers in the image, plus the manifest retrieval.
4A docker push translates to multiple write operations, based on the number of layers that must be pushed. A
docker push includes ReadOps to retrieve a manifest for an existing image.
You can change a registry's service tier with the Azure CLI or in the Azure portal. You can move freely between tiers as long as the tier you're switching to has the required maximum storage capacity.
There is no registry downtime or impact on registry operations when you move between service tiers.
To move between service tiers in the Azure CLI, use the az acr update command. For example, to switch to Premium:
az acr update --name myregistry --sku Premium
In the container registry Overview in the Azure portal, select Update, then select a new SKU from the SKU drop-down.
For pricing information on each of the Azure Container Registry service tiers, see Container Registry pricing.
For details about pricing for data transfers, see Bandwidth Pricing Details.
Azure Container Registry Roadmap
Visit the ACR Roadmap on GitHub to find information about upcoming features in the service.
Azure Container Registry UserVoice
Submit and vote on new feature suggestions in ACR UserVoice.