Azure Container Registry
Does ZopNight manage Azure Container Registry?
Azure Container Registry bills a fixed per-day charge at one of 3 tiers (Basic, Standard, or Premium) plus additional storage beyond the tier's included allowance. ZopNight discovers each registry with tier and usage detail via Resource Graph, attributes spend through Cost Management, and surfaces tier-downgrade and cleanup opportunities.
Rules that fire on Azure Container Registry
At a glance
| Field | Value |
|---|---|
| Scheduling notes | discovery and cost visibility only. |
Azure Container Registry stores and distributes container images, billed per day by tier plus extra storage. Premium registries retained for finished projects and unbounded image growth are its usual leaks.
A daily tier fee that ignores activity
Unlike most storage, a container registry’s base charge is a flat per-day fee set by its tier, one of Basic, Standard, or Premium, that accrues whether the registry served ten thousand pulls or none. Each tier includes a storage allowance; images beyond it bill per GB per day on top. Premium adds capabilities like geo-replication, and a geo-replicated registry pays the Premium daily fee once per replica region. The consequence is a cost floor that never declines on its own: an abandoned Premium registry with a decade of image layers bills every single day at the same rate as one under heavy production load.
Tier and usage detail in ZopNight’s inventory
ZopNight discovers each registry through Azure Resource Graph with tier and usage detail, and Cost Management billing attributes registry spend. Tier-downgrade and cleanup opportunities surface in review. There is no stop verb for a registry and nothing to schedule, so the levers are stepping Premium down to Standard where its features go unused, pruning image storage back under the included allowance, and deleting registries whose projects have shipped their last build.
How registries outgrow and outlive their need
Three patterns dominate. CI pipelines that push a tagged image on every commit and never delete one, growing storage past the allowance for years. A Premium tier chosen for geo-replication during an evaluation that stayed after the evaluation ended. And per-project registries that survive their projects because image deletion feels riskier than it is.
Checking a registry’s tier and consumption
Azure portal → Container registries → select a registry: the Overview blade shows the SKU, and Metrics exposes Storage used. Repositories lists every image and tag. Sorted by last push time, the prune list writes itself.