Set up Service Bus queue connector

Set up a connector of type 'Service Bus queue' to exchange information via an Azure Service bus queue or topic.

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.

Activities

Name	Responsible	Description
Set up Azure Service Bus namespace - Queue	Application Consultant	You can use a connector of type 'Service Bus queue' to exchange information via an Azure Service bus queue. A Service Bus queue provides 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. To set up an Azure Service Bus queue: Create a namespace in the Azure portal You need the Service Bus namespace name to fill in the Service Bus namespace field of the connector. Create a queue in the Azure portal You need the Service Bus queue name to fill in the Entity name field of the connector. Create Shared access signature (SAS) policy You can create and use a SAS policy on these levels: Service Bus queue or Service Bus namespace. You need the: SAS policy name to fill in the Policy name field of the connector. Primary key of the SAS policy to fill in the Policy key field of the connector. For more information, refer to: Service Bus queues, topics, and subscriptions Use Azure portal to create a Service Bus namespace and a queue Service Bus access control with Shared Access Signatures
Set up Azure Service Bus namespace - Topic and subscriptions	Application Consultant	You can use a connector of type 'Service Bus queue' to exchange information via an Azure Service bus topic and subscriptions. A topic 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. To set up an Azure Service Bus queue: Create a namespace in the Azure portal You need the Service Bus namespace name to fill in the Service Bus namespace field of the connector. Create a topic in the Azure portal You need the Service Bus topic name to fill in the Entity name field of the connector. Create subscriptions to the topic You need the Service Bus subscription name to fill in the Subscription field of the connector. Create Shared access signature (SAS) policy You can create and use a SAS policy on these levels: Service Bus topic (advised) or Service Bus namespace. You need the: SAS policy name to fill in the Policy name field of the connector. Primary key of the SAS policy to fill in the Policy key field of the connector. For more information, refer to: Service Bus queues, topics, and subscriptions Use the Azure portal to create a Service Bus topic and subscriptions to the topic Service Bus access control with Shared Access Signatures
Set up Service Bus queue connector	Application Consultant	Set up a connector of type 'Service Bus queue'. Use this connector type to exchange information via an Azure Service bus queue or topic. You can use the 'Service Bus queue' connector to: Export data: Use a Connectivity studio export message to send messages to the applicable Service Bus queue or Service Bus topic. The export message must have the 'Service Bus queue' connector as target connector. On export, each message that is sent to a queue or topic is logged in the 'Data sent to queue' history table. Import data: Run 'Receive queue data' to receive messages from a Service Bus queue or a Service Bus topic subscription. The received messages are added to the 'Received data from queue' table in Connectivity studio. These receive modes are supported: 'Receive and delete' and 'Peek lock'. Run import messages to read data from the 'Received data from queue' table and import this data into D365 FO. The import message must have the 'Service Bus queue' connector as source connector. The related document defines which data is sent to or received from a queue or topic and in which format and structure. So, the document does not result in a file. 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.
Set up Service Bus search definition	Application Consultant	You can use Service Bus search definitions to automatically assign Connectivity studio messages to received data records from a Service Bus.

Activities

Name	Responsible	Description
Set up Azure Service Bus namespace - Queue	Application Consultant	You can use a connector of type 'Service Bus queue' to exchange information via an Azure Service bus queue. A Service Bus queue provides 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. To set up an Azure Service Bus queue: Create a namespace in the Azure portal You need the Service Bus namespace name to fill in the Service Bus namespace field of the connector. Create a queue in the Azure portal You need the Service Bus queue name to fill in the Entity name field of the connector. Create Shared access signature (SAS) policy You can create and use a SAS policy on these levels: Service Bus queue or Service Bus namespace. You need the: SAS policy name to fill in the Policy name field of the connector. Primary key of the SAS policy to fill in the Policy key field of the connector. For more information, refer to: Service Bus queues, topics, and subscriptions Use Azure portal to create a Service Bus namespace and a queue Service Bus access control with Shared Access Signatures
Set up Azure Service Bus namespace - Topic and subscriptions	Application Consultant	You can use a connector of type 'Service Bus queue' to exchange information via an Azure Service bus topic and subscriptions. A topic 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. To set up an Azure Service Bus queue: Create a namespace in the Azure portal You need the Service Bus namespace name to fill in the Service Bus namespace field of the connector. Create a topic in the Azure portal You need the Service Bus topic name to fill in the Entity name field of the connector. Create subscriptions to the topic You need the Service Bus subscription name to fill in the Subscription field of the connector. Create Shared access signature (SAS) policy You can create and use a SAS policy on these levels: Service Bus topic (advised) or Service Bus namespace. You need the: SAS policy name to fill in the Policy name field of the connector. Primary key of the SAS policy to fill in the Policy key field of the connector. For more information, refer to: Service Bus queues, topics, and subscriptions Use the Azure portal to create a Service Bus topic and subscriptions to the topic Service Bus access control with Shared Access Signatures
Set up Service Bus queue connector	Application Consultant	Set up a connector of type 'Service Bus queue'. Use this connector type to exchange information via an Azure Service bus queue or topic. You can use the 'Service Bus queue' connector to: Export data: Use a Connectivity studio export message to send messages to the applicable Service Bus queue or Service Bus topic. The export message must have the 'Service Bus queue' connector as target connector. On export, each message that is sent to a queue or topic is logged in the 'Data sent to queue' history table. Import data: Run 'Receive queue data' to receive messages from a Service Bus queue or a Service Bus topic subscription. The received messages are added to the 'Received data from queue' table in Connectivity studio. These receive modes are supported: 'Receive and delete' and 'Peek lock'. Run import messages to read data from the 'Received data from queue' table and import this data into D365 FO. The import message must have the 'Service Bus queue' connector as source connector. The related document defines which data is sent to or received from a queue or topic and in which format and structure. So, the document does not result in a file. 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.
Set up Service Bus search definition	Application Consultant	You can use Service Bus search definitions to automatically assign Connectivity studio messages to received data records from a Service Bus.

See also

Provide feedback