Net.Azure.ServiceBusConsole 0.3.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

Note: Subscription IDs are currently hardcoded. See Configuration.

Features

• Browse Service Bus namespaces across multiple Azure subscriptions
• Queues and topics with live message counts (active, DLQ, scheduled, transfer) — animated spinner while refreshing from cache
• Filter queues, topics, and subscriptions by typing in the filter box
• Scrollable tables — arrow keys or scrollbar to navigate long lists
• Peek messages non-destructively (PeekLock) or receive/delete them (ReceiveAndDelete)
• Inspect message properties and body (auto pretty-printed if JSON) with a scrollable body panel
• Dead-letter queue browsing per queue and per subscription
• Requeue DLQ messages — fetch-lock a dead-lettered message, republish it to the origin queue/topic, and complete it in one step
• Delete individual queues, topics, subscriptions, or messages

Screenshots

Keyboard shortcuts

All screens

Connection screen

Queue list / Topic list / Subscription list

Queue browser / Subscription browser

Message detail

Prerequisites

• .NET 10 SDK
• Azure CLI logged in:

az login

Authentication uses AzureCliCredential — no connection strings or API keys are stored.

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.

Configuration

Azure subscription IDs are hardcoded in Pages/ConnectionPage.razor in the SubscriptionOptions array. Update these to match your environment before running from source.

How requeue works

When a message ends up in a dead-letter queue, F10 on the message list or message detail will:

1. Receive the message from the DLQ with PeekLock
2. Send an identical copy to the origin entity (queue or topic)
3. Complete (permanently remove) the original from the DLQ

The message is immediately removed from the list on success.

Releasing

Every push to main checks the <Version> in ServiceBusConsole.csproj. If a tag for that version doesn't exist yet, the publish workflow will automatically create the tag, pack, and push to NuGet.org.

To release a new version, bump the version in ServiceBusConsole.csproj and merge to main:

<Version>0.2.0</Version>

Requires a NUGET_API_KEY secret in the repository settings.

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