bussinFeatures
Bussin is designed to get you in, let you do what you need with your Azure Service Bus, and get out. If you are used to the desktop Service Bus Explorer, most of the message-level workflow below will look familiar. Here is what you can do with it.
Browser-Native & No Installation
Bussin runs entirely in your browser as a static web application. There is no need to download binaries, configure local environments, or ask for administrator installation privileges. Just navigate to the site and connect. A desktop Service Bus Explorer needs Windows and a .NET Framework install before you can look at a single message; Bussin needs a browser tab. On a phone it switches to a simpler layout for checking queues and clearing dead-letter queues on the go.
Connection Strings & Entra ID SSO
Connect securely using Microsoft Entra ID (Azure AD) for single sign-on and namespace discovery. Alternatively, connect instantly using standard Azure Service Bus Connection Strings without signing in. This is especially useful for managing external, third-party, or partner Service Bus namespaces where you do not have Entra ID directory access.
Message Search and Peeking
Read active or dead-letter messages without locking or deleting them from the broker, oldest or newest first. You can search through thousands of messages using property and body pattern matching inside your browser's memory, or watch a queue, subscription or dead-letter queue and see new messages as they arrive.
Peek-Lock Settlement Support
Work with standard Service Bus lock states. Lock messages for inspection, then explicitly complete, abandon, or dead-letter them with full protocol compliance. Live countdowns display exactly when your locks will expire, and a single click renews the lease.
Session-Enabled Queue Support
Managing session-enabled FIFO queues and topic subscriptions can be complex. Unlike typical tools that force you to know and supply specific Session IDs in advance to even view messages, Bussin detects session-enabled entities automatically and allows you to peek messages across all active sessions directly. When executing bulk data operations (such as a full queue purge), Bussin automatically falls back to an optimized sequential session receiver loop that leases and drains next-available sessions one by one, clearing out message data safely and reliably.
Dead-Letter Queue Browsing & Recovery
Browse failed messages in the DLQ, read the failure reasons (like MaxDeliveryCountExceeded or TTLExpiredException), and resubmit them back to their active queue individually or in batches using background tasks.
Inline Message Editing & Resubmission
Need to fix a payload or modify message properties before re-submitting? Edit message bodies, adjust editable system headers (like Correlation ID, Content Type, or Session ID), and manage custom application properties directly in the UI. Choose to resubmit as a clone, or cleanly delete the original message from the queue or DLQ upon success.
JSON Export & Batch Uploads
Download selected messages, loaded messages, or up to 10,000 messages from the active or dead-letter queue as a structured JSON file. An interactive export modal lets you pick exactly which broker properties and custom application headers to include. The exported JSON fits the batch-upload schema, making it easy to import and send those messages back later with metadata intact.
Background Operations
Start long-running actions (such as moving large message backlogs or purging queues) in the background. The user interface remains responsive while background tasks track and show progress.
Scheduled Message Cancellation
Bussin fully supports identifying and managing scheduled messages. In addition to seeing scheduled message counts and inspecting their properties (like scheduled enqueue times), you can cancel scheduled messages directly from the UI. Select scheduled messages from the list or within the details modal to cancel them in batches or individually before they are enqueued, avoiding accidental double-processing or unwanted message delivery.
Subscription Filter Management
Inspect, add, and remove subscription filters (rules) directly from the browser interface. You can view all active SQL and correlation filters on any topic subscription, create new SQL filters to route specific messages, or define correlation filters based on message headers, giving you complete control over message routing rules directly inside the app, with built-in safety warnings to alert you of potential message loss before saving changes.
Namespace Organization
Organize multiple Service Bus namespaces into nested folders. Pin favorite namespaces across different Microsoft Entra ID directories to switch contexts in milliseconds, and give them names that make sense to your team. All configurations are saved locally in your browser.
Frequently Asked Questions
Which Service Bus Explorer features does Bussin cover?
Bussin covers the message-level half of what people use Service Bus Explorer for: peeking active and dead-letter messages, searching bodies and properties, peek-lock settlement, inline editing and resubmission, bulk purge and move, JSON export and batch upload, scheduled message cancellation, and subscription filter management. It does not cover entity administration, so creating or deleting queues and topics, editing entity properties, and managing authorization rules still belong in the Azure Portal or the desktop Service Bus Explorer. The comparison page lays out the split in detail.
Can I search message bodies, not just properties?
Yes. Bussin matches patterns against both the message body and broker or application properties. Search runs against the messages loaded into your browser's memory, so it never consumes anything from the broker and never sends your payloads anywhere. You can load thousands of messages and filter them without changing their delivery count.
Can I resubmit a dead-lettered message and delete the original in one step?
Yes, individually or across a whole selection. This is a common gap in other tools. The Azure Portal's resend operation sends a copy and Microsoft documents that the original stays in the dead-letter queue, so you have to purge or receive it separately. See the dead-letter queue guide for the full recovery workflow.
Does Bussin support session-enabled queues?
Yes, and without asking you for a Session ID first. Bussin detects session-enabled entities and peeks across all active sessions. For bulk operations such as a full purge, it falls back to a sequential session receiver loop that leases and drains next-available sessions one at a time.
Will peeking messages affect delivery counts or locks?
No. Peek is a read that does not lock or consume, so delivery counts stay where they are. Locking is a separate, explicit action: you lock a message when you intend to complete, abandon, or dead-letter it, and Bussin shows a live countdown to lock expiry with a one-click renew.
How many messages can I export at once?
Up to 10,000 from either the active or the dead-letter queue, or just your current selection. You choose which broker properties and custom application headers to include, and the resulting JSON matches Bussin's batch-upload schema, so you can send the same messages back later with their metadata intact.
Does the browser tab need to stay open during a bulk operation?
Yes. Long-running actions such as purging a large queue or moving a backlog run as background tasks that keep the UI responsive and report progress, but the work happens in your browser, so closing the tab ends the operation. Messages already settled stay settled.
Can I edit subscription filters from Bussin?
Yes. You can view every SQL and correlation filter on a topic subscription, add new ones, and remove existing ones. Bussin warns you before saving a change that could cause messages to stop matching a subscription.