---
title: "Service Bus Queue"
slug: "service-bus-queue"
updated: 2026-10-29T11:13:41Z
published: 2026-10-29T11:13:41Z
canonical: "docs.turbo360.com/service-bus-queue"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.turbo360.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Service Bus Queue

## Overview

**Azure Service Bus** is a cloud messaging service that connects applications, devices, and services running in the cloud or across devices, acting as a messaging backbone between them. You can associate a Service Bus Queue with a Turbo360 Business Application to view, process, and manage its messages.

### Business value

Turbo360 gives you visibility into Service Bus Queue messages that the Azure portal doesn't expose by default, letting your team query, filter, repair, and resubmit messages directly, reducing the need for custom tooling during incident response.

## How it works

Turbo360 lets you query messages in the Active-end or Dead-Letter queue, in **Peek** or **Deferred** state, using message count and sequence number to control where retrieval starts. Retrieved messages can be filtered by System and Custom properties, and by Dead-letter reason (including system-provided and custom error reasons). Filtering supports both JSON and text formats.

Deferred messages can be accessed anytime from the **Deferred Active Messages** and **Deferred Dead-Letter** tabs.

| Peek mode | Defer mode |
| --- | --- |
| Messages are peeked; active receivers of the active-end queue are unaffected. | Messages are deferred; active receivers of the active-end queue are affected. |
| Delivery count is not increased. | Delivery count is increased. |
| Delete operation is not available. | Delete operation is available. |

You can also run out-of-the-box queries on retrieved messages using system or custom properties.

              **Points to remember:**

              

- To access a deferred message in the Azure portal, you need its sequence number. Turbo360 gives you access to all deferred-state messages without needing the sequence number.

The options under the **Actions** button (Save, Resubmit, Repair & Resubmit) are disabled for messages larger than 1 MB. Messages larger than 10 MB can't access context menu options other than **resubmit** and **properties**.

## Permissions

| Permission | Description |
| --- | --- |
| Read | View, query, and filter messages in the active-end and dead-letter queue. |
| Manage | Update queue status and perform bulk status changes, in addition to all Read capabilities. |
| Reprocess | Resubmit messages from the active-end or dead-letter queue to the same queue, a different queue, a topic, or an API endpoint. |
| Repair & Reprocess | Repair message content (individually, or in bulk using Excel or JSON) and resubmit it. |
| Upload | Upload messages from an Excel workbook or process messages from stored JSON files into the queue. |
| Purge active messages | Backup and delete messages from the active-end queue. |
| Purge dead-letter messages | Backup and delete messages from the dead-letter queue. |

Purge is split into two separately grantable permissions, so you can allow a custom role to purge only active messages, only dead-letter messages, both, or neither. Consider the following when you grant them:

- To use **Messaging** > **Purge**, a role needs **Manage** on **Automated Task** and at least one of the two purge permissions.
- In the **Purge messages** blade, the **Active messages** and **Dead-letter messages** options are enabled based on the role's permissions. The option the role isn't allowed to use is disabled.
- In the **Process Service Bus dead-letter** automated task, the **Delete** and **Resubmit & Delete** operations require **Purge dead-letter messages**. **Resubmit & Delete** also requires **Reprocess**.
- If an existing custom role should purge dead-letter messages, open the role and check that **Purge dead-letter messages** is selected for the resource. A role that has only **Purge active messages** can't purge dead-letter messages.
- Users with the Owner or Contributor role on the Business Application aren't limited by these checkboxes.

## Operations

Manage Service Bus Queue messages directly from Turbo360 to avoid switching to the Azure portal during message troubleshooting, replay, or cleanup.

### Save a query filter

- **Save:** Saves the current filter query for reuse. Use this when you run the same message query regularly and want to avoid re-entering it.
- **Default query:** Sets a query to display automatically when retrieving messages in any mode.

Click **Save** next to the **Filter** option, or access saved queries from **Saved queries** at the top of the screen.

### Update status

Change the status of the Service Bus Queue resource by selecting one of the available options. Use this when you need to enable or disable the queue without going to the Azure portal.

1. Click **Update status** and select an option from the available list.

### Resubmit and repair messages

- **Resubmit:** Sends a single message or a bulk of messages from the active-end or dead-letter queue back to the same queue, a different queue, a topic, or an API endpoint. Use this when a message needs to be replayed after a transient failure.
- **Repair and Resubmit:** Repairs message content before resubmitting, individually or in bulk using an Excel sheet or JSON file. Use this when the message content itself caused the failure and needs correction before replay.

              **Avoid duplicate message loss**

              

Sending messages with the same message ID to a Service Bus resource with duplicate detection enabled causes the duplicates to be ignored. Turbo360 lets you regenerate the message ID manually or automatically while resubmitting.

Repairing an individual queue message:

Select the appropriate option from the **Actions** menu to repair and resubmit using Excel sheets or JSON files. Modify the downloaded file and upload it using the same blade.

### Export and upload messages

- **Export:** Saves selected messages as a single JSON file for portability or reuse across environments. Use this when you need to back up or migrate messages between queues.
- **Upload from Excel:** Uploads messages stored in an Excel workbook directly to the queue.
- **Process from stored JSON:** Uploads JSON files stored in a storage container to the queue.

Choose the desired messages and click **Actions -> Save** to export as JSON.

To upload from Excel:

1. Select the Excel workbook from your local device and validate the relevant worksheet.
2. Click **Next** to upload the messages to the queue.

To process stored JSON files:

1. From the **Messaging** menu, click **Process Message**.
2. Choose the storage blob container associated with the Business Application.
3. Locate and select the directory containing the relevant JSON files.
4. Click **Process** to begin uploading the messages.

### Backup and delete messages

- **Delete:** Removes messages from the active-end or dead-letter queue when retrieving in defer mode. Use this when stale or unneeded dead-letter messages need to be cleared.
- **Backup:** Saves messages safely to an associated **Storage Blob container** before processing them. Use this when you want a safety net before deleting or modifying messages.

### Inline task

- **Send messages:** Quickly sends messages to the queue using message count, Session ID/Partition Key, message body, user properties, and an optional saved configuration name. Use this when you need to test or replay messages immediately.
- **Purge messages:** Quickly purges messages from the active-end or dead-letter queue, using message count, queue type, enqueue time, and user properties. Use this when you need to clear queue backlog without a full automated task setup. You can purge only the message state your role allows: **Purge active messages** enables **Active messages**, and **Purge dead-letter messages** enables **Dead-letter messages**.

Task status can be viewed from **Automated tasks > Task history**.

              Note:

              

Navigate to the **Automated tasks** section in Turbo360 to create a task with a more detailed configuration, schedule tasks to run at a specific time, or automate the task to run on the specified hours, days, and more.

### Automated task

- **Schedule message processing:** sends or processes large volumes of active and dead-lettered messages without manual intervention. Use this when message volume is too high to manage manually, or you need consistent, scheduled processing.

### Bulk operations

- **Bulk status update:** Updates the status of multiple Service Bus Queue resources at once. Use this when applying the same status change across several queues, such as during planned maintenance.

## Resource dashboard

The dashboard gives you real-time visibility into message throughput and connection activity for the queue, helping you spot abnormal traffic patterns without querying messages directly.

| Widget | What it shows |
| --- | --- |
| Incoming Messages | Volume of messages entering the queue over time. |
| Outgoing Messages | Volume of messages leaving the queue over time. |
| Connections Opened vs Connections Closed | Connection churn for the queue, useful for spotting connection leaks or instability. |
| Overall Summary | High-level summary of queue activity. |

### Metrics

The Metrics tab surfaces message throughput and connection activity data for Service Bus Queue, giving you visibility into queue traffic trends over time. Use the Metrics tab to identify sustained spikes in incoming messages that may indicate backlog buildup, and to confirm that throughput returns to normal after dead-letter recovery or message purge operations.

You can add, remove, or reconfigure widgets to focus on the metrics most relevant to your support scenario.

## Monitoring

Service Bus Queue supports state and metric monitoring rules, configured from **Service Bus Queue -> Monitoring**.

              
              

Monitoring rules are saved for the Service Bus Queue, and the monitoring state for the metrics updates after every monitoring cycle.

### State monitoring

Tracks the queue's status against a configured threshold. Use this when you need to be alerted if the queue becomes unavailable or enters an unexpected state.

1. Configure the state rule under Status with the desired threshold.
2. Click **Save**.

### Metric monitoring

Tracks queue metrics such as message count or throughput against a configured threshold, violating the rule when the metric meets the configured value. Use this when you need early warning of queue backlog or unusual traffic before it impacts downstream consumers.

1. Select the necessary monitoring metrics and configure the threshold values.
2. Click **Save**.

## Troubleshooting

1. **Resubmitted message creates a duplicate instead of replacing the original** Cause: Duplicate detection is enabled on the Service Bus resource, and the resubmitted message reused the original message ID. Fix: Regenerate the message ID automatically or manually before resubmitting.
2. **Actions button options are disabled for selected messages** Cause: One or more selected messages exceed the 1 MB size limit for Save, Resubmit, and Repair & Resubmit. Fix: Deselect oversized messages, or process them individually using the available context menu options.
3. **Deferred message can't be located** Cause: The message sequence number wasn't provided, or the message isn't actually in deferred state. Fix: Use the **Deferred Active Messages** or **Deferred Dead-Letter** tab to browse deferred messages without needing the sequence number.
4. **Metric monitoring rule not reflecting the latest state** Cause: The monitoring state only updates after a full monitoring cycle completes. Fix: Wait for the next monitoring cycle, or verify the threshold configuration matches the intended metric.
5. **A custom role can't purge dead-letter messages** Cause: The role has **Purge active messages** but not **Purge dead-letter messages**. The **Dead-letter messages** option is disabled in the **Purge messages** blade, and **Delete** is disabled in the **Process Service Bus dead-letter** task. Fix: Edit the role and select **Purge dead-letter messages** for the Service Bus Queue resource.

## FAQs

1. **Can I give a role permission to purge only dead-letter messages?** Yes. Select **Purge dead-letter messages** and leave **Purge active messages** cleared. The role also needs **Manage** on **Automated Task** to use **Messaging** > **Purge**.
2. **How do I let a custom role purge both active and dead-letter messages?** Select both **Purge active messages** and **Purge dead-letter messages** for the resource. A role that has only one of them can purge only that message state.
3. **Does the separate purge permission apply to other resource types?** The two permissions apply to Service Bus Queue and Service Bus Topic Subscription. Other resource types that support purge keep a single **Purge** permission.

## Related articles

- [Service Bus Topic](https://docs.turbo360.com/docs/service-bus-topic)
- [Runbook](https://docs.turbo360.com/docs/runbook)
- [Resource Graph Query](https://docs.turbo360.com/docs/resource-graph)