Microsoft Azure AzureBridgeAdminClient

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.