Microsoft Azure AzureBridgeAdminClient
Browse all Azure APIsAgent-ready OpenAPI document · curated by JenticCloud InfrastructureComputeoauth24 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Manage Azure Bridge activations on the Azure Stack admin plane that link a hub to a public Azure subscription.
Use for: I need to register an Azure Bridge activation on Azure Stack, List Azure Bridge activations in a resource group, Get a named activation on the Azure Stack admin plane, Delete an Azure Bridge activation
Not supported: Does not manage tenant subscriptions, marketplace items, or public-cloud resources - use for Azure Bridge activations on the Azure Stack admin plane only.
Jentic publishes the only available OpenAPI specification for AzureBridgeAdminClient, keeping it validated and agent-ready. The API runs on the Azure Stack admin plane and manages Azure Bridge activations - the registration that links an Azure Stack hub to a public Azure subscription so syndicated marketplace items can flow into the hub. It targets the Microsoft.AzureBridge.Admin resource provider and is intended for Azure Stack operators administering registration objects, not for tenant-side workloads.
Install Jentic One Beta
Connect the AzureBridgeAdminClient to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the AzureBridgeAdminClient, 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%2Fazurebridgeadminclient" | 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%2Fazurebridgeadminclient" | 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 AzureBridgeAdminClient API.
List Azure Bridge activations in a resource group
Retrieve a named activation on the Azure Stack admin plane
Create or update an activation linking a hub to a public Azure subscription
Delete an activation to break the link to public Azure
Audit which resource groups host Azure Bridge activations
Use Cases
Patterns agents use AzureBridgeAdminClient API for, with concrete tasks.
★ Register marketplace syndication
Create an Azure Bridge activation so Azure Stack can pull syndicated marketplace items from a public Azure subscription. The PUT /activations/{activationName} operation accepts the public subscription credentials and registers the link. Required first step before any marketplace syndication workflow on Azure Stack.
PUT /resourcegroups/{rg}/providers/Microsoft.AzureBridge.Admin/activations/{name} with the registration properties and verify provisioningState=Succeeded
Audit activations across stamps
Walk every resource group on an Azure Stack stamp and list its Bridge activations to confirm only sanctioned hubs are linked to public Azure. The GET /activations collection returns each named activation. Output supports compliance reporting on hybrid-cloud connectivity.
Iterate every resource group on the admin plane, GET its Microsoft.AzureBridge.Admin/activations collection, and emit a CSV of activation names per resource group
Decommission a hub registration
Remove an Azure Bridge activation when retiring an Azure Stack hub or breaking its link to public Azure. The DELETE /activations/{activationName} operation removes the registration. Standard part of the Azure Stack decommissioning runbook.
DELETE /resourcegroups/{rg}/providers/Microsoft.AzureBridge.Admin/activations/{name} and confirm subsequent GET returns 404
Agent-driven Azure Stack admin
Allow an AI agent operating against an Azure Stack admin plane to register, inspect, or remove Azure Bridge activations as part of a broader hybrid-cloud workflow. Through Jentic the agent searches by intent, loads the activation schema, and executes against the local admin endpoint. Removes a class of typos when constructing the long Microsoft.AzureBridge.Admin resource path.
Search Jentic for 'register azure bridge activation', load the activation properties schema, and execute the PUT against the admin endpoint
Key Endpoints
4 endpoints — jentic publishes the only available openapi specification for azurebridgeadminclient, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
GET
/subscriptions/{subscriptionId}/resourcegroups/{resourceGroup}/providers/Microsoft.AzureBridge.Admin/activations
List activations in a resource group
GET
/subscriptions/{subscriptionId}/resourcegroups/{resourceGroup}/providers/Microsoft.AzureBridge.Admin/activations/{activationName}
Get a specific activation
PUT
/subscriptions/{subscriptionId}/resourcegroups/{resourceGroup}/providers/Microsoft.AzureBridge.Admin/activations/{activationName}
Create or update an activation
DELETE
/subscriptions/{subscriptionId}/resourcegroups/{resourceGroup}/providers/Microsoft.AzureBridge.Admin/activations/{activationName}
Delete an activation
GET
/subscriptions/{subscriptionId}/resourcegroups/{resourceGroup}/providers/Microsoft.AzureBridge.Admin/activations
List activations in a resource group
GET
/subscriptions/{subscriptionId}/resourcegroups/{resourceGroup}/providers/Microsoft.AzureBridge.Admin/activations/{activationName}
Get a specific activation
PUT
/subscriptions/{subscriptionId}/resourcegroups/{resourceGroup}/providers/Microsoft.AzureBridge.Admin/activations/{activationName}
Create or update an activation
DELETE
/subscriptions/{subscriptionId}/resourcegroups/{resourceGroup}/providers/Microsoft.AzureBridge.Admin/activations/{activationName}
Delete an activation
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the AzureBridgeAdminClient API by hand means registering an Azure AD app for OAuth2 bearer auth against the Azure Stack admin host adminmanagement.local.azurestack.external rather than public Azure, holding an admin role on the stamp, and building the long Microsoft.AzureBridge.Admin resource path. Through Jentic you install once, import AzureBridgeAdminClient from the API Directory, store the Azure AD credential once, and your agent calls it.
Permission scoping
The resource group and activation name sit in the URL path (/resourcegroups/{resourceGroup}/providers/Microsoft.AzureBridge.Admin/activations/{activationName}), so a rule can pin your agent to one activation. You choose the operations it may call, so the DELETE that breaks a hub's link to public Azure is not included unless you add it.
Credential isolation
Your Azure AD admin 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 'register an azure bridge activation on azure stack' or 'list activations in a resource group', and Jentic returns the matching Microsoft.AzureBridge.Admin activations operation with its property schema so the agent calls the right endpoint without memorising the admin-plane path.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using AzureBridgeAdminClient API through Jentic.
Why is there no official OpenAPI spec for AzureBridgeAdminClient?
Microsoft Azure does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call AzureBridgeAdminClient 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 this API use?
The API uses Azure AD OAuth 2.0 with the implicit flow against the Azure Stack admin endpoint. The caller must have an admin role on the stamp. Through Jentic, the bearer token is held in your Jentic One instance and exchanged for a scoped access token at execution time.
Can I use this API against the public Azure cloud?
No. The base URL is adminmanagement.local.azurestack.external - this API runs on the Azure Stack admin plane and is unreachable from public Azure. Use it only when operating directly against an Azure Stack stamp.
What are the rate limits for this API?
Azure Stack admin endpoints share the same Resource Manager throttling model - typically 12,000 reads and 1,200 writes per hour per subscription scope. Activation operations may be long-running and return 202 Accepted; track via the operation status endpoint.
How do I register an activation through Jentic?
Run pip install jentic, then search for 'register azure bridge activation'. Jentic returns the PUT /activations/{name} operation, loads the activation properties schema, and executes against the Azure Stack admin endpoint.
Does this API manage tenant subscriptions or marketplace items directly?
No. This API only manages activation registrations. Tenant subscriptions, marketplace item syndication, and offers are handled by adjacent admin specs on the same admin plane.
Can I limit what my agent is allowed to do with the Microsoft Azure Bridge Admin API?
Yes. Because Jentic One is self-hosted, your own rules decide which operations and credentials the agent may use. The resource group and activation name live in the URL path (/resourcegroups/{resourceGroup}/providers/Microsoft.AzureBridge.Admin/activations/{activationName}), so a rule can pin your agent to a single activation. You also choose which operations it may call, so the DELETE that breaks a hub's link to public Azure is excluded unless you explicitly add it.
GET STARTED