--- title: "Data import from Azure Service Bus queue or topic subscription" slug: "data-import-from-azure-service-bus-queue-or-topic-subscription" description: "Import data seamlessly from Azure Service Bus queues and topic subscriptions into D365 F&SCM using the Service Bus queue connector." tags: ["Concept", "Connectivity Studio", "CS"] status: "update" updated: 2026-10-05T12:14:01Z published: 2026-10-05T12:14:01Z canonical: "docs.staedean.com/data-import-from-azure-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. # Data import from Azure Service Bus queue or topic subscription You can use a connector of type '**Service Bus queue**' to import data from an Azure Service bus queue or topic subscription. ### Supported Service Bus entities The '**Service Bus queue**' connector supports these Service Bus entities: - **Queue**: Queues provide First In, First Out (FIFO) message delivery to one or more competing consumers. That is, receivers typically receive and process messages in the order in which they were added to the queue. And only one message consumer receives and processes each message. - **Topic and subscriptions**: Topics and subscriptions provide a one-to-many form of communication in a publish and subscribe pattern. It's useful for scaling to large numbers of recipients. Each published message is made available to each subscription registered with the topic. Publisher sends a message to a topic and one or more subscribers receive a copy of the message, depending on filter rules set on these subscriptions. For more information, refer to [Service Bus queues, topics, and subscriptions](https://learn.microsoft.com/en-us/azure/service-bus-messaging/service-bus-queues-topics-subscriptions). ### Service Bus search definitions To import data received from a Service Bus queue or topic subscription, you need an import message. Define dead-letter-specific Service Bus search definitions that are used to assign messages to the received data records. You can use these messages to import the received data into D365 F&SCM. ### Data import from Service Bus queue You can use the '**Service Bus queue**' connector to import data from a Service Bus queue. Make sure that for the connector the: - **Service Bus type** is '**Queue**'. - **Entity** field is filled with the name of the applicable Service Bus queue. To import data: 1. Run '**Receive data**' to receive data from a Service Bus queue. The received data is added to the **Received data (BisConSbReceivedData)** table in Connectivity Studio. On receiving data from the Service Bus queue, based on the Service Bus search definitions and settings on the received data, import messages are automatically assigned to the received data records. 2. Run import messages to read data from the **Received data (BisConSbReceivedData)** table and import this data into D365 F&SCM. The import messages must have the '**Service Bus queue**' connector as source connector. ![Diagram illustrating data import from Azure Service Bus to D365 F&SCM Connectivity studio.](https://cdn.document360.io/da662430-6a41-47b1-8c7e-7e4ac37a9756/Images/Documentation/AzureServiceBusQueue-Import.png) ### Data import from Service Bus topic subscription You can use the '**Service Bus queue**' connector to import data from a Service Bus topic subscription. Make sure that for the connector, the: - **Service Bus type** is '**Topic**' - **Entity** field is filled with the name of the applicable Service Bus topic. - **Subscription** field is filled with the name of the applicable Service Bus topic subscription. To import data: 1. Run '**Receive data**' to receive data from a Service Bus topic subscription. The received data is added to the **Received data (BisConSbReceivedData)** table in Connectivity Studio. On receiving data from the Service Bus topic subscription, based on the Service Bus search definitions and settings on the received data, import messages are automatically assigned to the received data records. 2. Run the assigned import messages to read data from the **Received data (BisConSbReceivedData)** table and import this data into D365 F&SCM. The import messages must have the '**Service Bus queue**' connector as source connector. ![Diagram illustrating data import from Azure Service Bus to D365 F&SCM Connectivity studio.](https://cdn.document360.io/da662430-6a41-47b1-8c7e-7e4ac37a9756/Images/Documentation/AzureServiceBusTopicSubscription-Import.png) ### Document The source document of the import message defines which data is imported from the '**Received data**' table and in which format and structure. With the '**Service Bus queue**' connector, you can use these external file-based documents: **EDI**, **Fixed text**, **Text**, **XML**, **JSON**. You can only use this connector in combination with a document for which the version 3 (V3) handler class is selected. ### Receive modes On receiving data from an Azure Service Bus queue or topic subscription, these [receive modes](https://docs.microsoft.com/en-us/azure/service-bus-messaging/service-bus-queues-topics-subscriptions#receive-modes) are supported: - Receive and delete - Peek lock If you use '**Peek lock**' when you run 'Receive data', the received messages are temporarily locked in the Service Bus queue or topic subscription. When the Connectivity Studio message that imports the data from the '**Received data**' table has run: - Successfully, the message is deleted from the queue or topic subscription. - With errors, the message is moved to the applicable Service Bus dead letter queue. ## Related - [Service Bus search definitions](/service-bus-search-definitions.md) - [Set up Service Bus queue connector](/set-up-service-bus-queue-connector.md) - [Monitor Service Bus data](/monitor-service-bus-data.md) - [Receive data from Service Bus queue or topic subscription](/receive-data-from-service-bus-queue-or-topic-subscription.md) - [Monitor data received from Service Bus queue or topic subscription](/monitor-data-received-from-service-bus-queue-or-topic-subscription.md) - [Import received Service Bus data](/import-received-service-bus-data.md) - [Set up Azure Service Bus namespace - Queue](/set-up-azure-service-bus-namespace-queue.md) - [Set up Azure Service Bus namespace - Topic and subscriptions](/set-up-azure-service-bus-namespace-topic-and-subscriptions.md) - [Data import from Azure Service Bus dead letter queue](/data-import-from-azure-service-bus-dead-letter-queue.md)