Integration with Microsoft Dynamics 365


Data about contacts and potential clients from Microsoft Dynamics 365 can be incorporated into Dialog Insight projects thanks to this integration. The goal of this feature is to retrieve contacts or prospects from your Dynamics platform for use in campaigns, segmentation, personalization, and the large variety of other features that the Dialog Insight platform provides. When a contact is added or modified in the third-party system, real-time data is added to the DI project. In a single project developed specifically for this integration, a first import is required to restore the initial state of Microsoft Dynamics 365 contact or prospect data. You can get a 360-degree view of your contacts and potential clients by creating a project structure similar to a single customer view (SCV). This structure's details are available here for your review. Be aware that no information is transmitted to the Microsoft Dynamics solution.

Initialization procedures

Before you can integrate your Dynamics 365 data into your project, there are three basic steps to fulfill: the configuration of an Azure Service Bus, the setup of the Dialog Insight plug-in within the Dynamics platform and the Dialog Insight project-level configurations.

1. Setting up an Azure Service Bus

The purpose of this system is to collect events into a waiting list so that the Dialog Insight system can recover them all at once.

Prior beginning

Owning a Portal Azure account (How to Create a Portal Azure Account)

Note:: It is strongly suggested that a member of your IT teammanage the Azure Service Bus. A certain level of technical knowledge is needed for this configuration. You are welcome to ask us for assistance in this process as well.


1.1 Sign in to your Azure Portal account.

1.2 Select Service Bus on the portal, by using the word "bus" in the search bar above.

1.3 If you do not yet have a Service Bus namespace, create one by going through steps 1.4 and 1.5; otherwise, choose the one you want and move on to step 1.6.

1.4 Select one of the two possibilities on the page that is displayed: Create a Service Bus namespace or + Create.

1.5 Configure Service Bus namespace.

  1. Choose the subscription type; 
  2. Select the resource group; 
  3. Enter the namespace name; 
  4. Select the location; 
  5. Choose the desired pricing.

1.6 Navigate to the resource's page. 

1.7 Create a new queue.

  1. Type a name. The name associated with the object that represents the data exchange. E.g., Contact. 
  2. Enter a maximum delivery count to specify how many times it will attempt to send the same message without success before giving up.

1.8 Create an access policy with Send rights for the Dynamics plugin once the new queue has been created.

  1. Go to the new queue page; 
  2. Select in the left menu Shared access policies
  3. Click on the + Add button to add a new access policy; 
  4. Type a name to the policy; 
  5. Check the Send box; 
  6. Click on Create

1.9 Create an access policy with Listen rights for the Dialog Insight platform.

  1. Go to the new queue page; 
  2. Select in the left menu Shared access policies
  3. Click on the + Add button to add a new access policy; 
  4. Type a name to the policy; 
  5. Check the Listen box; 
  6. Click on Create

1.10 Take note of the Primary Connection String field for the two access policies you just created. These will be used throughout the remaining steps.


You have a working and error-free instance of the Azure Service Bus.

2. Plugin Setup

This part of the integration gathers real-time modifications and additions to contacts and potential clients and sends them to an Azure Service Bus instance, where our service retrieves them and integrates them into the platform. 

Prior beginning 

Have access to the Microsoft Dynamics 365 account in the Plugin Registration Tool. 

Note: It is strongly recommended that a member of your IT team handle this configuration. 


2.1 Download and install the plugin using the instructions in the documentation.

2.2 Once the installation is completed, go to the Tools folder and then the PluginRegistration folder  

2.3 Launch the PluginRegistration app.

2.4 Click + CREATE NEW CONNECTION, then fill out your login details. 

2.5 Register the Azure Service Bus endpoint.

  1. Click on the Register tab;
  2. Select the Register new service endpoint option;
  3. Enter the Connection string retrieved in step 1.10 for the Listen access policy;
  4. Click the Next button;
  5. Make sure you have the correct Service Bus queue name;
  6. Validate that the Endpoint name is the one you want;
  7. Click the Save button.


The plug-in is correctly configured and error-free in the Microsoft Dynamics 365 environment.

3. Dialog Insight platform configuration

You can specify in which instance of the Azure Service Bus to retrieve the data and link the fields between Microsoft Dynamics 365 and DI using this integration component.

Prior beginning

Possess access to the targeted project's DI account.

Possess the connection string for the Azure Service Bus instance.


3.1 Select Configuration from the left-hand menu on the platform.

3.2 Select Project from the submenu that appears.

3.3 Select Advanced Setup from the top right corner.

3.4 Select Dynamics Connection from the new menu that appears.

3.5 Check the box to confirm that the project can use Microsoft Dynamics 365 as a data source. .

3.6 Complete the following: 

  1. Enter the Azure connection string created through the Azure Portal;
  2. Add a recipient who will receive alerts if a problem occurs with the system;
  3. Select a data source between Contact or Lead;
  4. Define the linking of DI fields and Dynamics 365 by indicating the primary key of the linked contact card and with the contact ID in Microsoft Dynamics 365. 

3.7 Enable integration from the data source


The addition or modification of data from Microsoft Dynamics 365 is added in the Dialog Insight project in real time, demonstrating active data integration, when the status of the contact source reads "active"

Did you find it helpful? Yes No

Send feedback
Sorry we couldn't be helpful. Help us improve this article with your feedback.