Today, we're excited to announce that Azure Container Registry Premium SKU now supports up to 100 TiB of registry storage—a 2.5x increase from the previous 40 TiB limit, and a 5x increase from the original 20 TiB limit just two years ago. We've also improved geo-replication data sync speed, reducing data sync times for new replicas.
We're also introducing an updated Portal experience for storage capacity visibility—a long-standing customer request. You can now monitor your storage consumption directly from the Monitoring tab in the Azure Portal Overview blade, making it easier to track usage against your registry limits.
Imagine you're managing container infrastructure for a large enterprise. Your teams have embraced containerization, migrating critical workloads from VMs to containers for improved composability and deployment velocity. Meanwhile, your AI and machine learning teams are storing increasingly large model artifacts, agent tooling, and pipeline outputs in your registry. You've watched your storage consumption climb steadily toward the 40 TiB limit, and you're evaluating complex workarounds like splitting workloads across multiple registries.
With today's announcement, that constraint is lifted. Premium SKU registries now support up to 100 TiB, giving you the headroom to consolidate workloads and scale confidently.
Background: Container and AI Adoption Drive Storage Growth
Organizations continue to adopt containers at an accelerating pace. The migration from virtual machines to containerized architectures—driven by the composability, portability, and operational benefits of containers—shows no signs of slowing. At the same time, the AI revolution has introduced new storage demands: large language models, vision models, agent frameworks, and their associated tooling all require substantial registry capacity.
These parallel trends have pushed many enterprises toward the previous 40 TiB limit faster than anticipated.
The Challenge: Storage Constraints at Scale
For organizations operating at scale, the 40 TiB limit created operational challenges:
- Multi-Registry Complexity: Teams were forced to split workloads across multiple registries, complicating access control, networking, and operational visibility.
- Architectural Workarounds: Some organizations implemented custom garbage collection and artifact lifecycle policies specifically to stay under limits, rather than based on actual retention requirements.
- Growth Planning Uncertainty: Rapidly growing AI workloads made capacity planning difficult, with some organizations uncertain whether they could consolidate new model artifacts in their primary registry.
- Geo-Replication Provisioning: Syncing data to new geo-replicas for expanding global footprints took longer than desired, slowing regional expansion.
Introducing 100 TiB Storage Limits
Premium SKU registries now support up to 100 TiB of storage—a 2.5x increase that provides substantial headroom for continued growth. This limit applies to the total storage across all repositories in a single registry.
We've also improved geo-replication data sync speed when expanding your registry's global footprint with new replicas, as detailed in the table below.
What's Changing
| Aspect | Previous | New |
|---|---|---|
| Premium SKU Storage Limit | 40 TiB | 100 TiB |
| Basic/Standard SKU Limits | Unchanged | Unchanged |
No Action Required
The new 100 TiB limit is automatically available for all Premium SKU registries. There's no migration, feature flag, or configuration change required—your registry can now grow beyond 40 TiB without any intervention.
Who Benefits
This storage increase is particularly valuable for:
- Enterprise platform teams managing centralized container registries for large organizations with hundreds of development teams
- AI and ML teams storing large model artifacts, training outputs, and inference containers
- Organizations migrating from VMs who are consolidating legacy workloads into containerized architectures
- Global enterprises using geo-replication across many regions, where storage is replicated to each replica
Some of the world's largest AI and financial services organizations have been operating near the previous limit and will benefit immediately from this increase.
Getting Started
Check Your Current Usage
You can view your registry's current storage consumption and the new 100 TiB limit in the Azure Portal (under the Monitoring tab in the Overview blade) or via CLI:
# View registry storage usage and limits. The registry size limit will be under MaximumStorageCapacity.
az acr show-usage --name myregistry --output tableThe Portal, CLI, and REST API/SDKs all now reflect the increased 100 TiB capacity. You can programmatically query your registry's storage usage via the List Usages REST API, making it easy to integrate capacity monitoring into your existing tooling and dashboards.
Upgrade to Premium SKU
The 100 TiB storage limit is exclusive to Premium SKU. If you're on Basic or Standard and need higher storage capacity, upgrading to Premium unlocks the full 100 TiB limit along with geo-replication, enhanced throughput, private endpoints, and other enterprise features:
# Upgrade to Premium SKU
az acr update --name myregistry --sku PremiumRelated Resources
Microsoft