Microsoft Azure ServiceBusManagementClient
Browse all Azure APIsAgent-ready OpenAPI document · curated by JenticCloud InfrastructureServerlessoauth265 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Provision Azure Service Bus namespaces, queues, topics, subscriptions, authorization rules, and disaster-recovery pairings through the Azure Resource Manager control plane.
Use for: Provision a new Service Bus Premium namespace in West Europe, Create a queue with dead-lettering enabled in a Service Bus namespace, Create a topic with three subscriptions filtered by a SQL rule, Rotate the primary SAS key on a namespace authorization rule
Not supported: Does not send or receive messages, manage Event Hubs, or run AMQP traffic - use for Service Bus namespace, queue, topic, and DR control-plane configuration only.
Jentic publishes the only available OpenAPI specification for ServiceBusManagementClient, keeping it validated and agent-ready. The Azure Service Bus management API exposes the Microsoft.ServiceBus resource provider so agents can provision Service Bus namespaces, create queues and topics with subscriptions and rules, manage authorization rules and shared access keys, configure network rule sets, and orchestrate geo-disaster-recovery pairings between namespaces. It is the control plane for setting up messaging infrastructure - the data plane for sending and receiving messages lives separately.
Install Jentic One Beta
Connect the ServiceBusManagementClient to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the ServiceBusManagementClient, 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%2Fazure-servicebusmanagementclient" | 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%2Fazure-servicebusmanagementclient" | 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 ServiceBusManagementClient API.
Provision Service Bus namespaces with a chosen SKU and capacity
Create queues with dead-lettering, sessions, and duplicate detection settings
Create topics with subscriptions and SQL filter rules
Manage SAS authorization rules and rotate primary or secondary keys
Configure network rule sets that restrict namespace access by VNet or IP
Pair two namespaces into a geo-disaster-recovery alias and trigger failover
Migrate a Standard namespace to Premium with a migration configuration
Use Cases
Patterns agents use ServiceBusManagementClient API for, with concrete tasks.
★ Messaging Infrastructure Provisioning
Platform teams provision Service Bus namespaces, queues, and topics as part of an environment bootstrap rather than clicking through the portal. The namespaces, queues, and topics endpoints accept the full resource definition - SKU, capacity, message TTL, lock duration, and dead-letter settings - so an agent can stand up a fully configured messaging tier from a template in one pass.
PUT a Premium namespace in West Europe, then PUT a queue named orders with deadLetteringOnMessageExpiration true and lockDuration PT1M
SAS Key Rotation
Security teams rotate Service Bus SAS keys on a schedule to limit blast radius if a key leaks. The AuthorizationRules/regenerateKeys endpoint regenerates either the primary or secondary key in place, and the listKeys endpoint returns the new connection strings so an agent can push them to dependent services or a secrets vault without downtime.
POST to /.../AuthorizationRules/{authorizationRuleName}/regenerateKeys with keyType PrimaryKey, then call listKeys and store the new connection string in the secrets manager
Geo Disaster Recovery Failover
Resilience engineers pair two Service Bus namespaces into a geo-DR alias so that consumers can keep using the same connection string when a region fails. The disasterRecoveryConfigs endpoint creates the pairing, breakPairing dissolves it, and failover promotes the secondary namespace, giving an agent the full set of operations to execute a documented runbook.
PUT a disasterRecoveryConfigs alias linking the primary and secondary namespaces, then on incident POST failover on the alias
AI Agent Messaging Setup
An agent built on Jentic stands up a complete pub-sub topology when a developer asks for somewhere to publish events. The agent provisions a namespace, creates a topic, attaches subscriptions for each consumer, and returns the connection string from listKeys, all without the developer touching the Azure portal.
Search Jentic for create azure service bus topic, load the schema, and execute PUT topics/{topicName} followed by PUT subscriptions/{subscriptionName} for each consumer
Key Endpoints
65 endpoints — jentic publishes the only available openapi specification for servicebusmanagementclient, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
PUT
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ServiceBus/namespaces/{namespaceName}
Create or update a Service Bus namespace
PUT
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ServiceBus/namespaces/{namespaceName}/queues/{queueName}
Create or update a queue
PUT
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ServiceBus/namespaces/{namespaceName}/topics/{topicName}
Create or update a topic
POST
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ServiceBus/namespaces/{namespaceName}/AuthorizationRules/{authorizationRuleName}/listKeys
List the connection strings for an authorization rule
POST
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ServiceBus/namespaces/{namespaceName}/AuthorizationRules/{authorizationRuleName}/regenerateKeys
Regenerate primary or secondary SAS key
POST
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ServiceBus/namespaces/{namespaceName}/disasterRecoveryConfigs/{alias}/failover
Trigger geo-DR failover on a namespace alias
PUT
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ServiceBus/namespaces/{namespaceName}
Create or update a Service Bus namespace
PUT
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ServiceBus/namespaces/{namespaceName}/queues/{queueName}
Create or update a queue
PUT
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ServiceBus/namespaces/{namespaceName}/topics/{topicName}
Create or update a topic
POST
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ServiceBus/namespaces/{namespaceName}/AuthorizationRules/{authorizationRuleName}/listKeys
List the connection strings for an authorization rule
POST
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ServiceBus/namespaces/{namespaceName}/AuthorizationRules/{authorizationRuleName}/regenerateKeys
Regenerate primary or secondary SAS key
POST
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ServiceBus/namespaces/{namespaceName}/disasterRecoveryConfigs/{alias}/failover
Trigger geo-DR failover on a namespace alias
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Microsoft.ServiceBus control plane by hand means registering an Azure AD app, running the OAuth2 token exchange yourself, and handling the 202 asyncOperation polling and retry-header backoff that ARM returns for namespace and queue provisioning. Through Jentic you install once, import Service Bus Management from the API Directory, store the Azure AD service principal credential once, and your agent calls it.
Permission scoping
Service Bus puts the subscription, resource group, and namespace in the URL path (/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ServiceBus/namespaces/{namespaceName}/...), so a rule can pin your agent to one namespace and its queues and topics. You choose the operations it may call, so destructive ones like regenerateKeys or a disaster-recovery failover are not included unless you add them.
Credential isolation
Your Azure AD service principal 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, and neither do the SAS connection strings returned by listKeys.
Intent-based discovery
Agents search Jentic by intent such as 'create an Azure Service Bus queue' or 'rotate a Service Bus SAS key', and Jentic returns the matching Microsoft.ServiceBus operation with its input schema so the agent calls the right endpoint without reading the ARM reference.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using ServiceBusManagementClient API through Jentic.
Why is there no official OpenAPI spec for ServiceBusManagementClient?
Microsoft Azure does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call ServiceBusManagementClient 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 the Service Bus management API use?
It uses Azure AD OAuth 2.0 with the implicit flow against https://login.microsoftonline.com/common/oauth2/authorize and the user_impersonation scope. When called through Jentic, your AAD service principal credentials live in your Jentic One instance and the agent receives only a short-lived bearer token.
Can I send messages with this API?
No - this is the management control plane. To send and receive messages you use the Service Bus AMQP or REST data plane endpoints scoped to the namespace's servicebus.windows.net hostname. Use this management API to provision the namespace, queues, topics, and authorization rules first, then use the data plane for messaging.
How do I rotate a Service Bus SAS key?
POST to /.../namespaces/{namespaceName}/AuthorizationRules/{authorizationRuleName}/regenerateKeys with a body containing keyType set to PrimaryKey or SecondaryKey. Then call listKeys at the same authorization rule path to retrieve the new connection strings.
What are the rate limits for this API?
Azure Resource Manager throttles around 12,000 reads and 1,200 writes per hour per principal at subscription scope, surfaced via x-ms-ratelimit-remaining-subscription-reads and x-ms-ratelimit-remaining-subscription-writes headers. Long namespace provisioning operations return a 202 with an asyncOperation URL to poll.
How do I create a topic with subscriptions through Jentic?
Search Jentic for create azure service bus topic, load the schema for PUT /.../topics/{topicName}, execute it, then PUT each subscription under /.../topics/{topicName}/subscriptions/{subscriptionName}. The full search, load, and execute pattern is in the Jentic Python SDK after pip install jentic.
Can I trigger a geo-DR failover with this API?
Yes. POST to /.../disasterRecoveryConfigs/{alias}/failover on the secondary namespace and the alias promotes it to primary. /breakPairing on either namespace dissolves the pairing without failover when you simply want to detach.
Can I limit what my agent is allowed to do with the Service Bus Management API?
Yes. Because Jentic One is self-hosted, your own rules decide which Microsoft.ServiceBus operations and credentials the agent may use. Since the subscription, resource group, and namespace all sit in the URL path, you can pin the agent to a single namespace and its queues and topics. You also pick the exact operations it may call, so destructive ones like regenerateKeys or a disaster-recovery failover stay out of reach unless you add them.
GET STARTED