Manage Azure Container Registry resources including images, cloud builds, ACR Tasks, and networking using the az acr command group.
- GitHub stars
- 41,038
- Files
- 5
- Last commit
- Nov 11, 2026
- License
- MIT
- Allowed tools
- —
What does the azure-container-registry-cli skill do?
azure-container-registry-cli manages Azure Container Registry resources including images, cloud builds, ACR Tasks, and networking using the az acr command group.
Summary generated from the skill's SKILL.md.
About the azure-container-registry-cli skill
Managing Azure Container Registry resources through the Azure CLI is what this skill enables for developers and DevOps engineers. It provides direct access to the az acr command group to handle the entire lifecycle of a registry, from creation and deletion to configuring networking and geo-replication. An agent should load this skill when a user needs to interact with container images, manage cloud builds, or configure security settings within Azure.
Users can perform server-side operations like importing images from other registries or running cloud builds via ACR Tasks, which removes the need for a local Docker daemon. The tool supports various registry tiers, including Premium features such as private endpoints, agent pools, and repository-scoped tokens. It relies on the core Azure CLI and can utilize the acrtransfer extension for specific export and import pipelines. This skill produces actionable commands for managing repositories, tags, manifests, and connectivity diagnostics.
What an agent can do with it
- 1Perform cloud-based image buildsAn agent can build and push container images directly to Azure without requiring a local Docker installation.
- 2Transfer images between registriesDevelopers can move images from one registry to another using server-side copying to save local bandwidth and storage.
- 3Manage repository content and tagsYou can list, show, or delete specific repositories and tags to maintain your container environment.
- 4Diagnose registry health and connectivityAn AI can run diagnostic checks to verify the connectivity and configuration of an Azure Container Registry.
Written from the skill's SKILL.md. Every use case is checked against a quote from it.
How to install the azure-container-registry-cli skill
Each command copies the skill folder into the client's skills directory. Restart the client or start a new session to load it.Install the azure-container-registry-cli skill in Claude Code
~/.claude/skills/azure-container-registry-cli/SKILL.md
$ npx degit github/awesome-copilot/skills/azure-container-registry-cli ~/.claude/skills/azure-container-registry-cliInstall the azure-container-registry-cli skill in Claude Code (project)
.claude/skills/azure-container-registry-cli/SKILL.md
$ npx degit github/awesome-copilot/skills/azure-container-registry-cli .claude/skills/azure-container-registry-cliInstall the azure-container-registry-cli skill in Codex
~/.agents/skills/azure-container-registry-cli/SKILL.md
$ npx degit github/awesome-copilot/skills/azure-container-registry-cli ~/.agents/skills/azure-container-registry-cliInstall the azure-container-registry-cli skill in Gemini CLI
~/.gemini/skills/azure-container-registry-cli/SKILL.md
$ npx degit github/awesome-copilot/skills/azure-container-registry-cli ~/.gemini/skills/azure-container-registry-cliInstall the azure-container-registry-cli skill in Claude.ai
npx degit github/awesome-copilot/skills/azure-container-registry-cli azure-container-registry-cli && zip -r azure-container-registry-cli.zip azure-container-registry-cli # claude.ai → Customize → Skills → + → Create skill → Upload a skill → azure-container-registry-cli.zip
Automated checks
Ran Nov 15, 2026Full report →Passed our automated checks. That is not a security audit: read the scripts before you let an agent run them. How checks work
- Source repository linked and reachablegithub/awesome-copilot/skills/azure-container-registry-cli is public and reachablegithub.com/github/awesome-copilot/tree/HEAD/skills/azure-con ↗Pass
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit 2026-11-11github.com/github/awesome-copilot/commits ↗Pass
- No download-and-run or credential theft in scriptsNo scripts in the skill folderPass
- No hidden instructions in SKILL.mdNo override phrases, safeguard switches, credential requests or hidden charactersgithub.com/github/awesome-copilot/blob/HEAD/skills/azure-con ↗Pass
- Pre-approved tools are scopedNo pre-approved tools; the agent asks before using onegithub.com/github/awesome-copilot/blob/HEAD/skills/azure-con ↗Pass
- SKILL.md follows the Agent Skills formatValid name and description; says when to use it; 91 linesgithub.com/github/awesome-copilot/blob/HEAD/skills/azure-con ↗Pass
SKILL.md
View on 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 |
Files in this skill
5azure-container-registry-cli skill questions
How do I install the azure-container-registry-cli skill in Claude Code?
Run npx degit github/awesome-copilot/skills/azure-container-registry-cli ~/.claude/skills/azure-container-registry-cli. Claude Code loads skills from ~/.claude/skills (all projects) or .claude/skills (one project) and uses a skill when its description matches the task.
Which clients can use the azure-container-registry-cli skill?
Any client that reads the Agent Skills format: Claude Code, Codex, Gemini CLI and claude.ai (upload as a ZIP). Scripts in the skill run only where the client allows code execution.
Do I need an extension to use the az acr command group?
No, az acr is included with the core Azure CLI, though the acrtransfer extension is required for export/import pipelines.
How can I build images without having a local Docker daemon?
You can use the az acr build command to perform cloud image builds directly in Azure.
What is the best way to move images between registries?
Use the az acr import command to perform a server-side copy, which is faster and does not require local storage.