
Azure Container Registry CLI
OfficialFreeManage Azure Container Registry resources with ease.
Free · Opens the source repo
What Azure Container Registry CLI does
The Azure Container Registry CLI skill enables users to manage Azure Container Registry (ACR) resources effectively using the az acr command group from the Azure CLI. This skill is particularly useful for developers and DevOps professionals who need to create, manage, and troubleshoot container registries in Azure. It allows for seamless integration with other Azure services and simplifies the process of handling container images and builds. With built-in commands for creating registries, authenticating, and managing images, users can streamline their workflows and improve efficiency when working with containers.
Users can quickly set up a registry, authenticate Docker or Podman, and even build images in the cloud without needing a local Docker installation. The CLI commands cover a wide range of functionalities, including creating and deleting registries, listing repositories, checking health, and managing network rules. The skill also emphasizes best practices, such as using ACR Tasks for cloud builds and avoiding the use of admin credentials in production environments, thereby enhancing security and operational efficiency.
The skill is designed for those who frequently work with Azure Container Registry, whether for deploying applications, managing CI/CD pipelines, or maintaining container images. It is an essential tool for teams that rely on Azure for their containerization needs, providing a comprehensive set of commands to manage resources effectively. Users can also access reference files for detailed command syntax and examples, ensuring they have the necessary information at their fingertips to resolve issues or optimize their workflows.
When to use it
Use this skill when you need to manage Azure Container Registry resources, including creating registries, pushing images, and configuring network settings.
When not to use it
This skill may not be suitable if you're not using Azure services or if you require a graphical interface for managing container registries.
What you can build with it
Creating a New Registry
Easily create a new Azure Container Registry with specified SKU using the `az acr create` command.
Building Images in the Cloud
Utilize the `az acr build` command to build container images directly in Azure, streamlining your CI/CD processes.
Managing Repository Tags
List and manage repository tags efficiently with commands like `az acr repository list` and `az acr repository show-tags`.
How to install Azure Container Registry CLI
View source1. Install with the skills CLI
npx skills add github/awesome-copilot/azure-container-registry-cli --agent claude-code2. Or install it manually
Download the skill folder and drop it into ~/.claude/skills/ for all projects, or .claude/skills/ to scope it to one repo. Restart Claude Code so it picks up the new skill.
Anthropic's agentic coding CLI, and the reference implementation of Agent Skills. Drop a skill folder into ~/.claude/skills and Claude Code loads it automatically whenever a task matches the skill's description. Claude Code docs
Inside SKILL.md
Written by githubAzure Container Registry CLI
Manage Azure Container Registry (ACR) resources using the az acr command group of the Azure CLI.
CLI: az acr ships with core Azure CLI — no extension required (the acrtransfer extension is only needed for export/import pipelines).
Prerequisites
# Install Azure CLI
brew install azure-cli # macOS
curl -sL https://aka.ms/InstallAzureCLIDeb | sudo bash # Linux
winget install Microsoft.AzureCLI # Windows
# Sign in and select subscription
az login
az account set --subscription {subscription-id}
Quick Start
# Create a registry (SKU: Basic | Standard | Premium)
az acr create --resource-group {rg} --name {registry} --sku Standard
# Authenticate Docker/Podman against the registry
az acr login --name {registry}
# Build and push in the cloud — no local Docker needed
az acr build --registry {registry} --image app:v1 .
# Copy an image from another registry without pull/push
az acr import --name {registry} --source mcr.microsoft.com/hello-world:latest
# List repositories and tags
az acr repository list --name {registry} --output table
az acr repository show-tags --name {registry} --repository app --orderby time_desc
# Diagnose registry connectivity and configuration
az acr check-health --name {registry} --yes
Key Principles
- Prefer
az acr build/ ACR Tasks over localdocker build+docker push: builds run in Azure, work without a local daemon, and integrate with triggers. - Prefer
az acr importto move images between registries: it is server-side, faster, and requires no local storage. - Never enable the admin user for production — use Microsoft Entra identities (RBAC roles
AcrPull/AcrPush, orContainer Registry Repository Reader/Writeron ABAC-enabled registries), repository-scoped tokens, or managed identities. - Premium-only features: geo-replication, private endpoints, retention policies, connected registries, agent pools. (Repository-scoped tokens work in all tiers; zone redundancy is automatic in all tiers in supported regions.)
CLI Structure
az acr
├── create / delete / list / show / update # Registry lifecycle
├── login # Docker credential helper (or --expose-token)
├── check-health / check-name / show-usage # Diagnostics & quota
├── build # Cloud image build (quick task)
├── run # Run a command / multi-step task once
├── task # ACR Tasks (triggers, timers, logs, runs)
├── agentpool # Dedicated task agent pools (Premium)
├── import # Server-side image copy into the registry
├── repository # List/show/delete/untag repos & tags, lock images
├── manifest # Manifest metadata, delete, OCI referrers
├── credential # Admin user credentials (avoid in production)
├── token / scope-map # Repository-scoped tokens (Premium)
├── replication # Geo-replication (Premium)
├── network-rule # IP network rules
├── private-endpoint-connection # Private Link approvals
├── config # content-trust, retention, soft-delete, ...
├── cache / credential-set # Artifact cache (pull-through cache) rules
├── webhook # Push/delete event webhooks
├── connected-registry # On-premises / IoT connected registries
└── export-pipeline / import-pipeline / pipeline-run # acrtransfer extension
Reference Files
Read the relevant reference file based on the user's task. Each file contains complete command syntax and examples for its domain.
| File | When to read | Covers |
|---|---|---|
references/auth-and-security.md | Login failures, permissions, CI/CD or AKS pull access | az acr login (incl. --expose-token), Entra RBAC roles, service principals, managed identities, --attach-acr for AKS, repository-scoped tokens & scope maps, admin user, content trust |
references/build-and-tasks.md | Building images in Azure, automation, CI triggers | az acr build, az acr run, multi-step task YAML, az acr task (git/base-image/timer triggers, logs, runs), agent pools |
references/images-and-artifacts.md | Managing repos, tags, cleanup, storage costs | az acr import, repository & manifest commands, untag vs delete, purge (acr purge), image locking, retention policy, soft delete, artifact cache, show-usage |
references/networking-and-geo.md | Multi-region, private access, edge scenarios | Geo-replication, zone redundancy, private endpoints, network rules, dedicated data endpoints, connected registries, registry transfer pipelines |
Frequently asked questions about Azure Container Registry CLI
Similar skills
Turborepo
Optimized build system for JavaScript/TypeScript monorepos.
Azure Pipelines Validation
Streamline your Azure DevOps pipeline changes locally.
Azure Developer CLI
Streamline your Azure project workflows with best practices.
Aspire
Build and orchestrate polyglot distributed applications seamlessly.
Vercel CLI
Manage and deploy Vercel projects from the command line.
Agent Customization
Streamline your VS Code agent customization process.
