Jentic OSThe workplace. An in-house AI platform for every employeeJentic OneSafe access. Agents reach your systems without holding keysJentic AIRThe foundation. Gets your existing platforms ready for AI
Pricing

GET STARTED

API DirectoryBrowse 10,000+ APIs ready for AI agent integrationDocumentationGuides and API reference

TOOLS

API ScoringCheck your AI readiness using our scorecardArazzo UIVisualize Arazzo workflows as interactive documentationArazzo EditorBuild and edit multi-step API workflows visually

COMMUNITY

GitHubOpen source projects and examplesOpen StandardsBuilt on open specs. Never locked in.
All ResourcesEverything in one placeBlogLatest articles and insightsTech Talk NewsletterAPIs, AI agents, architecture and strategyWebinarsLive sessions and on-demand recordingsReports & WhitepapersOriginal research on enterprise AI
About UsOur mission and teamCareersJoin our teamContactGet in touch
Try it now
Jentic OSJentic OneJentic AIR
Pricing
API DirectoryDocumentationAPI ScoringArazzo UIArazzo EditorGitHubOpen Standards
All ResourcesBlogTech Talk NewsletterWebinarsReports & Whitepapers
About UsCareersContact
Try it now
JenticJentic
Products
  • Jentic OS
  • Jentic One
  • Jentic AIR
For Developers
  • API Directory
  • Documentation
  • GitHub
Company
  • About Jentic
  • Careers
  • Contact Us
  • Trust Centre
ISO/IEC 27001:2022 certification badge issued by Prescient SecurityISO/IEC 27001:2022 certification badge issued by Prescient Security

Information Security Management System

Certified to ISO/IEC 27001:2022 by Prescient Security

AICPA SOC for Service Organizations logoAICPA SOC for Service Organizations logo

SOC 2® Type 1 report

Audited by Prescient Assurance

Terms & Conditions•Privacy Policy•
© 2026 Jentic Technology Ltd. All rights reserved.
2 Grattan Court East, Dublin, D02 VX86, Ireland
Switch to light modeSwitch to dark mode
APIs / Cloud Infrastructure / Azure / ComputeManagementConvenienceClient
ComputeManagementConvenienceClient logo

Microsoft Azure ComputeManagementConvenienceClient

Browse all Azure APIs
41
AI ReadinessFoundational (D-)41/100
See full scorecard
Agent-ready OpenAPI document · curated by JenticCloud InfrastructureComputeoauth21 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Submit an Azure Resource Manager deployment that lands compute resources from a template, and read back its provisioning state.

Use for: I need to deploy a VM from an ARM template into resource group prod-rg, Submit an ARM deployment named 'web-tier-deploy' with my parameters, Check the provisioning state of deployment 'web-tier-deploy', Re-run my ARM deployment with new VM size parameters

Not supported: Does not delete deployments, list deployments, manage VMs directly, or read deployment templates back - use for submitting an ARM deployment by name only.

Jentic publishes the only available OpenAPI specification for ComputeManagementConvenienceClient, keeping it validated and agent-ready. This convenience client wraps a single Azure Resource Manager endpoint that creates or updates a Microsoft.Resources deployment, used as the canonical 'deploy this ARM template' call when a workflow only needs to land a VM-shaped deployment without pulling in the full Compute Management Client surface. It accepts an ARM template plus parameters and returns the deployment's provisioning status.

Jentic One on GithubView OpenAPI Document

Install Jentic One Beta

Connect the ComputeManagementConvenienceClient to your agent

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

1

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fazure.com%2Fcompute-management-convenience-client" | sh
2

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fazure.com%2Fcompute-management-convenience-client" | 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 ComputeManagementConvenienceClient API.

Submit an ARM template deployment that lands VMs or other compute resources into a resource group

Read back the provisioning state of a named deployment to drive a wait-for-completion loop

Re-run an existing deployment with updated parameters by reusing its name

Use a single convenience endpoint instead of pulling in the full Compute Management Client surface

Use Cases

Patterns agents use ComputeManagementConvenienceClient API for, with concrete tasks.

★ One-shot ARM deployment for compute resources

When a workflow only needs to land a single ARM template that defines VMs, NICs, and disks, this convenience endpoint is enough - there is no need to pull in the full Compute Management Client. PUT the template and parameters under a deployment name and the resource group becomes the unit of consistency. The provisioning state on the response drives a poll loop or a webhook completion handler.

PUT /subscriptions/{subscriptionId}/resourcegroups/prod-rg/providers/Microsoft.Resources/deployments/web-tier-deploy with the ARM template body and return the provisioningState from the response.

Idempotent infrastructure refresh

Reusing the same deployment name with the same template makes the call idempotent - ARM diffs the desired state against the current state and only changes what differs. This is the pattern teams use to roll forward infrastructure changes from CI without writing a custom diff layer.

Re-PUT /subscriptions/{subscriptionId}/resourcegroups/prod-rg/providers/Microsoft.Resources/deployments/web-tier-deploy with the same name but updated VM size parameter and confirm provisioningState reaches Succeeded.

Programmatic poll-for-completion

ARM deployments are asynchronous. After PUTting the template, callers GET the same deployment URL until provisioningState is Succeeded, Failed, or Canceled. This convenience endpoint handles both create and read so a single client wrapper can drive the full deploy-and-wait pattern.

GET /subscriptions/{subscriptionId}/resourcegroups/prod-rg/providers/Microsoft.Resources/deployments/web-tier-deploy every 30 seconds until provisioningState is no longer 'Running'.

Agent-driven infrastructure deployment via Jentic

An AI agent integrated through Jentic can take a natural-language request such as 'spin up a Linux VM in westeurope', generate or fetch the matching ARM template, and submit it via this endpoint. Jentic's intent search exposes the deployment operation and the AAD token stays scoped via the vault, so the agent doesn't handle raw Azure credentials.

Take an ARM template literal for a Standard_D2s_v3 Linux VM, PUT it under deployment name 'agent-vm-001' in resource group agent-rg, and report back when provisioningState is Succeeded.

Key Endpoints

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

METHOD

PATH

DESCRIPTION

PUT

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

Submit an ARM template deployment to a resource group

PUT

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

Submit an ARM template deployment to a resource group

Jentic AI Readiness Score

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

C

ComputeManagementConvenienceClient

- Foundational (D-)
41/100
60
Foundational Compliance
56
Developer Experience & Jentic Compatibility
20
AI-Readiness & Agent Experience
94
Agent Usability
35
Security
100
AI Discoverability
Powered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
60

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: B-Signals: 4
91%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

0%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

50%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

56

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: CSignals: 4
0%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

25%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

20

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: FSignals: 4
79%

Description Coverage

Coverage of descriptions across API elements.

0%

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

0%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

0%

Summary Coverage

Coverage of summaries across operations/tags/info.

94

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1
94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

35

Security

Trust, risk posture, and security compliance.

Grade: FSignals: 1
35%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

100

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A+Signals: 1
100%

Descriptive Richness

Clarity and depth of descriptions across API elements.

View full reportHow the score is calculatedMore about the dimensions

Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

Score your own APIScoring CLI agent skill
npx @jentic/api-scorecard-cli score <openapi-url>

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring this convenience deployment endpoint by hand means an Azure AD app registration for the OAuth implicit flow against management.azure.com, learning the Microsoft.Resources deployment path shape, and building the ARM template payload yourself. Through Jentic you install once, import ComputeManagementConvenienceClient from the API Directory, store the Azure AD credential once, and your agent calls it.

Permission scoping

The subscription, resource group, and deployment name are all URL path parameters (/subscriptions/{subscriptionId}/resourcegroups/{resourceGroupName}/providers/Microsoft.Resources/deployments/{deploymentName}), so a rule can pin the agent to one resource group. You limit the agent to the operations it needs, so submitting an ARM deployment is included only when you add it.

Credential isolation

Your Azure AD token for the user_impersonation scope 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 'submit an ARM template deployment' or 'deploy a VM from a template', and Jentic returns the PUT deployments operation with its template-shaped input schema so the agent calls the right endpoint without navigating the Microsoft.Resources ARM paths.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Compute Management Client

→

Full Compute Management surface for direct VM and scale set operations

Choose Compute Management Client when the agent needs fine-grained VM, scale set, or disk operations rather than a template-shaped deployment

Alternative

Container Instance Management Client

→

Provisions container groups when a container, not a VM, is the right unit of compute

Choose Container Instance Management when the workload is containerised and serverless container groups beat full VMs

Complementary

Consumption Management Client

→

Reports billing and usage for the resources the deployment provisions

Choose Consumption Management when the agent needs to track or attribute the cost of resources deployed via this endpoint

FAQs

Specific to using ComputeManagementConvenienceClient API through Jentic.

Why is there no official OpenAPI spec for ComputeManagementConvenienceClient?

Microsoft Azure does not publish this convenience client as a separate OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call ComputeManagementConvenienceClient 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 ComputeManagementConvenienceClient 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. Through Jentic the AAD token sits in the encrypted vault and the agent receives a scoped access token instead of the raw bearer credential.

Can I deploy an ARM template with this API?

Yes. Issue PUT /subscriptions/{subscriptionId}/resourcegroups/{resourceGroupName}/providers/Microsoft.Resources/deployments/{deploymentName} with the template, parameters, and mode (Incremental or Complete) in the request body. The response contains the deployment's provisioningState.

What are the rate limits for the ComputeManagementConvenienceClient?

ARM applies subscription-level throttling - typically 12,000 reads and 1,200 writes per hour per subscription. Deployment PUTs count as writes and large templates can trigger 429s under load.

How do I deploy infrastructure through Jentic?

Search Jentic for 'submit arm deployment', load the schema for PUT /subscriptions/{subscriptionId}/resourcegroups/{resourceGroupName}/providers/Microsoft.Resources/deployments/{deploymentName}, and execute it with your template body. Run pip install jentic to get the SDK.

Is the ComputeManagementConvenienceClient free?

Calling the deployment endpoint itself is free. Costs come from the Azure resources the deployment provisions - VMs, disks, NICs, and so on are billed on standard Azure rates.

Can I limit what my agent is allowed to do with the ComputeManagementConvenienceClient API?

Yes. Because you run Jentic One yourself, your own rules decide which operations and credentials your agent can use, so the single PUT deployments operation is available to the agent only when you add it. Since the subscription, resource group, and deployment name are all URL path parameters, a rule can pin the agent to one resource group and hold it to submitting ARM deployments there rather than reaching across your subscription. Your Azure Active Directory token is stored once by your own instance and injected at execution time, never entering the agent's prompt or context.

GET STARTED

Start building with ComputeManagementConvenienceClient API

Explore with Jentic One
View OpenAPI Document