For Agents
Discover the available admin backup operations on an Azure Stack Hub via the Microsoft.Backup.Admin resource provider.
Get started with BackupManagementClient in minutes using your preferred integration method.
# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
"jentic": {
"url": "https://api.jentic.com/mcp",
"auth": "oauth"
}
}
# Then ask your agent:
"list Azure Stack admin backup operations"
# → Jentic returns the GET /events tool with parameter schema, agent executes.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
Return operation display names and descriptions for catalogue or documentation generation
GET STARTED
Use for: List every admin backup operation registered on this Azure Stack stamp, Discover what backup admin operations the resource provider exposes, Retrieve the operation catalogue for Microsoft.Backup.Admin, Check whether the stamp has the Backup.Admin provider available
Not supported: Does not trigger backups, schedule jobs, or restore data — use only to enumerate admin backup operations on the Microsoft.Backup.Admin provider.
Jentic publishes the only available OpenAPI document for BackupManagementClient, keeping it validated and agent-ready.
Jentic publishes the only available OpenAPI specification for BackupManagementClient, keeping it validated and agent-ready. The Admin Backup Management Client exposes operations metadata for the Microsoft.Backup.Admin resource provider on Azure Stack Hub. It allows operators to enumerate the available admin-side backup operations against an Azure Stack stamp through its admin management endpoint.
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
1 endpoints — jentic publishes the only available openapi specification for backupmanagementclient, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
/providers/Microsoft.Backup.Admin/operations
List all admin backup operations available on the stamp
/providers/Microsoft.Backup.Admin/operations
List all admin backup operations available on the stamp
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.
Alternatives and complements available in the Jentic catalogue.
Azure Recovery Services Backup
Public Azure recovery and backup management rather than Azure Stack admin operations.
Use Recovery Services Backup for public Azure workloads; use this admin client for an on-premises Azure Stack stamp.
Azure Storage Management
Manages storage accounts that backups commonly land in.
Pick Storage Management to provision the storage backing a backup; pick this admin client to discover Azure Stack backup operations.
Azure Deployment Manager
Coordinates rollouts that may include backup configuration changes.
Use Deployment Manager when bundling backup config into a staged rollout; use this client just to query admin operation availability.
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.