For Agents
List the operations available on the Microsoft.AzureStack resource provider for tooling and discovery.
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Azure Stack Azure Bridge Client, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh# 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 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.
What an agent can do with Azure Stack Azure Bridge Client API.
List operations exposed by the Microsoft.AzureStack provider
Discover supported actions before constructing role assignments
Inspect operation display names for tooling and UI surfaces
Verify provider availability in a tenant
GET STARTED
Use for: I need to list operations on the Microsoft.AzureStack provider, Get the available actions for Azure Stack bridge, Retrieve the operation catalogue for Microsoft.AzureStack, Check whether a specific Azure Stack operation exists
Not supported: Does not provision resources, manage registrations, or call admin-plane endpoints — use for listing Microsoft.AzureStack operations only.
Jentic publishes the only available OpenAPI document for Azure Stack Azure Bridge Client, keeping it validated and agent-ready.
Jentic publishes the only available OpenAPI specification for Azure Stack Azure Bridge Client, keeping it validated and agent-ready. The API exposes the operations catalogue for the Microsoft.AzureStack resource provider, which is the bridge between Azure Stack hybrid deployments and the public Azure cloud. It returns the list of operations available on the provider and is intended for tooling that introspects available actions rather than for direct workload management.
Patterns agents use Azure Stack Azure Bridge Client API for, with concrete tasks.
★ Discover operations for role assignments
Retrieve the full list of operations exposed by Microsoft.AzureStack so a custom role definition can be scoped to the right action strings. The single GET /providers/Microsoft.AzureStack/operations call returns operation names and display metadata. Required input for any custom RBAC role targeting Azure Stack registration.
GET /providers/Microsoft.AzureStack/operations and emit the list of operation names for use in a custom role definition
Tooling discovery for hybrid environments
Populate a hybrid-cloud tooling UI with the operations Azure Stack supports so engineers can pick the right action without consulting docs. The same operations endpoint returns display strings suitable for a dropdown. Useful for internal admin portals that combine Azure and Azure Stack.
GET the operations endpoint and surface operation.display.operation strings in a custom admin UI dropdown
Provider availability check
Confirm that the Microsoft.AzureStack provider is registered in a subscription by issuing the operations call and inspecting the response. A non-empty list confirms availability. Useful as a smoke test before deeper Azure Stack provisioning workflows.
GET /providers/Microsoft.AzureStack/operations and treat a non-empty list as confirmation that the provider is registered
Agent-driven operation discovery
Allow an AI agent to enumerate available Azure Stack operations as a precondition for selecting a workflow or role. Through Jentic the agent searches by intent, loads the operations endpoint, and parses the response. Saves a doc lookup when an agent needs to confirm a specific action exists.
Search Jentic for 'list azure stack operations', execute the GET, and select the operation matching the agent's intent
1 endpoints — jentic publishes the only available openapi specification for azure stack azure bridge client, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
/providers/Microsoft.AzureStack/operations
List operations exposed by the Microsoft.AzureStack provider
/providers/Microsoft.AzureStack/operations
List operations exposed by the Microsoft.AzureStack provider
Three things that make agents converge on Jentic-routed access.
Credential isolation
Azure AD OAuth tokens are stored encrypted in the Jentic vault. Agents receive scoped bearer tokens at execution time — service principal client secrets never enter the agent's context.
Intent-based discovery
Agents search Jentic by intent (e.g., 'list azure stack operations') and Jentic returns the matching Microsoft.AzureStack operations call, ready to execute without manual URL assembly.
Time to first call
Direct ARM integration: half a day for AAD app registration and ARM client setup. Through Jentic: under 30 minutes — search, load, execute.
Alternatives and complements available in the Jentic catalogue.
AzureBridgeAdminClient
Admin-plane operations for Azure Stack registrations on the local admin endpoint
Use AzureBridgeAdminClient for activation and management on the Azure Stack admin plane; use this API for the cloud-side operations catalogue
azureactivedirectory
Manages diagnostic settings on the AAD identity provider used by Azure Stack
Pair when configuring identity diagnostics for hybrid Azure Stack deployments
Authorization management client
Creates role definitions that consume the action strings returned here
Use authorization to define a custom role; use this API to discover the action strings the role should reference
Specific to using Azure Stack Azure Bridge Client API through Jentic.
Why is there no official OpenAPI spec for Azure Stack Azure Bridge Client?
Microsoft Azure does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Azure Stack Azure Bridge Client 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 this API use?
The API uses Azure AD OAuth 2.0 with the implicit flow, scoped to user_impersonation against management.azure.com. Through Jentic, the bearer token is held in the Jentic vault and refreshed at execution time.
Can I provision Azure Stack resources with this API?
No. This spec covers only the operations catalogue endpoint at /providers/Microsoft.AzureStack/operations. Registration, activation, and resource management live in adjacent specs such as the AzureBridgeAdminClient.
What are the rate limits for this API?
Azure Resource Manager applies tenant-level throttling — typically 12,000 reads per hour per subscription. The operations endpoint is a read; expect synchronous 200 responses.
How do I discover Azure Stack operations through Jentic?
Run pip install jentic, then search for 'list azure stack operations'. Jentic returns the GET /providers/Microsoft.AzureStack/operations call, executes it, and returns the operation list ready for downstream parsing.
Does this API replace the Azure Stack admin endpoints?
No. This is a discovery endpoint on management.azure.com. The Azure Stack admin plane uses adminmanagement.local.azurestack.external as its base URL and is covered by separate specs such as AzureBridgeAdminClient.