Azure · Cloud service
Azure Container Registry with OrchestrAI
Catalog exported 2026-09-02
Manage Azure Container Registry from chat: create registries, list repositories, and log Docker in.
OrchestrAI exposes 6 ACR operations: 3 are low-risk (read-only or low-impact), and 3 create or modify resources and run only after you confirm the plan. 1 of them also carries a step-level approval gate.
What teams use it for
Teams use OrchestrAI to create an ACR instance alongside a new AKS cluster or App Service app, then log their Docker client in so the first push works. Listing registries and the repositories inside them helps answer which images a subscription actually holds when nobody remembers. Image deletion, retention policies, and ACR Tasks builds are not available, so cleaning up untagged manifests still happens through the az CLI.
Every ACR operation, with its risk level
| Operation | What it does | Risk | Step-level approval |
|---|---|---|---|
List ACR Repositories |
List repositories in an Azure Container Registry | Low risk | No |
List Azure Container Registries |
List Azure Container Registries | Low risk | No |
Login to ACR |
Login to an Azure Container Registry | Low risk | No |
Create Azure Container Registry |
Create an Azure Container Registry | Creates resources | No |
Create Azure Container Registry |
Create an Azure Container Registry | Creates resources | No |
Delete Azure Container Registry |
Delete an Azure Container Registry | Modifies existing | Yes |
Risk tiers come from the catalog: low is read-only or low-impact, medium creates resources and is reversible, high modifies existing resources, destructive may lose data. Every plan that creates or changes resources is shown with its cost estimate and waits for your confirmation. Operations marked with a step-level approval pause again on their own step. Destructive operations require a typed risk phrase.
Prompts that work
- Create a Basic tier container registry called acmeprodacr in resource group rg-prod in eastus
- Log me into acmeprodacr so I can push images
- List all container registries in the subscription and the repositories in acmeprodacr
Before anything runs
Every mutation shows its plan, cost estimate, and blast radius, then waits for your confirmation. Destructive operations require a typed risk phrase. Credentials are minted per run through OIDC federation and discarded afterward; nothing you create here is invisible later, because every resource lands in the desired-state ledger where drift is detected and can be converged. Details on the security page.
Frequently asked questions
- Will OrchestrAI delete an Azure Container Registry without asking?
- It will not. Registry deletion is rated high risk and pauses for your confirmation, because every image in the registry is removed along with it.
- How does OrchestrAI log in to ACR?
- The login operation is read-only and uses the federated Azure credential OrchestrAI mints for the run, so there is no separate registry credential to upload.
- Which ACR operations need an extra approval step?
- One operation carries a step-level approval gate on top of plan confirmation: Delete Azure Container Registry. None of them is classed destructive.
Other Azure services
Related integrations
Try it on your own account
Connect your cloud read-only and see your resources, drift, and costs before anything runs. $5 minimum to start. Unused credits refunded in your first 14 days.
Unused credits refunded in your first 14 days.