Microsoft Azure Compute Admin Client

Name: Compute Admin Client API
Brand: Compute Admin Client
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCloud InfrastructureComputeoauth21 Endpoints

Install Jentic One Beta

Connect the Compute Admin Client to your agent

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

List the provider operations advertised by Microsoft.Compute.Admin on a stamp

Use the operations response as a capability probe before scripting Azure Stack fabric tasks

Diff supported operations across stamp versions to detect deprecated actions

GET STARTED

Start building with Compute Admin Client API

Explore with Jentic

View OpenAPI Document

For Agents

Discover which Microsoft.Compute.Admin operations the Azure Stack stamp advertises before scripting fabric-side compute automation.

Use for: List the operations supported by Microsoft.Compute.Admin, Check whether the Compute Admin provider is registered on this Azure Stack stamp, Get the capability surface for the Azure Stack compute admin plane, Find deprecated Compute Admin operations between stamp versions

Not supported: Does not provision VMs, manage scale sets, attach disks, or run guest workloads - use for Microsoft.Compute.Admin operation discovery on Azure Stack only.

Use Cases

Patterns agents use Compute Admin Client API for, with concrete tasks.

★ Pre-flight capability probe for stamp automation

Before an operator script attempts to call a specific Microsoft.Compute.Admin action, it should confirm the action is advertised on the target stamp. The Compute Admin Client's operations endpoint returns the registered set, so a runbook can fail fast with a clear message if a stamp is older than expected and the desired action is missing.

GET /providers/Microsoft.Compute.Admin/operations on the stamp and assert that the response contains the operation names the runbook depends on.

Detect drift across Azure Stack stamps

Operators running multiple Azure Stack stamps need to know when the supported Compute Admin surface changes - for example after an update package is applied. Calling this endpoint on each stamp and diffing the results highlights newly available or deprecated operations and feeds the change into a compatibility report.

Call /providers/Microsoft.Compute.Admin/operations on each registered stamp and emit a diff of operation names against a reference baseline.

Provider registration sanity check

If a downstream Azure Stack admin script is failing with 404s, the simplest first check is whether Microsoft.Compute.Admin is even registered on the stamp. A successful call to the operations endpoint confirms registration; a non-success surface lets an agent escalate to the operator with a precise diagnosis.

Call GET /providers/Microsoft.Compute.Admin/operations and report whether the response is 200 with a non-empty operation list.

Agent-driven capability discovery via Jentic

An AI agent integrated through Jentic can use the Compute Admin Client as the first hop in any Azure Stack compute admin workflow - discovering operations, then chaining into Compute Disk Admin or Compute Management for the actual fabric-side action. Intent-based search means the agent does not have to memorise admin-plane paths.

From an agent loop, first call /providers/Microsoft.Compute.Admin/operations to confirm capability, then route to the matching Compute Disk Admin or Compute Management operation.

Key Endpoints

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

METHOD

PATH

DESCRIPTION

GET

/providers/Microsoft.Compute.Admin/operations

List supported Microsoft.Compute.Admin operations

GET

/providers/Microsoft.Compute.Admin/operations

List supported Microsoft.Compute.Admin operations

Why Jentic?

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

Credential isolation

Your Azure AD credential 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 'list Azure Stack compute admin operations', and Jentic returns the Operations_List operation with its input schema so the agent calls the right admin endpoint without browsing the Microsoft.Compute.Admin reference.

Time to first call

FAQs

Specific to using Compute Admin Client API through Jentic.

Why is there no official OpenAPI spec for Compute Admin Client?

Microsoft does not publish a consolidated OpenAPI specification for the Azure Stack Compute Admin provider. Jentic generates and maintains this spec so that AI agents and developers can call Compute Admin Client 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 Compute Admin Client 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 must be an Azure Stack operator. Through Jentic the AAD token is held in the encrypted vault and never enters the agent context.

Can I provision VMs with the Compute Admin Client?

No. This 2015-12-01-preview revision only exposes /providers/Microsoft.Compute.Admin/operations - a capability-discovery endpoint. To provision VMs use the public Compute Management Client (computemanagementclient) against management.azure.com.

What are the rate limits for the Compute Admin Client?

The Azure Stack admin plane inherits Azure Resource Manager subscription-level throttling. The spec does not declare separate headers; expect ARM 429 responses under sustained load.

How do I check Compute Admin operations through Jentic?

Search Jentic for 'list compute admin operations', load the schema for GET /providers/Microsoft.Compute.Admin/operations, and execute it. Run pip install jentic to get the SDK and feed the result into your runbook as a capability gate.

Is the Compute Admin Client free?

Calling the admin operations endpoint itself is free; you only need an Azure Stack operator role. Costs come from running the Azure Stack stamp, not from calling this API.

Can I limit what my agent is allowed to do with the Compute Admin Client?

Yes. Because you run Jentic One yourself, your own rules decide which operations and credentials the agent may use, so you can restrict it to only GET /providers/Microsoft.Compute.Admin/operations, the single read operation this API exposes. That endpoint just enumerates the available Microsoft.Compute.Admin operations on an Azure Stack stamp; it does not provision VMs or attach disks, so no write or destructive action is reachable through it. Your Azure AD credential is stored encrypted by your own instance and injected only at execution time, so it never enters the agent's prompt or logs.