Net.Azure.ServiceBusConsole 0.10.0

azure-servicebus-console

A terminal UI browser for Azure Service Bus — explore namespaces, queues, topics, and messages directly from your terminal.

Install

Requires .NET 10 SDK and an active Azure CLI login.

dotnet tool install -g Net.Azure.ServiceBusConsole
az login
azsb

To update to the latest version:

dotnet tool update -g Net.Azure.ServiceBusConsole

Features

• Lists the Azure subscriptions of your az login by name, hides the ones without Service Bus namespaces, and lets you filter them; the local emulator is always available
• Namespace details (resource group, location, SKU, status) on the connection page
• Switch subscription, namespace or section (Queues, Topics, All Subscriptions) from dropdowns in the header
• Queues, topics and subscriptions with live message counts (active, DLQ, scheduled, transfer): everything loads from a local cache first, then polls every 15 seconds; changed counts flash briefly
• Sort any list by clicking a column header (ascending, descending, off); the default sort (DLQ) shows in the header
• Filter queues, topics, subscriptions and Azure subscriptions by typing
• Color-coded counts and states: dead letters in red, zero counts dimmed, lock and browse modes highlighted
• Peek, receive (PeekLock) or receive-and-delete a chosen number of messages, like the Azure portal's Service Bus Explorer
• Multi-select messages (Space, click the checkbox, A all, I invert) and act on all of them at once
• Locked messages: complete, abandon, dead-letter or requeue; locks renew automatically and are released when you leave
• Split message browser: the list on top, a preview of the message under the cursor below (properties left, JSON-highlighted body right); Enter opens it full screen
• Dead-letter queue browsing per queue and per subscription; requeue dead-lettered messages to their origin
• Delete queues, topics or subscriptions; purge (dead-letter) queues
• Mouse support: buttons, rows, column headers, header dropdowns, wheel scrolling

Screenshots

Sample data from the test suite; regenerate with tools/update-screenshots.sh.

Connection: Azure subscriptions of your login, filter, namespace details

Queues: color-coded counts, sortable columns, type to filter

Live counts: lists poll every 15 seconds; a changed count flashes and fades

Header dropdowns: switch namespace (or subscription, or section) in place

Message browser: dead-letter reasons, delivery counts, multi-select, preview of the message under the cursor

Retry: confirm the flow, follow its progress, check the result

Message detail: properties and highlighted JSON body

All subscriptions across every topic

Keyboard shortcuts

All screens

Connection screen

Queue list / Topic list / Subscription list

Queue browser / Subscription browser

Actions apply to the selected messages, or to the focused one when nothing is selected.

Message detail

Prerequisites

• .NET 10 SDK
• Azure CLI logged in:

az login

Authentication uses AzureCliCredential — no connection strings or API keys are stored. The subscriptions you see are the ones your az login account can access.

Running from source

git clone --recurse-submodules https://github.com/zidad/azure-servicebus-console
cd azure-servicebus-console
az login
dotnet run

Logs are written to ./logs/session-<timestamp>.log on each run.

How message operations work

The browser follows the Service Bus Explorer in the Azure portal:

• Peek is read-only.
• Retry (dead-letter queue): peek, select the messages to retry, press F10. The selected messages are locked, sent to the origin queue (or the topic, for subscriptions: every subscription gets a copy) in order, then removed from the dead-letter queue. Service Bus can only lock from the front of a queue, so dead-lettered messages ahead of them are locked briefly and released; their delivery count goes up by one and they stay in the dead-letter queue. Already locked or received messages are retried the same way, without the extra lock step.
• Receive (PeekLock) locks the messages on a receiver that stays open. Locks are renewed in the background and abandoned when you leave the page or load something else, so messages come back right away instead of after lock expiry.
• Receive (ReceiveAndDelete) removes messages immediately; requeue them before leaving or they are gone.
• Resend (active queue, peeked) sends copies; the originals stay.

Bulk actions show a progress dialog (Esc cancels). When done it shows the result, including any failures, until you press Enter (OK); failed messages stay selected so you can retry. If nothing is left in the list, OK returns to the queue or subscription list.

Releasing

Push a version tag on a commit on main:

git tag v1.2.3 origin/main
git push origin v1.2.3

The publish workflow runs the tests, packs the tool with the tag's version, pushes it to NuGet.org and creates a GitHub release with generated notes and the package attached. There is no version number in the code.

Publishing uses NuGet trusted publishing — no API key secret is stored. The workflow exchanges a GitHub OIDC token for a short-lived nuget.org API key via NuGet/login.

This requires a trusted publishing policy on nuget.org (Account → Trusted Publishing) with:

Built with

• RazorConsole — Blazor Razor components rendered to the terminal via Spectre.Console
• Azure.Messaging.ServiceBus — Service Bus client
• Azure.ResourceManager.ServiceBus — namespace discovery via ARM