---
title: "Receive data from Service Bus queue or topic subscription"
slug: "receive-data-from-service-bus-queue-or-topic-subscription"
description: "Import data from a Service Bus queue using the 'peek lock' feature in Connectivity Studio. Learn to manage messages efficiently with our guide."
tags: ["Task topic"]
updated: 2026-04-14T13:28:35Z
published: 2026-04-14T13:28:35Z
canonical: "docs.staedean.com/receive-data-from-service-bus-queue-or-topic-subscription"
---

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

# Receive data from Service Bus queue or topic subscription

You can use the '**Service Bus queue**' connector to import data from a **Service Bus queue**.

To import data, first receive the data from a **Service Bus queue** or topic subscription. The received data is added to the 'Received data from queue' table in Connectivity Studio.

On receiving data from the **Service Bus**:

- Based on the Service Bus search definitions and settings on the received data, import messages are automatically assigned to the received data records.
- You can use '**peek lock**'. If you use '**peek lock**', the received Service Bus messages are temporarily locked in the Service Bus queue or topic subscription.

### Steps

1. Go to **Connectivity studio > Inquiries** > **Service Bus queue > Received data**.
2. On the **Action Pane**, click **Operation**.
3. Click **Receive** **data**
4. Define the connector that is used to receive Service Bus data. The connector defines where to receive the data from:

In the **Source connector** field, enter or select a value.
  - Service Bus namespace
  - Queue or topic subscription
  - Authentication
5. On receiving data from an Azure Service Bus queue or topic subscription, these receive modes are supported:

If you use '**Peek lock**' when you receive Service Bus data, the received Service Bus messages are temporarily locked in the Service Bus queue or topic subscription.

Select **Yes** in the **Peek lock** field.
  - Receive and delete (**Peek lock** = **No**)
  - Peek lock (**Peek lock** = **Yes**)
6. Define the number of **Service Bus messages** to be read from the queue or topic subscription. If the number is '0', all messages are read from the queue or topic subscription.

In the **Number of messages** field, enter a number.
7. If you use '**peek lock**', define the number of hours after which the Service Bus messages are automatically unlocked on the queue or topic subscription. Define a number of hours during which Connectivity Studio usually must have processed the data. Resulting in the Service Bus message being:

In the **Reschedule message (hrs)** field, enter a number.
  - Removed from the queue or topic subscription (when processed successfully).
  - Moved to the Service Bus dead letter queue (when processed with errors).
8. Sub-task: Set recurrence.
  1. You can receive data from a Service queue or topic subscription in batch in a recurring pattern.

Expand the **Run in the background** section.
  2. Select **Yes** in the **Batch processing** field and fill in the other fields as desired.
  3. Click **Recurrence**.
  4. Fill in the recurrence settings as desired and click **OK**.
  5. Click **OK**.

> [!NOTE]
> **Notes**
> 
> You can also use the '**Receive and process data**' process. This process:
> 
> 1. Receives the data from the Service Bus queue or topic subscription.
> 2. Runs the messages that are automatically assigned to the received Service Bus data records.
> 
> You can indicate which data you want to receive:
> 
> - Queue or topic subscription data. If '**Yes**', you can also use the peek lock function.
> - Dead letter data. You cannot use the peek lock function for dead letter data.

## Related

- [Data import from Azure Service Bus queue or topic subscription](/data-import-from-azure-service-bus-queue-or-topic-subscription.md)
- [Service Bus search definitions](/service-bus-search-definitions.md)