// the find
paolosalvatori/ServiceBusExplorer
The Service Bus Explorer allows users to connect to a Service Bus namespace and administer messaging entities in an easy manner. The tool provides advanced features like import/export functionality or the ability to test topic, queues, subscriptions, relay services, notification hubs and events hubs.
ServiceBusExplorer is a Windows GUI tool for managing Azure Service Bus, Event Hubs, Notification Hubs, Relay, and Event Grid. It fills a real gap — the Azure Portal's messaging management is genuinely bad, and this tool has been the standard alternative for over a decade. Target audience is .NET developers working on Azure messaging who need to inspect, send, and dead-letter messages without writing code.
The dead-letter management workflow is the standout feature — you can peek, repair, and resubmit DLQ messages in a few clicks, which would otherwise require custom code every time. The namespace import/export is genuinely useful for replicating environments or documenting configuration. Entra ID / AAD authentication was added properly, storing no credentials locally and using the standard MSAL browser flow. Available via Chocolatey, Scoop, and Winget — zero-friction install for Windows shops.
Still targets .NET Framework 4.6.2 and Windows Forms — this is a hard Windows-only dependency with no cross-platform story, which is a real problem on teams with mixed OS dev environments. Entra ID support is incomplete: managed identity, service principal, and sovereign cloud auth are all missing, so it doesn't work in a lot of enterprise setups. The codebase shows its age — ServiceBusHelper.cs is a god class with hundreds of methods, and they're mid-migration from the old WindowsAzure.ServiceBus SDK to the new Azure.Messaging.ServiceBus SDK, so both SDKs coexist. No active maintainers; the README explicitly says development is entirely voluntary, which is a real adoption risk for teams depending on it.