- 12 minutes to read

Effortless Management for Azure Service Bus Queues

Experience seamless, secure, and automated management of your Microsoft Azure Service Bus with Nodinite. This page shows you how to monitor, manage, and automate message queues, topics, and subscriptions—without direct Azure Portal access. Discover how Nodinite empowers your team to streamline operations, boost security, and ensure compliance.

What you’ll gain with Nodinite for Azure Service Bus Queues:

✅ Proactive queue monitoring with real-time alerts
✅ Secure, role-based self-service remote actions—no direct Azure Portal access required
✅ Automated troubleshooting and message management
✅ Full audit logging for compliance and accountability
✅ Sessions support for remote actions on the active sub queue (Queues and Topic Subscriptions)

Take full control of your Microsoft Azure Service Bus with the Nodinite Message Queueing Monitoring Agent. This robust agent not only replaces Service Bus Explorer (both the open-source and Azure portal versions), but also elevates management, security, and automation—enabling systems integration experts to save time and achieve superior results faster.

Why Choose Nodinite?

Advanced Queue Management Without Azure Portal Access

Empower your team to view, manage, and resolve issues—without granting direct Azure Portal access. This approach reduces security risks by minimizing attack surfaces and limiting privileged access. Nodinite's RBAC-based Monitor Views ensure only authorized users have the right level of control.

Azure Service Bus Queue, Topic and Topic Subscription Resources as presented in a self-service enabled Nodinite Monitor View.

Comprehensive Monitoring & Proactive Alerts

Prevent message backlogs before they impact your business. Receive real-time alerts for:

Growing queue depths
Aging messages
Dead-lettered messages
Misconfigured forwarding
Misconfigured forwarding dead-letter to
Misconfigured or empty Topic Subscriptions
Disabled entities

Built-in Auditing for Compliance & Accountability

All sensitive operations in Nodinite are Audit Logged, ensuring full traceability—a must for regulated industries like finance, healthcare, and government. Eliminate the blame game and always know who did what, and when.

Feature-Rich Agent: Replace Service Bus Explorer with Nodinite

With the Nodinite Message Queueing Monitoring Agent, you gain unmatched control over Azure Service Bus queues, topics, and subscriptions:

Remote Actions & Message Management

Cancel scheduled messages
Delete messages (individual or selected)
Enable/Disable queue
Move active messages to the Dead-letter sub-queue
Purge Active and Dead letter sub queues
Repair individual messages
Resubmit Dead-lettered messages with "Resume" and "Resume & Delete" options

⚡ Threshold & Configuration Management

Set global or individual thresholds for age, count, and quota
Enable/Disable monitoring for queues, topics, and subscriptions

Message Retrieval & Processing

List messages
Download single messages or bulk messages as ZIP files
Post message to queues or topics, including advanced options
Move messages between sub queues (e.g., from Active to Dead-letter, and anti-clockwise)

Take Full Control of Your Azure Service Bus—Without the Hassle

With Nodinite, you can streamline operations, prevent downtime, and reduce manual work—all while ensuring compliance, security, and efficiency.

Upgrade your monitoring strategy today and leave Service Bus Explorer behind—experience faster troubleshooting, automated issue resolution, and effortless queue management with Nodinite!

Service Bus Queue Actions

There are several actions available for managing Azure Service Bus Queues. The actions are available from the Actions button on the selected queue in the Resources list view.

A User with access rights to a Monitor Views with the Resources of the Category 'Service Bus Queue' where Remote Actions are allowed can perform the Actions documented next.

Menu items from the Action button on selected queue

Details
Edit thresholds
Enable
Disable
Resubmit and Delete All Dead Letter Messages
List Active Messages
List Dead Letter Messages
List Scheduled Messages
Purge Messages (Active)
Purge Dead Letter

Service Bus Queue Details

💡View details about the Service Bus Queue.

Click the Details menu item in the Actions button to open a page with information about the Service Bus Queue:

Details menu item in the Actions button on selected queue.

Next, you will see a page with essential information about the selected Service Bus Queue.

Example with essential information about the selected Service Bus Queue.

At the bottom of the page, you will find the Thresholds section with the current thresholds for the selected queue.

Example with essential information about the selected Service Bus Queue thresholds.

Edit thresholds

💡Edit the Monitoring thresholds for the selected Service Bus Queue.

Use the Edit thresholds page to change the Monitoring thresholds. When untouched, the Monitoring is using the global settings which you can change using the Remote Configuration. You can override these individually for each queue.

You can modify the following properties:

Description - Brief Nodinite specific description of the queue.
Delete message on resubmit - When checked, delete the original message by default after a successful resubmit operation.
Allowed timespan - Evaluate the age of the first message on the queue. Warning and Error alerts are triggered based on the age of the first message on the queue.
Queue Count Evaluation Type:
- None - Count-based Monitoring is disabled.
- Fixed - Evaluate the Monitoring based on the number of messages on the queue.
- Percentage - Evaluate the Monitoring based on the current size vs the maximum allowed size of the queue.
- Comes First - Both the Fixed and Percent options are enabled and the Monitoring yields alerts on what happens first.

Click the Edit thresholds menu item in the Actions button on the selected queue to open the Edit Service Bus Queue Monitoring Thresholds modal.

Example of the 'Edit thresholds' menu item.

Here's an example modifying the Monitoring thresholds for the selected Service Bus queue.

If you see the following warning message it means that this queue is using global thresholds. When you click on the Save button you will start to use specific thresholds instead.

If you see this alert, the current configuration is using the Global configuration.

Click the Save button to persist changes.

Persist changes by clicking the Save button.

Queue Description

You can manage the Description field for the Nodinite Resource. This option provides you a way to add a "comment" for the specific queue.

Delete message on resubmit

When checked, delete the original message by default after a successful resubmit operation. The user can override this setting on individual resubmit operations.

Timespan evaluation

Allowed timespan - manage threshold for the maximum allowed age for the first message on the specific queue

State	Name	Data Type	Value Example	Description
	Warning TimeSpan	Timespan	00:05:00 (5 minutes)	The age of the first message on the queue to trigger Warning alert
	Error TimeSpan	Timespan	01:10:00 (1 hour 10 minutes)	The age of the first message on the queue to trigger Error alert

Queue Count Evaluation Type

There are four different types of count-based evaluations:

None - Count-based Monitoring is disabled.
Fixed - Evaluate the Monitoring based on the number of messages on the queue.
Percentage - Evaluate the Monitoring based on the current size vs the maximum allowed size of the queue.
Comes First - Both the Fixed and Percent options are enabled and the Monitoring yields alerts on what happens first.

Options for monitoring of queue based on numbers

None

When the Queue Count Evaluation Type is None, the number-based evaluation is disabled.

Fixed

With the Fixed option, monitoring is based on "fixed" numbers.

Percentage

With the Percent option, monitoring is based on quota.

Comes First

With the Comes First option, you can set thresholds for Fixed and Percent and both options will be monitored.

Number evaluation - Manage threshold for the maximum number of allowed messages

Name	Data Type	Value Example	Description
Warning Count	integer	>=0	The number of messages to go above on the queue to trigger Warning alert
Error Count	integer	>=0	The number of messages to go above on the queue to trigger Error alert
Warning Limit %	integer	1-100	Set the threshold quota value in percentage (1-100) for Warning alert
Error Limit %	integer	1-100	Set the threshold quota value in percentage (1-100) for error alert

Enable

💡Enable a Service Bus Queue that is in the Disabled state.

You can Enable a Service Bus Queue that is in the Disabled state. Click the Enable menu item in the Actions button on the Resource representing the queue. Example of the 'Enable' menu item in the Actions button on selected queue.

Next, you will be prompted with intent to continue with the operation. Click either Yes to proceed and No to abort the current operation.

Confirm intent to Enable Queue.

If the operation is successful, you will see a result resembling the following screen capture:
Example of the 'Enable operation succeeded' screen capture.

Disable

💡Disable a Service Bus Queue that is in the Enabled state.

You can Disable a Service Bus Queue that is in the Enabled state. Click the Disable menu item in the Actions button on the Resource representing the queue. Example of the 'Disable' menu item in the Actions button on selected queue.

Next, you will be prompted with intent to continue with the operation. Click either Yes to proceed and No to abort the current operation.

Confirm intent to Disable Queue.

If the operation is successful, you will see a result resembling the following screen capture:

Example of the 'Disable operation succeeded' screen capture.

List Dead Letter Messages

Click the List Dead Letter Messages menu item on the Action button for the selected queue to view a list of all dead letter messages on the selected Service Bus queue.
Example of the 'List Dead Letter Messages' menu item in the Actions button on selected queue.

Nodinite will then load a shared modal with a paged list view with the dead letter messages currently on the queue. The Dead Letter tab is now the active tab.
Sample list of dead letter messages on Service Bus queue.

You can reload the list by clicking on the Reload button or clicking the tab.

Manage Dead Letter Messages

From the Actions button you can further choose to manage the selected dead letter message. The following options are available:

Download (documented in a shared paragraph)
Delete
Resubmit

List Active Messages

Click the List Active Messages menu item on the Action button for the selected queue to view a list of all messages on the selected Service Bus queue.

Nodinite will then load a shared modal with a paged list view with the messages currently on the queue. The Active tab is now the active tab.

Sample list of messages on a Service Bus Queue.

You can reload the list by clicking on the Reload button.

Manage Active Messages

From the Actions button you can further choose to manage the selected active message. The following options are available:

Download (documented in a shared paragraph)
Delete

List Scheduled Messages

Click the Scheduled tab from within the "Manage messages ..." modal to get a paged list of all scheduled messages on the selected Service Bus queue.

Sample list of scheduled messages on Service Bus queue.

You can reload the list by clicking on the Reload button.

Manage Scheduled Messages

From the Actions button you can further choose to manage the selected scheduled message. The following options are available:

Download (documented in a shared paragraph)

Download Messages

You can download messages from the Service Bus queue. The messages are downloaded as either a single file with the content of the message body and or a zip file if you select several messages .

There are two alternatives for downloading messages from the queue:

Download single message (.out file)
Download selected messages (.zip file)

Regardless of which alternative you download from ('Active', 'Dead-letter' or 'Scheduled'), you can "globally" select which encoding to apply on the downloaded message(s) as file.

Select encoding for downloaded message.

1. Download single message

You can download a single message by clicking on the Action button and selecting Download.

You must 'allow browser pop-ups'

Click on download menu item to download message from queue.

2. Download selected messages

You can also download selected messages from the queue by clicking on the Download menu item in the 'With selected' button:

Download selected messages as zip button.

This operation may time out if you have a large amount of messages on the queue, use with caution.

Post message

From the Post tab, you can submit a new message to the selected target entity (Queue or Topic).

Post message tab with essential send options.

Send a message with the following properties:

Subject/Label
Message

You can modify additional properties, expand the Advanced accordion.

Target entity name - The name of the target entity (Queue or Topic)
Message ID - You can set a user-defined Message ID. Leave the field empty for the automatic creation of a unique Guid.
Correlation ID
Session ID
Reply to Session ID
Reply to
Dead letter source (read-only) - Name of the queue or subscription that this message was enqueued on, before it was dead-lettered.
Encoding
Content type
Time to live - Enter a time to live (TTL) in the format: days.hours.minutes.seconds, e.g., 0.00:00:30 for thirty seconds.
Scheduled enqueue time (local)

In addition, you can add any number of custom properties (Key-Value).

Message custom properties

Purge Messages (Active)

If you click on the 'Purge Messages' menu item of the Actions button you are presented with a confirmation dialogue:
![Purge Active Messages][25]

If the operation succeeds you are presented with this information and the number of messages that was removed.

Purge Dead Letter Messages

If you click on the 'Purge Dead Letter' menu item of the Actions button you are presented with a confirmation dialogue: