Microsoft Azure ResourceManagementClient

Name: ResourceManagementClient API
Brand: ResourceManagementClient
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCloud InfrastructureComputeoauth278 EndpointsREST

For Agents

Submit and manage Azure Resource Manager template deployments, resource groups, resources, and tags across subscriptions and management groups.

Install Jentic One Beta

Connect the ResourceManagementClient to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the ResourceManagementClient, 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 ResourceManagementClient API.

Create or update an ARM template deployment at subscription, resource group, or management group scope

Validate an ARM template before submitting it to detect schema or quota issues

List, move, and delete resources across resource groups within a subscription

GET STARTED

Start building with ResourceManagementClient API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI specification for ResourceManagementClient, keeping it validated and agent-ready. The Azure Resource Management API is the control plane for ARM deployments, resource groups, individual resources, and tags across subscriptions and management groups. Agents can submit and validate ARM template deployments at any scope, list and update resources by id, manage resource groups and their tags, and inspect deployment operations to debug failures. It is the foundational API for everything Azure builds on top of subscriptions.

Use Cases

Patterns agents use ResourceManagementClient API for, with concrete tasks.

★ Infrastructure-as-Code Deployment

Platform teams use ResourceManagementClient to submit ARM template deployments from CI/CD pipelines or agent workflows. The API accepts a template plus parameters and returns a deployment resource the caller can poll until completion. Validation can be run separately first to catch schema or quota issues before consuming a deployment slot. Deployments scope to subscription, resource group, or management group depending on what the template provisions.

PUT /subscriptions/{subscriptionId}/resourcegroups/{rg}/providers/Microsoft.Resources/deployments/{name} with a template body and poll the deployment until provisioningState is Succeeded

Failure Forensics on Stuck Deployments

When an ARM deployment fails, an operator needs to see which specific resource caused the failure. The deployment operations endpoint returns one record per resource the deployment attempted, including provisioning state, error code, and the target resource id. Agents can pull this data to summarise the failure or open a remediation ticket without re-running the deployment.

GET deployment operations for deployment infra-prod-42 in resource group rg-prod and return the operation entries where provisioningState equals Failed

Resource Group Lifecycle and Tagging

FinOps and governance teams use the resource group endpoints to enforce tagging standards, export templates, and clean up empty resource groups. The API supports creating a resource group, patching its tags in place, listing the resources it contains, and deleting it. Tag updates are applied without recreating the group so existing automation is unaffected.

PATCH /subscriptions/{subscriptionId}/resourcegroups/{rg} with tags {costCenter: "42", env: "prod"} and verify the response echoes the new tag set

Cross-Resource-Group Resource Moves

When teams reorganise Azure subscriptions, they need to move resources from one resource group or subscription to another. The moveResources operation accepts a list of resource ids and a target resource group, performs the move asynchronously, and returns a long-running operation handle. The API also supports validating a move first to confirm all resource types support relocation.

POST moveResources on resource group rg-old with target rg-new and a list of three storage account ids, then poll the long-running operation until it completes

Agent-Driven ARM Operations via Jentic

Through Jentic, an infrastructure agent can search for deploy arm template, load the deployment input schema, populate template and parameters, and execute the call with a managed Azure OAuth token. The same flow extends to validation, cancellation, and operation inspection so a single agent can own a full deployment lifecycle without writing ARM SDK code.

Search Jentic for deploy arm template to resource group, load the deployment PUT schema, execute it with subscriptionId, resourceGroupName, and a template body, then poll the deployment to completion

Key Endpoints

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

METHOD

PATH

DESCRIPTION

PUT

/subscriptions/{subscriptionId}/resourcegroups/{resourceGroupName}/providers/Microsoft.Resources/deployments/{deploymentName}

Create or update a resource-group-scoped deployment

POST

/subscriptions/{subscriptionId}/resourcegroups/{resourceGroupName}/providers/Microsoft.Resources/deployments/{deploymentName}/validate

Validate an ARM template before deployment

POST

/subscriptions/{subscriptionId}/resourcegroups/{resourceGroupName}/providers/Microsoft.Resources/deployments/{deploymentName}/cancel

Cancel a running deployment

GET

/subscriptions/{subscriptionId}/resourcegroups/{resourceGroupName}/providers/Microsoft.Resources/deployments/{deploymentName}/operations

List operations for a deployment

PUT

/subscriptions/{subscriptionId}/resourcegroups/{resourceGroupName}

Create or update a resource group

POST

/subscriptions/{subscriptionId}/resourcegroups/{sourceResourceGroupName}/moveResources

Move resources to another resource group

GET

/providers

List all resource providers

PUT

/subscriptions/{subscriptionId}/resourcegroups/{resourceGroupName}/providers/Microsoft.Resources/deployments/{deploymentName}

Create or update a resource-group-scoped deployment

POST

/subscriptions/{subscriptionId}/resourcegroups/{resourceGroupName}/providers/Microsoft.Resources/deployments/{deploymentName}/validate

Validate an ARM template before deployment

POST

/subscriptions/{subscriptionId}/resourcegroups/{resourceGroupName}/providers/Microsoft.Resources/deployments/{deploymentName}/cancel

Cancel a running deployment

GET

/subscriptions/{subscriptionId}/resourcegroups/{resourceGroupName}/providers/Microsoft.Resources/deployments/{deploymentName}/operations

List operations for a deployment

PUT

Why Jentic?

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

Credential isolation

Azure service principal credentials are stored encrypted in the Jentic vault. Agents receive scoped OAuth tokens for the management.azure.com audience only — the underlying client secret never enters the agent context.

Intent-based discovery

Agents search by intent such as deploy arm template or move azure resources, and Jentic returns the matching ResourceManagementClient operation with its full input schema, including the right scope-specific path for subscription, resource group, or management group.

Time to first call

Direct integration: 3-5 days to handle MSAL, ARM long-running operation polling, and per-scope path branching. Through Jentic: under an hour to search, load, and execute a deployment.

FAQs

Specific to using ResourceManagementClient API through Jentic.

Why is there no official OpenAPI spec for ResourceManagementClient?

Microsoft Azure does not publish a single unified OpenAPI specification for the Resource Manager control plane. Jentic generates and maintains this spec so that AI agents and developers can call ResourceManagementClient via structured tooling. It is validated against the live Azure Resource Manager API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does ResourceManagementClient use?

It uses Azure Active Directory OAuth 2.0 via the azure_auth flow defined in the spec. Acquire a bearer token for https://management.azure.com/.default and pass it as Authorization: Bearer. Jentic stores the underlying service principal in its vault and the agent only sees a scoped token.

Can I validate an ARM template with this API before deploying?

Yes. POST to /subscriptions/{subscriptionId}/resourcegroups/{rg}/providers/Microsoft.Resources/deployments/{name}/validate with the same body you would send to PUT. The service returns the same validation errors it would have produced during deployment without consuming any quota.

How do I cancel a stuck ARM deployment?

POST to /subscriptions/{subscriptionId}/resourcegroups/{rg}/providers/Microsoft.Resources/deployments/{name}/cancel. The deployment moves into a Cancelling state. Resources already provisioned remain in place — cancellation does not roll back completed steps.

What are the rate limits for ResourceManagementClient?

Azure Resource Manager applies subscription-level throttling: roughly 12,000 reads and 1,200 writes per hour, with deployment-specific quotas of 800 deployments per resource group history. Throttled responses come back as HTTP 429 with a Retry-After header.

How do I move a resource between resource groups via Jentic?

Search Jentic for move azure resources between resource groups, call client.load on the moveResources POST operation, and execute it with the source resource group, target resource group id, and an array of resource ids. Jentic injects the OAuth token and returns a long-running operation handle to poll.

Microsoft Azure ResourceManagementClient

Connect the ResourceManagementClient to your agent

Capabilities

Start building with ResourceManagementClient API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs