Microsoft Azure BatchManagement

Name: BatchManagement API
Brand: BatchManagement
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCloud InfrastructureComputeoauth235 EndpointsREST

For Agents

Provision Azure Batch accounts and manage their pools, applications, certificates, and keys for parallel compute workloads.

Install Jentic One Beta

Connect the BatchManagement to your agent

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

Provision and tag Batch accounts in any subscription with check-name-availability support

Rotate primary and secondary account keys via the regenerateKeys operation

Manage application and application package versions with activation control

GET STARTED

Start building with BatchManagement API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use BatchManagement API for, with concrete tasks.

★ HPC render farm provisioning

Studios provision Batch accounts and large pools to run distributed render jobs. They use BatchAccount_Create to set up the account, Pool_Create to define a pool of render nodes, and ApplicationPackage_Create plus ApplicationPackage_Activate to ship the renderer binaries. When a job ends, Pool_Update scales the pool down to zero to avoid charges.

Create a Batch account in West Europe, provision a 50-node pool with a Linux VM image, upload an application package, and activate it

Periodic key rotation

Security teams rotate Batch account keys on a schedule. BatchAccount_RegenerateKey rotates either the primary or secondary key, and BatchAccount_GetKeys returns the current pair so dependent services can be updated. This pattern keeps long-lived Batch credentials fresh without downtime.

Call BatchAccount_RegenerateKey for the secondary key, update consuming services to use it, then rotate the primary key

Quota and capacity audit

FinOps teams audit Batch core quotas across regions to forecast capacity for upcoming workloads. Location_GetQuotas returns per-region core counts, and BatchAccount_ListByResourceGroup walks the accounts in scope so consumed cores can be summed against the quota.

For each region, call Location_GetQuotas and compare the dedicated core count to the sum of pool sizes returned by Pool_ListByBatchAccount

AI agent integration via Jentic

An infrastructure agent uses Jentic to provision Batch accounts and pools on demand for ad-hoc HPC workloads. The agent searches Jentic for 'create an Azure Batch pool', loads the Pool_Create schema, and executes with structured input. Jentic mints AAD tokens against management.azure.com so credentials never reach the agent.

Use Jentic search 'provision an Azure Batch pool', load Pool_Create, and execute with VM size and target node count

Key Endpoints

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

METHOD

PATH

DESCRIPTION

PUT

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Batch/batchAccounts/{accountName}

Create or update a Batch account

POST

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Batch/batchAccounts/{accountName}/regenerateKeys

Regenerate primary or secondary account keys

PUT

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Batch/batchAccounts/{accountName}/pools/{poolName}

Create a Batch pool

POST

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Batch/batchAccounts/{accountName}/pools/{poolName}/disableAutoScale

Disable auto-scale on a pool

POST

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Batch/batchAccounts/{accountName}/applications/{applicationName}/versions/{versionName}/activate

Activate an application package version

GET

/subscriptions/{subscriptionId}/providers/Microsoft.Batch/locations/{locationName}/quotas

Get Batch quotas for a region

PUT

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Batch/batchAccounts/{accountName}

Create or update a Batch account

POST

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Batch/batchAccounts/{accountName}/regenerateKeys

Regenerate primary or secondary account keys

PUT

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Batch/batchAccounts/{accountName}/pools/{poolName}

Create a Batch pool

POST

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Batch/batchAccounts/{accountName}/pools/{poolName}/disableAutoScale

Disable auto-scale on a pool

POST

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Batch/batchAccounts/{accountName}/applications/{applicationName}/versions/{versionName}/activate

Why Jentic?

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

Credential isolation

Azure AD OAuth 2.0 tokens are minted and rotated inside the Jentic vault. Agents receive scoped, short-lived tokens for management.azure.com — client secrets never enter agent context.

Intent-based discovery

Agents search Jentic by intent, e.g. 'provision an Azure Batch pool', and Jentic returns Pool_Create with its input schema so the agent calls the right endpoint without browsing ARM docs.

Time to first call

Direct integration: 2-4 days for AAD auth, ARM polling, and Batch lifecycle handling. Through Jentic: under 1 hour — search, load schema, execute.

FAQs

Specific to using BatchManagement API through Jentic.

Why is there no official OpenAPI spec for BatchManagement?

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

What authentication does the BatchManagement API use?

The API uses Azure Active Directory OAuth 2.0 declared as azure_auth with the implicit flow. Tokens are presented as Bearer headers against management.azure.com. Through Jentic, the AAD client secret stays in the vault and the agent only ever sees scoped, short-lived tokens.

Can I submit Batch jobs and tasks with this API?

No. This is the management plane — it provisions Batch accounts, pools, applications, and certificates. Job and task submission happens on the Batch service data plane (batch.<region>.azure.com), which is a separate API.

What are the rate limits for the BatchManagement API?

Azure Resource Manager applies subscription-level throttling, typically 12,000 read and 1,200 write requests per hour, surfaced via x-ms-ratelimit-remaining headers. Batch also has per-region core quotas returned by Location_GetQuotas.

How do I provision a Batch pool through Jentic?

Run pip install jentic, then use the async client to search 'provision an Azure Batch pool', load Pool_Create, and execute with subscriptionId, resourceGroupName, accountName, poolName, and a body specifying the VM size, image, and target node count. Jentic returns the pool resource once provisioning starts.

Can I rotate Batch account keys without downtime?

Yes. The standard pattern is to regenerate the secondary key first via BatchAccount_RegenerateKey, update consumers to use it, then rotate the primary key. Both keys remain valid until each individual rotation completes.

Microsoft Azure BatchManagement

Connect the BatchManagement to your agent

Capabilities

Start building with BatchManagement API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs