Microsoft Azure HybridComputeManagementClient

Name: HybridComputeManagementClient API
Brand: Azure Hybrid Compute Management
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCloud InfrastructureComputeoauth213 EndpointsREST

For Agents

Manage Azure Arc-enabled servers as Azure resources - list machines, install or update machine extensions, and trigger reconnects.

Use for: I need to install the MMA agent extension on every Arc-enabled server, List all Arc machines in resource group 'hybrid-rg', Retrieve the OS and connection state of Arc machine 'datacenter-01', Update the tags on an Arc machine to mark it as production

Not supported: Does not perform initial Arc onboarding from the server side, run remote commands, or manage native Azure VMs - use for managing Arc-enabled machine records and extensions only.

Jentic publishes the only available OpenAPI specification for HybridComputeManagementClient, keeping it validated and agent-ready. The Azure Hybrid Compute Management API manages Azure Arc-enabled servers - the resource projection that makes on-premises and other-cloud machines first-class Azure resources. It exposes machine and machine-extension lifecycle operations alongside a reconnect endpoint used when an agent needs to re-onboard a machine. Authentication is Azure AD OAuth2 against management.azure.com, scoped under Microsoft.HybridCompute.

Install Jentic One Beta

Connect the HybridComputeManagementClient to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the HybridComputeManagementClient, 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://jentic.com/install.sh?src=apis&api=%2Fapis%2Fazure.com%2Fhybridcomputemanagementclient" | sh

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%2Fhybridcomputemanagementclient" | 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 HybridComputeManagementClient API.

List Arc-enabled machines across a subscription or filter by resource group

Retrieve the configuration and status of a specific Arc machine

Update tags or properties on an Arc-enabled machine record

Delete the Arc representation of a machine when the machine is decommissioned

GET STARTED

Start building with HybridComputeManagementClient API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use HybridComputeManagementClient API for, with concrete tasks.

★ Hybrid fleet inventory

List Arc-enabled machines across a subscription via GET /subscriptions/.../providers/Microsoft.HybridCompute/machines, returning an inventory of on-prem and other-cloud servers projected into Azure. Combine with the resource-group-scoped list to filter by environment. Useful for hybrid CMDB sync and licensing audits.

GET /subscriptions/{sub}/providers/Microsoft.HybridCompute/machines and return each machine's name, OS, and connection state.

Standardise extensions across hybrid hosts

Install or update machine extensions on every Arc machine via PUT /subscriptions/.../machines/{name}/extensions/{extensionName}. Useful for rolling out the Microsoft Monitoring Agent or DSC across a hybrid fleet so every machine reports telemetry. PATCH the same path to upgrade an extension version.

PUT /subscriptions/{sub}/resourceGroups/hybrid-rg/providers/Microsoft.HybridCompute/machines/datacenter-01/extensions/MMAExtension with the agreed agent settings, then poll until provisioningState is Succeeded.

Decommission and reconnect flows

When a server is retired, DELETE its Arc record via /subscriptions/.../machines/{name}. When an agent loses connection but the machine is still alive, POST .../machines/{name}/reconnect to refresh credentials and rejoin Arc. These operations bracket the lifecycle that field operators care about most.

POST /subscriptions/{sub}/resourceGroups/hybrid-rg/providers/Microsoft.HybridCompute/machines/datacenter-01/reconnect to bring the machine back into Arc inventory.

AI agent hybrid operations via Jentic

An infrastructure agent uses Jentic to sweep Arc-enabled servers, ensure the right extensions are installed, and trigger reconnects when machines drop out. Jentic resolves natural-language intents to the correct ARM operation and injects a scoped bearer token at execution time.

Use Jentic to search for 'install machine extension on azure arc', load MachineExtensions_CreateOrUpdate, and apply MMAExtension to every Arc machine in resource group 'hybrid-rg'.

Key Endpoints

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

METHOD

PATH

DESCRIPTION

GET

/subscriptions/{subscriptionId}/providers/Microsoft.HybridCompute/machines

List Arc machines in a subscription

GET

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.HybridCompute/machines/{name}

Get a specific Arc machine

PUT

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.HybridCompute/machines/{name}

Create or update an Arc machine record

DELETE

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.HybridCompute/machines/{name}

Delete an Arc machine record

PUT

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.HybridCompute/machines/{name}/extensions/{extensionName}

Install or update a machine extension

POST

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.HybridCompute/machines/{name}/reconnect

Trigger a reconnect on an Arc machine

GET

/subscriptions/{subscriptionId}/providers/Microsoft.HybridCompute/machines

List Arc machines in a subscription

GET

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.HybridCompute/machines/{name}

Get a specific Arc machine

PUT

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.HybridCompute/machines/{name}

Create or update an Arc machine record

DELETE

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.HybridCompute/machines/{name}

Delete an Arc machine record

PUT

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.HybridCompute/machines/{name}/extensions/{extensionName}

Install or update a machine extension

POST

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.HybridCompute/machines/{name}/reconnect

Trigger a reconnect on an Arc machine

Why Jentic?

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

Setup

Wiring Azure Arc hybrid compute by hand means creating an Azure AD service principal, exchanging its secret for a bearer token against management.azure.com, and polling the async operation header returned by extension installs. Through Jentic you install once, import Hybrid Compute Management from the API Directory, store the service principal credentials once, and your agent calls it.

Permission scoping

The machine and extension names travel in the URL path (/machines/{name}, /machines/{name}/extensions/{extensionName}), so a rule can pin your agent to listing machines and installing extensions on named Arc machines. You choose the operations it may call, so deleting an Arc machine record is not included unless you add it.

Credential isolation

Your Azure service principal credentials are stored once, encrypted, by your own Jentic One instance and exchanged for a scoped Azure AD bearer token at execution time. The client secret never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'list azure arc-enabled machines' or 'install a machine extension on azure arc', and Jentic returns the matching Machines or MachineExtensions operation with its input schema so the agent calls the right ARM endpoint without browsing Microsoft Learn.

FAQs

Specific to using HybridComputeManagementClient API through Jentic.

Why is there no official OpenAPI spec for HybridComputeManagementClient?

Microsoft Azure does not publish a stand-alone OpenAPI specification for the 2019-12-12 Hybrid Compute management surface. Jentic generates and maintains this spec from the Microsoft.HybridCompute ARM surface so that AI agents and developers can call HybridComputeManagementClient 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 this API use?

It uses Azure AD OAuth2 against management.azure.com, declared as the azure_auth security scheme. Through Jentic, your service principal credentials sit encrypted in the vault and are exchanged for a scoped bearer token at execution time.

Does this API onboard new servers to Arc?

No. The initial onboarding handshake is performed by the Azure Connected Machine agent on the server itself, which calls into Azure to register. This management API operates on the resulting Microsoft.HybridCompute/machines record. Use POST /subscriptions/.../machines/{name}/reconnect when a known machine has lost its agent connection and needs to refresh.

What are the rate limits?

Standard ARM throttles apply at the subscription level - about 12,000 reads and 1,200 writes per hour per subscription. Bulk extension installs across a large fleet should batch and back off on 429 responses.

How do I install a machine extension on every Arc machine through Jentic?

Run jentic.search('install extension on azure arc machine'), load the MachineExtensions_CreateOrUpdate schema, and execute it for each machine with the extension name and properties. Iterate over the list returned by Machines_ListBySubscription to cover the whole fleet.

Can I limit what my agent is allowed to do with the Azure Hybrid Compute Management API?

Yes. Because you run Jentic One yourself, your own rules decide which operations and credentials the agent can use, and the machine and extension names travel in the URL path (/machines/{name} and /machines/{name}/extensions/{extensionName}), so a rule can pin the agent to listing machines and installing extensions on named Arc machines. You choose the operations it may call, so deleting an Arc machine record or triggering a reconnect is excluded unless you add it. The Azure service principal credentials stay with your instance and are exchanged for a scoped bearer token only at execution time, never entering the agent's prompt or logs.

Microsoft Azure HybridComputeManagementClient

Connect the HybridComputeManagementClient to your agent

Capabilities

Start building with HybridComputeManagementClient API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs