Azure Service Bus
Queues, topics, subscriptions and their rules.
- Connect with
- Microsoft Entra ID, or a connection string encrypted on your PC
- Dead letters
- The dead-letter sub-queue
- Purge
- Everything, or a period
Free · Version 1.1 · Windows 10 and 11
Sign in with Microsoft Entra ID and open the namespaces and storage accounts you can see in Azure, with your roles and no key to copy. Browse queues, topics, blobs and tables, peek, search and replay messages, clean up dead letters, and run local Service Bus brokers on your PC. Free, with no account.
Sign in with your work or school account: Busrider finds the Service Bus namespaces and storage accounts you can see in Azure, with what your roles allow on each. Open one, or save several at once. No key to copy from the portal, none stored.
The first time, Microsoft asks you, or your organisation’s administrator, to allow Busrider. Connection strings and SAS URLs still work, side by side.
The same screens for each broker, one tab per connection. What a broker can’t do is left out, not faked.
Queues, topics, subscriptions and their rules.
The queues of a storage account, with Base64 bodies decoded.
Azure shows the first 32 visible messages without taking them. To read further, Busrider asks first, then receives them and gives them back: each counts one more read.
Queues, exchanges and bindings.
Reading a classic or quorum queue takes its messages for a moment, so Busrider asks before the first read. Streams are read in place.
Queues and topics, read over AMQP 1.0.
Addresses and their queues, read over AMQP 1.0.
Beta, as in the app: support for these brokers is new. Azure Service Bus is the one Busrider started with.
Find a blob anywhere in a storage account, by its name or by what it holds, and read it formatted right away. Blobs, tables and queues in one tab, with your environment’s rules.
Connect with Microsoft Entra ID, a connection string, a SAS URL or Azurite. Edits and deletes act on your real data: an environment set to Read only locks them.
Run an Azure Service Bus namespace on your PC, created from the start page: empty, copied from a saved connection, or from a definition file. Your app connects with a local connection string. No Docker, no Azure bill.
Free, with no account. Local brokers run on Busrider’s own emulator, made for development and tests: it is not Microsoft’s emulator, nor Azure.
All of it is free, on every broker, with no account.
Sign in with Microsoft Entra ID, or paste a connection string or a broker’s address, pin the connections you use most and connect in one click. Several at once, one tab each, even to different brokers. Keys and passwords are encrypted with your Windows account.
Queues and topics stream in with their counts. Read messages page by page, all at once or live; search ids, labels, bodies and properties, and filter by date.
Write a message with what its destination asks for, send it again or several times. Edit and resend one, or check several to resubmit, move to dead-letter, delete or export them.
Empty a queue or its dead letters, entirely or only the messages of a period where the broker dates them (on RabbitMQ, all ready messages; on Azure Queue Storage, the whole queue). Progress and Cancel in the status bar.
Create, edit, duplicate and delete queues, topics, subscriptions, exchanges and bindings, and subscription filters. Export a namespace’s configuration and import it into another.
A purge, a bulk action or a resend ends with a receipt: what was done, where, and the counts before and after, read again from the broker.
Waiting messages by the hour or by the day, with the oldest message and the busiest hour.
Tag connections PROD, DEV or an environment of your own, such as REC, with its colour on the tab. Each one sets what Busrider may change there: read only, messages, or messages and entities. On PROD, a purge, a delete, a resubmit or a move to dead-letter asks you to type the entity’s name first.
Turn on Settings › AI assistants, and Claude, Codex, Antigravity or another MCP client works with your brokers through Busrider. Off until you turn it on, and free.
Queues, topics and subscriptions with their counts, settings and rules, messages peeked or searched, dead letters grouped by reason. Each environment, and each connection, says whether assistants may read, ask for changes, or nothing.
Production connections stay locked until you unlock one, read-only, for 15 minutes, an hour or until Busrider closes, with or without message content.
A send, a resubmit, a delete or a purge an assistant asks for waits for your approval in Busrider, described from what Busrider read, not from the assistant’s words.
An assistant can create, start, stop and restart your local brokers and read their log. Emptying one waits for your approval; deleting one is left to you.
Assistants get connection names, never connection strings, keys or passwords. They reach Busrider on your PC only, with a key other Windows accounts can’t read.
Settings › AI assistants › Activity keeps each request for 30 days on your PC, without message content. Pause, or stop all AI access, in one click.
What an assistant reads goes to its provider’s AI service, under that provider’s terms: see the privacy policy.
Busrider talks straight to your brokers and to Azure. Nothing about them goes through us.
Read the privacy policyEncrypted with your Windows account. They never leave the app.
Done with Microsoft, in your browser. Busrider keeps its tokens on your PC, encrypted with your Windows account, and talks to Azure directly.
Only exchanged between the app and your brokers or storage accounts. An error report you send hides the names of your connections, queues and hosts, and your user names, unless you choose to show them.
Sent only from Feedback & roadmap, with a random number for this installation, and read only by us.
At start and every 6 hours, Busrider asks our server which versions are current. It sends only where it was installed from, with no identifier.
Feature counts and error codes, sent only if you agree: Busrider asks at first start. No cookie, no lasting identifier. Settings › Privacy has a switch for each.
Facts rather than labels: what is in place in version 1.1.
Busrider opens production namespaces and storage accounts, so its own security comes first.
Busrider is built to need almost nothing about you.
How a vulnerability is handled, and how its fix reaches you.
Found a vulnerability? Write to [email protected], and please keep it private until a fix is out. How we handle it.
From the Microsoft Store, or from a terminal with winget. Either way you get the Store version, and the Store keeps it up to date.
winget install --id 9NP026NQZQ2M
winget comes with Windows 11 and recent versions of Windows 10. It shows the Store’s terms once: type Y to accept them.
Yes. Busrider is free to download from the Microsoft Store and free to use, on every broker, with no account: signing in with Microsoft Entra ID, local brokers and AI assistants included.
Azure Service Bus (plus local Service Bus brokers on your PC), Azure Queue Storage, the blobs and tables of Azure Storage, RabbitMQ 4, ActiveMQ Classic and Apache Artemis, each connection in its own tab of the same window. The same screens work with every broker; what a broker can’t do is left out. Support for all but Service Bus is new: the app marks it Beta.
Yes, with a work or school account, for Azure Service Bus, Azure Queue Storage and Azure Storage. Microsoft’s sign-in opens in your browser; the first time, Microsoft asks you, or your organisation’s administrator, to allow Busrider. Busrider then lists the namespaces and storage accounts you can see, guest directories included, and greys what your roles don’t allow, with the role to ask for.
Yes. For Azure Service Bus, Busrider covers the everyday tasks of the classic Service Bus Explorer for Windows in a modern desktop app. Browsing sessions comes in a later version. It is an independent project, not affiliated with Microsoft.
Open its blob containers, tables and queues in one tab: search the blobs by name, path, text or regular expression, preview them, edit text blobs (saved only if nobody changed them meanwhile, with a snapshot of the version replaced if you ask), and query tables with their types.
Azure shows only the first 32 visible messages of a queue without taking them. To read further, Busrider receives them and gives them back: meanwhile they are hidden from their consumers, and each counts one more read (Azure Functions gives up on a message after 5, by default). So it asks first, and always on PROD.
RabbitMQ can’t show a classic or quorum queue without taking its messages for a moment: consumers don’t get them meanwhile, and they come back marked redelivered. Busrider asks before the first read. Streams are read in place.
An Azure Service Bus namespace that runs on your PC, created and started by Busrider for development and tests, empty or copied from your namespaces’ configuration. No Docker and no Azure bill. It runs on Busrider’s own emulator, not Microsoft’s: check your app against Azure before it goes live.
Open the Dead-letter tab of a queue or subscription to read the messages and why they were dead-lettered, resubmit the ones to retry, then purge the rest. On Azure Queue Storage, the queue Azure Functions moves a queue’s failed messages to is that queue’s Dead-letter tab.
They are encrypted with your Windows account and never leave your computer. With Microsoft Entra ID there is no key at all, and your sign-in is kept the same way. Busrider talks directly to your brokers and to Azure; nothing goes through our servers.
Only where you allow it, and each change waits for your approval in Busrider. AI assistants are off until you turn them on, PROD connections stay locked, and assistants never get your keys.
Busrider is built to need almost no personal data: no account, nothing from your brokers or Azure, and statistics only if you agree, with no lasting identifier. What the app sends is hosted in the EU. The privacy policy says what is kept, why and for how long; write to [email protected] to use your rights. Your brokers’ data stays yours: we never receive it, so we never process it on your behalf.
Windows 10 and 11 today. macOS and Linux versions are coming, with the same features.