Streaming & Messaging · Integration
Azure Service Bus
Add Azure Service Bus to your product for your customers, and give your AI agents governed access to it.
Embed an Azure Service Bus integration so your customers can send and consume messages on their own queues and topics from inside your product, with access scoped per tenant and every call audited. Sends are deduplicated per event where the entity supports it, so a retry does not enqueue duplicate work.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let customers send messages to their own queues or topics from your product.
Consume messages so your product reacts to their existing pipelines.
Read queue depth and dead-letter counts so backlogs are visible.
Trigger your product when a dead-letter entity receives a message.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent publishes a message within governed permissions.
An agent reads entity depth before deciding whether to act.
An agent reacts to a dead-lettered message and gathers the failure detail.
Example prompt
Show queues and topics with dead-lettered messages in the last hour and the count for each.
Set up Azure Service Bus in 4 steps
- 01Open the Azure Service Bus connector from your fastn dashboard.
- 02Have each customer authenticate their Service Bus namespace.
- 03Map the queues and topics your product uses, then enable actions and triggers.
- 04Call them from your product, or expose them to an agent through the MCP server.
Why teams use the Azure Service Bus integration
What you get by embedding it with fastn instead of building it yourself.
- Ship an Azure Service Bus integration without building it. Your customers connect their own Azure Service Bus account inside your product and work their topics, streams and messages there, with no per-customer code on your side.
- Handle the part that actually costs time: ordering and replay are the whole problem: a consumer that falls behind must be able to resume without losing or double-processing. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so an Azure Service Bus update is not your on-call problem.
- One integration serves your product and your agents. The same governed Azure Service Bus connection powers in-product features and gives AI agents scoped, audited access, so you move events between your product and your customers' systems without either side polling without wiring it twice.
Used by these teams
Compare with
AWS Simple Queue ServiceWorks well with
Azure MonitorOften used alongside
Tools the same teams tend to run next to Azure Service Bus, across other categories.
Snowflake
Airtable
PostgreSQL
Anthropic ClaudeAzure Service Bus integration FAQ
How do I add an Azure Service Bus integration to my product?
Enable the Azure Service Bus connector in your fastn dashboard, then let each customer authenticate their own Azure Service Bus account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Azure Service Bus client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Azure Service Bus account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Azure Service Bus account and only ever sees their own topics, streams and messages. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this Azure Service Bus integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent publishes a message within governed permissions.
Who maintains the Azure Service Bus integration?
fastn does. When Azure Service Bus changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Can my product replay Azure Service Bus messages after an outage?
Yes, within the retention the customer's own Azure Service Bus setup keeps. Consumer position is tracked per tenant, so a consumer that falls behind resumes from where it stopped rather than skipping ahead or starting over, which is the difference between a gap in your data and a duplicate in it.
How is one customer's stream kept separate from another's?
Each customer authorises their own Azure Service Bus connection, so topics, credentials and consumer positions are theirs alone. That matters more here than in most integrations, because a misrouted message is delivered before anyone can review it.
What can I build with the Azure Service Bus integration?
A common starting point: send messages to their own queues or topics from your product. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the Azure Service Bus integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Azure Service Bus does not change your per-connector cost. You can start free with 3 connected accounts.
Add Azure Service Bus to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.