Microsoft Azure ContainerRegistryManagementClient

Name: ContainerRegistryManagementClient API
Brand: ContainerRegistryManagementClient
Availability: InStock

★ Only Publicly Available OpenAPI DocumentDeveloper ToolsPackage Registryoauth218 Endpoints

Install Jentic One Beta

Connect the ContainerRegistryManagementClient to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the ContainerRegistryManagementClient, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with ContainerRegistryManagementClient API.

Schedule a build, run, or quick-task run inside ACR with a source location and Dockerfile path

Cancel an in-progress run by run ID when a build needs to be aborted

Request a SAS URL to stream the log blob of a completed or running build

GET STARTED

Start building with ContainerRegistryManagementClient API

Explore with Jentic

View OpenAPI Document

For Agents

Schedule and manage Azure Container Registry Tasks runs - build, run, and cancel in-registry container builds and stream their logs.

Use for: I need to trigger a docker build of my repo inside Azure Container Registry, Cancel a stuck ACR run with id 'cb1' on registry agent-acr, Get a SAS URL for the log of run 'cb1', Schedule a quick-run task for image agent-app:latest

Not supported: Does not push or pull container image blobs, manage registry-level repositories, or create the registry itself - use for scheduling and managing ACR Tasks runs and task definitions only.

Use Cases

Patterns agents use ContainerRegistryManagementClient API for, with concrete tasks.

★ Trigger an in-registry container build

Teams that want to build container images close to where they will be pulled use ACR Tasks. The Container Registry Management Client schedules a run with a docker build step, source location, and platform target, returning a run ID that callers poll to completion. This avoids shipping an external CI runner and keeps the image inside the same network boundary.

POST /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ContainerRegistry/registries/{registryName}/scheduleRun with a docker build request for image 'agent-app:1.0' and return the run ID.

Stream build logs

When a build fails the operator wants the log without scraping the portal. Calling listLogSasUrl on the run returns a short-lived SAS URL pointing at the log blob in ACR-managed storage; the caller downloads the blob and pipes it to a chat channel or stores it alongside the failure ticket.

POST listLogSasUrl on run id 'cb1' for registry 'agent-acr', download the blob from the returned SAS URL, and emit the last 200 lines.

Cancel a runaway build

ACR runs occasionally hang on a layer pull or external download. The cancel endpoint terminates a specific run by ID so its allocated build agent is released and the queue moves forward. This is the safe option versus deleting the entire task.

POST cancel on run id 'cb1' for registry 'agent-acr' and confirm the run status transitions to Canceled.

Push a local source tarball before a run

If the source for a build is a local working tree rather than a git ref, ACR exposes a buildSourceUploadUrl endpoint that returns a SAS-signed upload URL plus a relative path. The caller uploads the tarball, then references the same relative path in a scheduleRun request to build it.

POST listBuildSourceUploadUrl on registry 'agent-acr', upload source.tar.gz to the returned URL, then scheduleRun with the relative path.

Agent-driven CI pipeline through Jentic

An AI agent integrated through Jentic can take a git ref, trigger an ACR build, monitor the run, fetch the log on failure, and push a digest of the result to the team chat. Jentic's intent search exposes the schedule, get, cancel, and log operations and the AAD token never leaves the vault.

Take a git URL, scheduleRun an ACR docker build, poll status, and on failure fetch the log SAS URL and post the last 200 lines to the team channel.

Key Endpoints

18 endpoints — jentic publishes the only available openapi specification for containerregistrymanagementclient, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ContainerRegistry/registries/{registryName}/scheduleRun

Schedule a quick-run on a registry

GET

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ContainerRegistry/registries/{registryName}/runs

List runs for a registry

GET

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ContainerRegistry/registries/{registryName}/runs/{runId}

Get a single run by ID

POST

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ContainerRegistry/registries/{registryName}/runs/{runId}/cancel

Cancel a run by ID

POST

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ContainerRegistry/registries/{registryName}/runs/{runId}/listLogSasUrl

Get a SAS URL for a run's log blob

POST

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ContainerRegistry/registries/{registryName}/listBuildSourceUploadUrl

Get a build source upload URL

POST

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ContainerRegistry/registries/{registryName}/scheduleRun

Schedule a quick-run on a registry

GET

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ContainerRegistry/registries/{registryName}/runs

List runs for a registry

GET

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ContainerRegistry/registries/{registryName}/runs/{runId}

Get a single run by ID

POST

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ContainerRegistry/registries/{registryName}/runs/{runId}/cancel

Cancel a run by ID

POST

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ContainerRegistry/registries/{registryName}/runs/{runId}/listLogSasUrl

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Your Azure AD token for the user_impersonation scope, along with any AcrPush role binding, is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'schedule a Docker build in Azure Container Registry' or 'fetch the log for a failed ACR run', and Jentic returns the matching scheduleRun, runs, or listLogSasUrl operation with its input schema so the agent calls the right endpoint directly.

Time to first call

FAQs

Specific to using ContainerRegistryManagementClient API through Jentic.

Why is there no official OpenAPI spec for ContainerRegistryManagementClient?

Microsoft Azure does not publish a single consolidated OpenAPI specification for the ACR Tasks management surface in the 2019-06-01-preview revision. Jentic generates and maintains this spec so that AI agents and developers can call ContainerRegistryManagementClient via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

What authentication does the ContainerRegistryManagementClient use?

It uses Azure Active Directory OAuth 2.0 with the implicit flow at https://login.microsoftonline.com/common/oauth2/authorize and the user_impersonation scope. The caller needs Contributor or AcrPush on the registry. Through Jentic the AAD token is held in the encrypted vault.

Can I cancel an in-progress ACR build with this API?

Yes. POST /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ContainerRegistry/registries/{registryName}/runs/{runId}/cancel. The run transitions to Canceled and its build agent is released for the next queued run.

What are the rate limits for the ContainerRegistryManagementClient?

ARM applies subscription-level write throttling (typically 1,200 writes per hour per subscription). ACR also enforces concurrent-run quotas per registry tier - Basic supports 1, Standard 2, Premium up to 8 concurrent build runs.

How do I trigger an ACR build through Jentic?

Search Jentic for 'schedule acr build', load the schema for POST /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ContainerRegistry/registries/{registryName}/scheduleRun, and execute it with a docker build request body. Run pip install jentic to get the SDK.

Is the ContainerRegistryManagementClient free?

Calling the management API itself is free. Costs come from the registry tier (Basic/Standard/Premium) and per-second build agent time. Each ACR Tasks run is billed for the build agent's runtime.

Can I limit what my agent is allowed to do with the Microsoft Azure ACR Tasks API?

Yes. Because you run Jentic One yourself and set the rules, you decide which operations the agent may call, so you can grant scheduleRun, list runs, and listLogSasUrl while withholding destructive ones like cancel run or delete task. The subscription, resource group, registry name, and run id are all URL path parameters, so a rule can pin the agent to a single registry and its runs. Your Azure AD credential is held by your own instance and injected at execution time rather than exposed to the agent.

Microsoft Azure ContainerRegistryManagementClient

Connect the ContainerRegistryManagementClient to your agent

Capabilities

Start building with ContainerRegistryManagementClient API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs