Service Bus Dojo is a cross-platform client that helps developers manage, inspect, and debug Azure Service Bus resources with precision and speed. Service Bus Dojo puts a focused interface between you and sprawling toolchains so corporate teams can peek into queues and subscriptions, send test traffic, and reproduce integration issues without jumping through multiple portals. The app supports secure connections suitable for development, non-destructive message inspection, single-message and batch sending, and investigation features such as forwarding and resubmitting messages; a 7-day free trial is available to evaluate the workflow in your environment.

Key Features

The core is built for reliability and performance, using a Rust-powered backend to keep message operations responsive under heavy workloads. Secure connection management stores credentials locally and supports common authentication patterns so you can attach to namespaces and entities safely during development and testing. Message inspection is non-destructive by default: you can preview payloads and properties without dequeuing, toggle between formatted JSON, plain text and raw/hex views, and view system and custom properties side by side. Sending options include single-message dialogs for quick probes and batch operations when you need to reproduce volume scenarios. Advanced investigative actions such as forwarding, resubmitting to a chosen queue, and re-enqueuing dead-lettered messages are exposed through contextual controls to help you test recovery and retry logic.

Workflow and Controls

The interface is organized around workspaces and connections so you can switch between namespaces and projects quickly. Controls are designed for both mouse and keyboard users: context menus, inline editors and keyboard shortcuts let you navigate long message lists, open message inspectors, and perform bulk operations without leaving the keyboard. Drag-and-drop and clipboard support simplify injecting test payloads or exporting a message to a file. Filters and search allow you to narrow results by property, payload content, or time window, and sortable columns help you track message age, sequence number, and delivery count during diagnostics.

Progression and Productivity

Service Bus Dojo supports an iterative debugging workflow: save connection profiles, keep message templates for repeatable test traffic, and use named batches to re-run complex scenarios. Progression happens as teams build a library of templates, saved filters and checkpoints that capture a specific state of investigation. Audit-friendly logs record actions you take so you can reproduce steps later. Export and import of captured messages is supported to help you move test data between environments or feed fixtures into automated test suites. The app is intentionally focused on developer productivity rather than general-purpose management, which keeps common tasks fast and discoverable.

Customization, Accessibility, and Offline Use

Customization options let you tailor the interface to your preferences: choose between light and dark themes, adjust font sizes for readability, and enable a compact layout for dense message lists. Accessibility features include clear focus indicators and keyboard navigation to reduce reliance on precise pointer input. For intermittent network conditions you can work with previously captured or exported messages offline in a read-only mode to analyze payloads and properties; when connectivity returns, the client resumes live inspection. These accommodations are designed to make diagnostic work comfortable across different displays and usage contexts.

Who it’s for and limitations

This tool is intended for corporate developers, integration engineers, and QA teams who need to speed up troubleshooting across Azure Service Bus namespaces. Service Bus Dojo is not aimed at casual users; its feature set prioritizes depth and control over simplified consumer flows. Note that the free-tier connection support and the complimentary 7-day trial are intended for development and testing environments, not for production usage. If your workflows require high-availability production connectivity or enterprise-grade deployment policies, treat the trial and free-tier safeguards as evaluation aids rather than long-term production solutions.