Azure Service Bus

Azure Service Bus is a fully managed enterprise message broker with message queues and publish-subscribe topics, providing reliable message delivery for decoupling applications and services in cloud and hybrid environments.

Azure Service Bus publishes 6 API contracts indexed on the APIs.io network, including Namespaces API, Queues API, Subscriptions API, and 3 more. Tagged areas include Microsoft Azure, Cloud, Enterprise, Message Broker, and Messaging.

The Azure Service Bus catalog on APIs.io includes 1 event-driven AsyncAPI specification, 1 JSON-LD context, and 3 Spectral governance rulesets.

Azure Service Bus’ developer surface includes support, Stack Overflow tag, authentication, developer portal, documentation, getting-started guide, pricing, and 24 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

68.0/100 exemplar ▬ flat Agent 26/100 agent aware open core · MIT Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

AccessPaidSelf serve

1 published contract 6 Features 4 Use Cases

Microsoft Azure Cloud Enterprise Message Broker Messaging Pub/Sub Queues Real-Time

What this lets a business do 1

Business capabilities this provider's published APIs can perform, derived from its own contracts. Browse all capabilities →

Information Technology Management

BC-600

NamespacesQueuesSubscriptionsTopics

PUT /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ServiceBus/namespaces/{namespaceName} PUT /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ServiceBus/namespaces/{namespaceName}/queues/{queueName} GET /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ServiceBus/namespaces/{namespaceName}/topics/{topicName}/subscriptions PUT /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ServiceBus/namespaces/{namespaceName}/topics/{topicName}

What people ask Azure Service Bus 5

The questions people put to an LLM, and the jobs they hand an agent, that Azure Service Bus's APIs answer — each one linked to the operation that does it. Generated by API Evangelist

Azure Service Bus Messages API Send a message to a queue or topic “How do I post a message onto an Azure Service Bus queue over REST?” Receive and delete the next queued message “How do I pull the next message off a queue and remove it in one step?” Peek and lock the next message for processing “How do I read the next message but keep it on the queue until I finish processing it?” Complete a peek-locked message “How do I mark a locked message as successfully processed so it leaves the queue?”

Azure Service Bus Namespaces API List all Service Bus namespaces in a subscription “Which Service Bus namespaces exist across my whole Azure subscription?” List namespaces in a resource group “What Service Bus namespaces are in this particular resource group?” Get details of a namespace “How do I look up the configuration of one specific Service Bus namespace?” Create or update a Service Bus namespace “How do I provision a new Service Bus namespace in a region?”

Azure Service Bus Topics API List the topics in a namespace “Which topics are defined in my Service Bus namespace?” Get a topic's description “How do I check how a single Service Bus topic is configured?” Create or update a topic “How do I add a new publish-subscribe topic to a Service Bus namespace?” Delete a topic “How do I remove a topic from a Service Bus namespace?”

Azure Service Bus Subscriptions API List the subscriptions on a topic “Which subscriptions are listening on my Service Bus topic?” Get a topic subscription's description “How do I look up the settings of one subscription on a topic?” Create or update a topic subscription “How do I subscribe a new consumer to a Service Bus topic?” Delete a topic subscription “How do I stop a subscriber from receiving a topic's messages by removing its subscription?”

Azure Service Bus Queues API List the queues in a namespace “Which queues are defined in my Service Bus namespace?” Get a queue's description “How do I check the settings of a single Service Bus queue?” Create or update a queue “How do I add a new queue to a Service Bus namespace?” Delete a queue “How do I remove a queue from a Service Bus namespace?”

Kin Score

Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0

Composite quality — 68.0/100 · exemplar

Contract Quality 10.2 / 16

Developer Ergonomics 8.5 / 13

Access Clarity 9.2 / 13

Operational Transparency 4.4 / 8

Contract Governance 1.1 / 8

Discoverability 4.6 / 7

Regulatory Posture 6.0 / 15

Open Source Surface 10.0 / 10

Create-or-Update Ergonomics 2.2 / 10

Agent readiness — 26/100 · agent aware

Machine-Readable Contract 18 / 18

Agentic Access Contract 10 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 0 / 8

Request/Response Examples 7 / 7

Rate-Limit Signaling 7 / 7

Typed Event Surface 6 / 6

Agent Skills 0 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 5 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the Horizontal (data, software, accessibility, platform) regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Open Source Surface applies to this provider. This product is open source and we read its repository directly, so Open Source Surface carries 10 points of the composite. It is scored from what the repository actually publishes — a security policy, a contribution guide, a release history, a code of conduct — read live from the provider rather than inferred from our own catalog pointers. This facet adds; nothing was taken away to make room for it. An open-source project is not excused from the commercial facets, because exemption would strip it of the points it does earn. If we have the wrong repository, or this product is not open source, say so on your provider repo and we will drop the facet rather than have you publish against it.

Create-or-Update Ergonomics applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.

The six quality facets above are damped to 65 points between them, because both conditional facets apply and carry 35 points together. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 65% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/azure-service-bus/"><img src="https://apis.io/badge/azure-service-bus/card.svg" alt="Azure Service Bus on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
Stable Error Semantics +8 pts — OpenAPI $refs a shared error schema across 4xx/5xx responses (verified), else common[].type includes ErrorCatalog / ErrorCodes / DeclineCodes
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Registration Without a Human +6 pts — a `registration_endpoint` in the served RFC 8414 / OIDC discovery document
Delegated User Identity +6 pts — a served discovery document listing authorization_code in grant_types_supported (served), else an oauth2 authorizationCode flow or openIdConnect declared in an OpenAPI (documented)

7 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Contract Governance scores 13.6 — up to +10.4 composite points
Contract Quality scores 62.8 — up to +9.3 composite points
Developer Ergonomics scores 65.5 — up to +6.9 composite points

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/azure-service-bus/apis.yml: open an issue on github.com/api-evangelist/azure-service-bus to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Standards implemented 3

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

Pub/Sub

tagged — the provider's own APIs.json carries the standard as a tag; implementation not verified

OpenAPI

Prices published by Azure Service Bus, read 2026-09-20 from azure.microsoft.com/en-us/pricing/details/service-bus/.

Plan	Price
Premium Geo-Replication Zone 1 (North America and Europe)	$0.09/GB
Premium Geo-Replication Zone 2 (Asia, Oceania, Middle East, and Africa)	$0.12/GB
Premium Geo-Replication Zone 3 (South America)	$0.23/GB
Basic Operations	$- per million operations
Standard Base charge	$-/hour Includes: First 13M ops/month Included; 1,000 brokered connections
Premium Hourly	$-/hour Includes: Operations included up to purchased capacity; brokered connections not charged
Hybrid Connection	$- per listener Includes: includes 5 GB of data/month
WCF Relay	$- for every 100 relay hours

Plan details, limits and sources →

Rate limits

Free Tier Default: 10 requests per minute
Free Tier Monthly Quota: 1000 requests per month
Professional Tier Default: 100 requests per minute

Compiled by API Evangelist, not yet checked against Azure Service Bus's documentation. All 5 limits →

Billed by: gb replicated · FinOps profile →

Pricing Plans 1

Published pricing tiers and plan structures.

Azure Service Bus Plans Pricing

8 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Azure Service Bus Rate Limits

5 limits

RATE LIMITS

Service Levels 1

Uptime the provider promises or reports, as SLA4OAI. Read from its own pages; APIs.io runs no monitors.

Azure Service Bus

SLA

FinOps 1

Cost, billing, and metering signals for API financial operations.

Azure Service Bus Finops

FINOPS

Features 6

Notable capabilities this provider offers.

Message Queues

Point-to-point messaging with FIFO delivery, sessions, dead-lettering, and duplicate detection for reliable asynchronous communication.

Publish-Subscribe Topics

One-to-many messaging with topic subscriptions, filters, and actions for event-driven architectures.

Dead-Letter Queue

Automatic routing of undeliverable or failed messages to a secondary queue for inspection and reprocessing.

Scheduled Delivery

Schedule messages for future delivery at a specified time without requiring sender availability.

Transactions

ACID transaction support for grouping multiple operations across queues and topics into atomic units.

Auto-Forwarding

Automatically forward messages from one queue or subscription to another entity for chaining processing stages.

Event Specifications 1

AsyncAPI definitions for this provider's event-driven and streaming APIs.

Azure Service Bus Messaging

Azure Service Bus is a fully managed enterprise message broker with message queues and publish-subscribe topics. This AsyncAPI spec describes the messaging patterns for sending ...

ASYNCAPI

Semantic Vocabularies 1

JSON-LD contexts and semantic vocabularies used across these APIs.

Azure Service Bus Context

0 classes · 0 properties

JSON-LD

Spectral Rules 3

Spectral governance rulesets for linting and validating these APIs.

Azure Service Bus — asyncapi rules

3 rules · 2 warnings 1 info

SPECTRAL

Azure Service Bus — jsonschema rules

5 rules · 3 warnings 2 info

SPECTRAL

Azure Service Bus API Rules

14 rules · 8 errors 5 warnings 1 info

SPECTRAL

Standalone JSON Schema definitions for this provider's data models.

SBNamespaceListResult

security.txt · contact published

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Azure Service Bus Scopes

1 scope · implicit

1 scopes

SCOPES

Agentic Access 1

Recommended x-agentic-access execution contracts for AI agents.

Azure Service Bus Agentic Access

17 operations · 8 acting

AGENTIC

Use Cases 4

What developers build with this provider.

Application Decoupling

Decouple microservices and distributed applications using asynchronous messaging for independent scaling and deployment.

Load Leveling

Buffer incoming requests during traffic spikes to protect backend services from overload.

Event-Driven Architecture

Build event-driven systems using publish-subscribe topics to broadcast events to multiple subscribers.

Workflow Orchestration

Coordinate multi-step business processes using message sessions and scheduled delivery for reliable workflow execution.

Integrations 3

Pre-built integrations with other platforms and tools.

Azure Functions

Trigger serverless functions automatically when messages arrive in queues or topic subscriptions.

Azure Logic Apps

Build automated workflows that send and receive Service Bus messages with no-code connectors.

Azure Event Grid

Route Service Bus events to other Azure services for real-time event processing and monitoring.

Resources

Get Started 2

Portal, sign-up, and the first successful call

Portal

Portal

GettingStarted

GettingStarted

Documentation 2

Reference material describing how the API behaves

ContributionGuide

ContributionGuide

Documentation

Documentation

Agent Surfaces 2

MCP servers, agent skills, and machine-readable catalogs

AgenticAccess

AgenticAccess

LlmsText

LlmsText

Build 5

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

SDKs

CodeOfConduct

PostmanWorkspace

GitHubRepository

Access & Security 5

Authentication, authorization, and security posture

SecurityPolicy

SecurityPolicy

VulnerabilityDisclosure

VulnerabilityDisclosure

DomainSecurity

DomainSecurity

Authentication

Authentication

OAuthScopes

OAuthScopes

Operate 6

Status, limits, changes, and where to get help

RateLimits

StatusPage

Support

StackOverflow

IssueTracker

Releases

Commercial 6

Pricing, plans, and the legal terms of use

FinOps

Plans

TermsOfService

PrivacyPolicy

License

Pricing

Company 2

The organization behind the API

Website

Website

Blog

Blog

Other 1

Properties that don't map to a standard resource type

CapabilityMap

CapabilityMap

Source (apis.yml)

aid: azure-service-bus
name: Azure Service Bus
description: Azure Service Bus is a fully managed enterprise message broker with message queues and publish-subscribe topics,
  providing reliable message delivery for decoupling applications and services in cloud and hybrid environments.
type: Index
deliveryModel:
  model: open-core
  license: MIT
  open_source: true
  commercial: true
  callable_host: true
  label: Open core · an OSS project plus a commercial hosted product
  confidence: high
  source:
  - license
  - openapi
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: paid
  onboarding: self-serve
  trial: false
  try_now: false
  public: false
  gated: none
  gated_source:
  - onboarding
  label: Paid · Self-serve signup
  confidence: medium
  source:
  - plans
  - authentication
  - security
  generated: '2026-11-06'
  method: derived
position: Consuming
access: 3rd-Party
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/azure-service-bus.png
tags:
- Microsoft Azure
- Cloud
- Enterprise
- Message Broker
- Messaging
- Pub/Sub
- Queues
- Real-Time
tags_raw:
- Azure
- Cloud
- Enterprise
- Message Broker
- Messaging
- Pub/Sub
- Queues
- Real-Time
url: https://azure.microsoft.com/en-us/products/service-bus
created: '2026-03-26'
modified: '2026-05-19'
specificationVersion: '0.23'
apis:
- aid: azure-service-bus:azure-service-bus-namespaces-api
  name: Azure Service Bus Namespaces API
  description: Service Bus namespace operations
  humanURL: https://azure.microsoft.com/en-us/products/service-bus
  tags:
  - Namespaces
  properties:
  - type: OpenAPI
    url: openapi/azure-service-bus-namespaces-api-openapi.yml
  - type: AsyncAPI
    url: https://raw.githubusercontent.com/api-evangelist/azure-service-bus/refs/heads/main/asyncapi/azure-service-bus-asyncapi.yml
  - type: JSONSchema
    url: https://raw.githubusercontent.com/api-evangelist/azure-service-bus/refs/heads/main/json-schema/azure-service-bus-queue.yml
  - type: JSONLD
    url: https://raw.githubusercontent.com/api-evangelist/azure-service-bus/refs/heads/main/json-ld/azure-service-bus-context.jsonld
- aid: azure-service-bus:azure-service-bus-queues-api
  name: Azure Service Bus Queues API
  description: Service Bus queue operations
  humanURL: https://azure.microsoft.com/en-us/products/service-bus
  tags:
  - Queues
  properties:
  - type: OpenAPI
    url: openapi/azure-service-bus-queues-api-openapi.yml
  - type: AsyncAPI
    url: https://raw.githubusercontent.com/api-evangelist/azure-service-bus/refs/heads/main/asyncapi/azure-service-bus-asyncapi.yml
  - type: JSONSchema
    url: https://raw.githubusercontent.com/api-evangelist/azure-service-bus/refs/heads/main/json-schema/azure-service-bus-queue.yml
  - type: JSONLD
    url: https://raw.githubusercontent.com/api-evangelist/azure-service-bus/refs/heads/main/json-ld/azure-service-bus-context.jsonld
- aid: azure-service-bus:azure-service-bus-subscriptions-api
  name: Azure Service Bus Subscriptions API
  description: Service Bus topic subscription operations
  humanURL: https://azure.microsoft.com/en-us/products/service-bus
  tags:
  - Subscription
  tags_raw:
  - Subscriptions
  properties:
  - type: OpenAPI
    url: openapi/azure-service-bus-subscriptions-api-openapi.yml
  - type: AsyncAPI
    url: https://raw.githubusercontent.com/api-evangelist/azure-service-bus/refs/heads/main/asyncapi/azure-service-bus-asyncapi.yml
  - type: JSONSchema
    url: https://raw.githubusercontent.com/api-evangelist/azure-service-bus/refs/heads/main/json-schema/azure-service-bus-queue.yml
  - type: JSONLD
    url: https://raw.githubusercontent.com/api-evangelist/azure-service-bus/refs/heads/main/json-ld/azure-service-bus-context.jsonld
- aid: azure-service-bus:azure-service-bus-topics-api
  name: Azure Service Bus Topics API
  description: Service Bus topic operations
  humanURL: https://azure.microsoft.com/en-us/products/service-bus
  tags:
  - Topic
  tags_raw:
  - Topics
  properties:
  - type: OpenAPI
    url: openapi/azure-service-bus-topics-api-openapi.yml
  - type: AsyncAPI
    url: https://raw.githubusercontent.com/api-evangelist/azure-service-bus/refs/heads/main/asyncapi/azure-service-bus-asyncapi.yml
  - type: JSONSchema
    url: https://raw.githubusercontent.com/api-evangelist/azure-service-bus/refs/heads/main/json-schema/azure-service-bus-queue.yml
  - type: JSONLD
    url: https://raw.githubusercontent.com/api-evangelist/azure-service-bus/refs/heads/main/json-ld/azure-service-bus-context.jsonld
- aid: microsoft-azure-service-bus:management-api
  name: Azure Service Bus Management REST API
  description: The management REST API enables namespace, queue, topic, and subscription configuration through Azure Resource
    Manager, including SKU, network rules, authorization rules, and disaster recovery configuration.
  image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg
  humanURL: https://learn.microsoft.com/en-us/rest/api/servicebus/controlplane-stable/
  baseURL: https://management.azure.com/
  tags:
  - Management
  - Namespaces
  - Provisioning
  properties:
  - type: Documentation
    url: https://learn.microsoft.com/en-us/rest/api/servicebus/controlplane-stable/
  - type: Authentication
    url: https://learn.microsoft.com/en-us/azure/active-directory/develop/authentication-flows-app-scenarios
- aid: microsoft-azure-service-bus:microsoft-azure-service-bus-messages-api
  name: Azure Service Bus Messages API
  description: The Messages API from Azure Service Bus — 3 operation(s) for messages.
  humanURL: https://learn.microsoft.com/en-us/rest/api/servicebus/
  baseURL: https://{namespace}.servicebus.windows.net/
  tags:
  - Message
  tags_raw:
  - Messages
  properties:
  - type: OpenAPI
    url: openapi/azure-service-bus-messages-api-openapi.yml
  - type: Documentation
    url: https://learn.microsoft.com/en-us/rest/api/servicebus/
  - type: Authentication
    url: https://learn.microsoft.com/en-us/rest/api/eventhub/authenticate-shared-access-signature
  - type: Reference
    url: https://learn.microsoft.com/en-us/rest/api/servicebus/resourceprovider
common:
- type: RateLimits
  url: rate-limits/azure-service-bus-rate-limits.yml
- type: FinOps
  url: finops/azure-service-bus-finops.yml
- type: Plans
  url: plans/azure-service-bus-plans-pricing.yml
- type: GitHubOrganization
  url: https://github.com/Azure
- type: SDKs
  url: https://learn.microsoft.com/en-us/azure/service-bus-messaging/service-bus-dotnet-get-started-with-queues
- type: StatusPage
  url: https://azure.status.microsoft/en-us/status
- type: TermsOfService
  url: https://www.microsoft.com/en-us/legal/terms-of-use
- type: PrivacyPolicy
  url: https://privacy.microsoft.com/en-us/privacystatement
- type: Support
  url: https://support.microsoft.com/
- type: StackOverflow
  url: https://stackoverflow.com/questions/tagged/azureservicebus
- type: Website
  url: https://www.microsoft.com/
- type: CapabilityMap
  url: capabilities/azure-service-bus-capability-edges.yml
  name: Azure Service Bus Business Capability Map
- type: IssueTracker
  url: https://github.com/Azure/azure-sdk-for-net/issues
- type: Releases
  url: https://github.com/Azure/azure-sdk-for-net/releases
- type: SecurityPolicy
  url: https://github.com/Azure/azure-sdk-for-net/blob/main/SECURITY.md
- type: CodeOfConduct
  url: https://github.com/Azure/.github/blob/main/CODE_OF_CONDUCT.md
- type: ContributionGuide
  url: https://github.com/Azure/azure-sdk-for-net/blob/main/CONTRIBUTING.md
- type: License
  name: MIT
  url: https://github.com/Azure/azure-sdk-for-net/blob/main/LICENSE
- type: PostmanWorkspace
  url: https://www.postman.com/kinlaneapi/azure-service-bus/overview
- type: AgenticAccess
  url: agentic-access/azure-service-bus-agentic-access.yml
- type: VulnerabilityDisclosure
  url: security/azure-service-bus-vulnerability-disclosure.yml
- type: DomainSecurity
  url: security/azure-service-bus-domain-security.yml
- type: Authentication
  url: authentication/azure-service-bus-authentication.yml
- type: OAuthScopes
  url: scopes/azure-service-bus-scopes.yml
- type: Portal
  url: https://azure.microsoft.com/en-us/products/service-bus
- type: Documentation
  url: https://learn.microsoft.com/en-us/azure/service-bus-messaging/
- type: GettingStarted
  url: https://learn.microsoft.com/en-us/azure/service-bus-messaging/service-bus-quickstart-portal
- type: Pricing
  url: https://azure.microsoft.com/en-us/pricing/details/service-bus/
- type: GitHubRepository
  url: https://github.com/Azure/azure-sdk-for-net/tree/main/sdk/servicebus
- type: Blog
  url: https://azure.microsoft.com/en-us/blog/
- type: Features
  data:
  - name: Message Queues
    description: Point-to-point messaging with FIFO delivery, sessions, dead-lettering, and duplicate detection for reliable
      asynchronous communication.
  - name: Publish-Subscribe Topics
    description: One-to-many messaging with topic subscriptions, filters, and actions for event-driven architectures.
  - name: Dead-Letter Queue
    description: Automatic routing of undeliverable or failed messages to a secondary queue for inspection and reprocessing.
  - name: Scheduled Delivery
    description: Schedule messages for future delivery at a specified time without requiring sender availability.
  - name: Transactions
    description: ACID transaction support for grouping multiple operations across queues and topics into atomic units.
  - name: Auto-Forwarding
    description: Automatically forward messages from one queue or subscription to another entity for chaining processing stages.
- type: UseCases
  data:
  - name: Application Decoupling
    description: Decouple microservices and distributed applications using asynchronous messaging for independent scaling
      and deployment.
  - name: Load Leveling
    description: Buffer incoming requests during traffic spikes to protect backend services from overload.
  - name: Event-Driven Architecture
    description: Build event-driven systems using publish-subscribe topics to broadcast events to multiple subscribers.
  - name: Workflow Orchestration
    description: Coordinate multi-step business processes using message sessions and scheduled delivery for reliable workflow
      execution.
- type: Integrations
  data:
  - name: Azure Functions
    description: Trigger serverless functions automatically when messages arrive in queues or topic subscriptions.
  - name: Azure Logic Apps
    description: Build automated workflows that send and receive Service Bus messages with no-code connectors.
  - name: Azure Event Grid
    description: Route Service Bus events to other Azure services for real-time event processing and monitoring.
- type: LlmsText
  url: https://azure.microsoft.com/llms.txt
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
x-parent: microsoft-azure
x-relationship: product

Azure Service Bus API — frequently asked questions

Does Azure Service Bus have an API?

Yes. APIs.io lists 6 APIs from Azure Service Bus, including Azure Service Bus Namespaces API, Azure Service Bus Queues API and Azure Service Bus Subscriptions API, and 3 more.

Is there an OpenAPI specification for the Azure Service Bus API?

Yes. APIs.io indexes 5 OpenAPI specifications for Azure Service Bus, each linked for download from this page.

How do I authenticate with the Azure Service Bus API?

Azure Service Bus uses bearer-token authentication (oauth2 · 1 scheme). The details are profiled on APIs.io as Azure Service Bus Authentication.

How much does the Azure Service Bus API cost?

Azure Service Bus publishes its prices; its Premium Geo-Replication Zone 1 (North America and Europe) plan is $0.09/GB as of 2026-09-20. APIs.io lists 8 pricing plans for Azure Service Bus, with each plan's price, limits and inclusions under Pricing on this page.

Is the Azure Service Bus API ready for AI agents?

Azure Service Bus has a Kin Score of 68.0 out of 100 (exemplar) and an Agent Readiness score of 25.6 (agent-aware), scored by API Evangelist on 2026-11-06.

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/azure-service-bus"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/azure-service-bus/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/azure-service-bus/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.