Microsoft Azure BackupManagementClient

Name: BackupManagementClient API
Brand: BackupManagementClient
Availability: InStock

★ Only Publicly Available OpenAPI DocumentStorageBackup Recoveryoauth21 EndpointsREST

For Agents

Discover the available admin backup operations on an Azure Stack Hub via the Microsoft.Backup.Admin resource provider.

Install Jentic One Beta

Connect the BackupManagementClient to your agent

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

Enumerate every available admin backup operation under the Microsoft.Backup.Admin resource provider

Discover operation IDs that downstream Azure Stack admin tooling can call

Query the resource provider against the local Azure Stack admin management endpoint

GET STARTED

Start building with BackupManagementClient API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use BackupManagementClient API for, with concrete tasks.

★ Discover admin backup operations on a stamp

Stamp operators call the operations endpoint to enumerate the admin-side backup operations available on Microsoft.Backup.Admin. The response feeds into operator dashboards or CMDB inventories so administrators know exactly which control-plane actions exist before invoking any of them.

Call GET /providers/Microsoft.Backup.Admin/operations and return the list of operation names plus display strings

Build a catalogue of stamp backup capabilities

Tooling that maintains an inventory of Azure Stack stamps polls this operations endpoint per stamp to build a capability matrix. It surfaces any drift between stamps and lets operators see at a glance which version of the Backup.Admin provider is deployed.

For each Azure Stack stamp in the inventory, call Operations_List and store the operation set keyed by stamp ID

AI agent integration via Jentic

An Azure Stack operator agent uses Jentic to discover backup admin capabilities without learning the admin URL convention. The agent searches Jentic for 'list Azure Stack admin backup operations', loads the schema, and executes the call. Jentic handles AAD auth against the admin management endpoint so the agent never has to manage admin tokens directly.

Use Jentic search 'list Azure Stack admin backup operations' and execute Operations_List against the stamp

Key Endpoints

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

METHOD

PATH

DESCRIPTION

GET

/providers/Microsoft.Backup.Admin/operations

List all admin backup operations available on the stamp

GET

/providers/Microsoft.Backup.Admin/operations

List all admin backup operations available on the stamp

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 the Azure Stack admin endpoint — client secrets never enter agent context.

Intent-based discovery

Agents search Jentic by intent, e.g. 'list Azure Stack admin backup operations', and Jentic returns Operations_List with its input schema so the agent calls the right endpoint without browsing admin docs.

Time to first call

Direct integration: 1-2 days for AAD admin auth and stamp connectivity. Through Jentic: under 1 hour — search, load schema, execute.

FAQs

Specific to using BackupManagementClient API through Jentic.

Why is there no official OpenAPI spec for BackupManagementClient?

Microsoft Azure does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call BackupManagementClient 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 BackupManagementClient API use?

The API uses Azure Active Directory OAuth 2.0 declared as azure_auth with the implicit flow. Calls go to the Azure Stack admin management endpoint (adminmanagement.local.azurestack.external) and tokens are presented as Bearer headers. Through Jentic, AAD client secrets are vault-stored and only short-lived scoped tokens reach the agent.

Can I trigger a backup with this API?

No. This admin client only exposes the operations endpoint that lists what Microsoft.Backup.Admin can do. Triggering, scheduling, or restoring backups is handled by other operations under the same resource provider that are not part of this spec.

What are the rate limits for the BackupManagementClient API?

Azure Stack admin endpoints apply ARM-style subscription throttling, typically 12,000 reads per hour, surfaced via x-ms-ratelimit-remaining headers. The admin Backup endpoint does not document additional limits beyond ARM.

How do I list admin backup operations through Jentic?

Run pip install jentic, then use the async client to search 'list Azure Stack admin backup operations', load the Operations_List operation, and execute. Jentic returns the array of operation names that the stamp's Backup.Admin provider exposes.

Does this API target public Azure or Azure Stack only?

It targets the Azure Stack admin management endpoint at adminmanagement.local.azurestack.external. Public Azure backup management is exposed through a different resource provider and base URL.