KNOW WHAT'S STUCK IN YOUR SERVICE BUS.
Connect Azure Service Bus to Menza and ask what's happening in your queues, topics and subscriptions — where messages are piling up, what's landed in dead-letter, whether a queue is draining. Menza reads it live through the official Azure Service Bus API, and any message it sends or moves waits for your approval.
- Reads databases data
- Can take action on Azure Service Bus, once you approve
- Connects via the official API
What can Menza do with Azure Service Bus?
Deal with dead-letters, not dashboards
Menza spots messages accumulating in a dead-letter queue, shows you what they are, and proposes resubmitting the recoverable ones — once you approve, it sends them back through.
See queue depth at a glance
Ask which queues are backing up and Menza enumerates them with live message counts, so a consumer that quietly stopped shows up before your users notice anything.
Peek at messages safely
Ask what's actually sitting in a queue and Menza inspects messages without removing them, so you can diagnose a poison message from chat instead of writing a throwaway script.
See these answers on your own Azure Service Bus data.
Menza working with Azure Service Bus.
Menza doesn't just answer questions about Azure Service Bus — it proposes the fix and, once you approve, does the work. You stay in control; nothing changes until you say go.
Menzajust now240 messages have landed in the payments dead-letter queue since 02:00 — normal is under 5 a day. I'll resubmit the 236 that failed on the expired-lock error and leave the 4 malformed ones for review.
Menza6m agoA poison message is failing at the head of the orders queue, blocking roughly 1,100 messages behind it. I'll move the poison message to the dead-letter queue so the backlog drains, and keep it there for inspection.
Connect Azure Service Bus in a couple of clicks.
Is my Azure Service Bus data secure?
Your credentials are encrypted at rest and never exposed to the AI. Menza reads your data through the provider's official API using the access you grant, and you stay in control of what it can do — read-only by default, with any actions gated behind your approval.
Read our privacy policy- Encrypted in transit and at rest
- Scoped access — you choose what Menza can see
- Read-only by default; any action needs your approval
- Credentials are encrypted and never shown to the AI
- Revoke access at any time
Azure Service Bus questions, answered.
How does Menza connect to Azure Service Bus?
You connect with a Service Bus shared access key, pasted in once. It's encrypted at rest and never shown to the AI; Menza uses it server-side against your namespace through the official API — nothing to install, nothing to export.
What can Menza answer about my Azure Service Bus data?
Your queues, topics, subscriptions and the messages moving through them. Ask which queues have the deepest backlogs, what's sitting in a dead-letter queue, or what a stuck message actually contains — answered from the live namespace.
Is my Azure Service Bus data safe with Menza?
Yes. Your access key is encrypted, never exposed to the AI, and scoped to what you grant. Menza can act on messages, but any action — a send, a resubmit — waits for your explicit approval before anything moves.
Will Menza consume messages my applications need?
No. When inspecting, Menza browses messages rather than taking them off the queue, so your consumers see everything they would have anyway. Anything that does move a message — a resubmit, a send — is proposed first and waits for your approval.