Microsoft Azure BatchManagement
Browse all Azure APIs40
AI ReadinessNon-Ready (F)40/100
Agent-ready OpenAPI document · curated by JenticCloud InfrastructureComputeoauth235 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Provision Azure Batch accounts and manage their pools, applications, certificates, and keys for parallel compute workloads.
Use for: I need to provision a new Azure Batch account in a target region, Rotate the primary key on a Batch account for security compliance, Resize a Batch pool from 100 to 0 nodes after a render finishes, Disable auto-scale on a Batch pool while debugging job submission
Not supported: Does not submit Batch jobs or tasks, manage data-plane operations, or run computations - use for Batch account, pool, application, and certificate management only.
Jentic publishes the only available OpenAPI specification for BatchManagement, keeping it validated and agent-ready. The Azure Batch management API provisions and operates Batch accounts, the parallel compute service used for HPC, rendering, and stress testing on Azure. It manages account-level concerns like keys and quotas plus the resources inside an account - applications, application packages, certificates, and pools - including pool resizing, auto-scale, and key rotation operations.
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.
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%2Fbatch-management" | sh2
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%2Fbatch-management" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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
Create, resize, and update Batch pools including disabling auto-scale and stopping resize operations
Provision certificates in a Batch account and cancel deletion when needed
Inspect per-region Batch quotas via the Location_GetQuotas operation
Synchronise auto-storage keys for an account against a linked storage account
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
Activate an application package version
GET
/subscriptions/{subscriptionId}/providers/Microsoft.Batch/locations/{locationName}/quotas
Get Batch quotas for a region
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.
B
BatchManagement
- Non-Ready (F)40/100
61
Foundational Compliance63
Developer Experience & Jentic Compatibility19
AI-Readiness & Agent Experience94
Agent Usability35
Security100
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
61
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: B-Signals: 4
70%
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).
75%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
63
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: B-Signals: 4
0%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
50%
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.
19
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: FSignals: 4
69%
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.
5%
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.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the BatchManagement API by hand means configuring Azure AD OAuth2 against management.azure.com, handling the control-plane and data-plane split so you only manage accounts and pools, and threading account, pool, and application ids through every Microsoft.Batch path yourself. Through Jentic you install once, import BatchManagement from the API Directory, store the Azure AD credential once, and your agent calls it.
Permission scoping
This API puts the account, pool, and application ids in the URL path (/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Batch/batchAccounts/{accountName}/pools/{poolName}), so a rule can pin your agent to one Batch account and its pools. You choose the operations it may call, so destructive ones like regenerating account keys or disabling pool autoscale are not included unless you add them.
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 'provision an Azure Batch pool' or 'create a Batch account', and Jentic returns the matching Pool or BatchAccount operation with its input schema so the agent calls the right ARM path without browsing the Microsoft.Batch reference.
Related APIs
Alternatives and complements available in the Jentic catalogue.
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 with Jentic One, the self-hosted execution layer.
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.
Can I limit what my agent is allowed to do with the Azure Batch Management API?
Yes. Because you run Jentic One yourself, your own rules decide which operations and credentials the agent may use, and this API puts the subscription, resource group, Batch account, and pool ids in the URL path, so a rule can pin the agent to one Batch account and its pools. You choose exactly which operations it can call, so read-only work like listing pools or checking quotas via Location_GetQuotas can be allowed while destructive calls such as BatchAccount_RegenerateKey or disabling pool auto-scale are left out. Your Azure AD credential is stored encrypted by your own instance and injected only at execution time, so the agent never sees it directly.
GET STARTED