Configure Microsoft Dynamics 365 (Current)
Available for: Preference Management Platform (PMP)
Access Type: Integrations Manage
Premium Feature: Microsoft Dynamic 365
In this article, we will cover how to configure the current version of the Didomi/Microsoft Dynamics 365 integration. The following steps can be utilized by organizations who are implementing Microsoft Dynamics 365 for the first time or are migrating their integration from the legacy version to the current version.
Prerequisites
Before continuing with the instructions included in this article, ensure that your organization meets the following criteria:
Didomi account with the Microsoft Dynamics 365 (Current) premium feature enabled
Preference Management Platform (PMP) configured in Didomi account
Microsoft Dataverse environment with Custom Insights - Journeys enabled
Configure Contact Point Consent table/entity (CPC)
Didomi pushes end-user preferences to the Contact Point Consent (msdynmkt_contactpointconsent) table/entity in Microsoft Dynamics 365. A distinct line item will be added to the Contact Point Consent table for each purpose and/or purpose the end-user submits along with their consent decision for that line item.
For example, if an end-user submits decisions on a purpose and three preferences via your privacy widget. The end-user would have four line items in the Contact Point Consent table.
Later when enabling the integration in the Didomi console, your organization will decide how different purposes and preferences will map to value options available in Microsoft Dynamics 365. Review the table below for more information on how purposes and preferences will be mapped:
Purpose
Purposes configured in your organization's Didomi account will target
the Purpose (msdynmkt_purpose) column of the Contact Point Consent table.
Mapping options for purposes will include any configured options for the column by msdynmkt_purposeId.
Preference
Preferences configured in your organization's Didomi account will target
the Topic (msdynmkt_topic) column of the Contact Point Consent table.
Mapping options for preferences will include any configured options for the column by msdynmkt_topicId.
In this section, we provide a brief overview on how to edit the available options in the Purpose and Topic columns in your Contact Point Consent table so that they are available during the mapping phase.
Note: There are multiple ways to edit the value options for the Purpose and Topic columns in Microsoft Dynamics 365. In this article, we will just focus on editing these columns via Power Apps.
From your organization's Power Apps account, click Tables on the left-hand panel.
Click the All tab on the subsequent page and use the provided search field to search for Purpose (msdynmkt_purpose).
Click the ellipsis inline with Purpose (msdynmkt_purpose) from the results and select Edit from the drop-down menu.
Click + New row and follow the instructions to add your organization's value options for purposes.
From your organization's Power Apps account, click Tables on the left-hand panel.
Click the All tab on the subsequent page and use the provided search field to search for Topic (msdynmkt_topic).
Click the ellipsis inline with Topic (msdynmkt_topic) from the results and select Edit from the drop-down menu.
Click + New row and follow the instructions to add your organization's value options for topics.
Retrieve Microsoft Dynamics 365 credentials
if migrating you can skip this step and use the credentials used to configure the legacy version
In order to successfully enable the Didomi/Microsoft Dynamics 365 integration your organization will need to retrieve the following credentials from your Microsoft account.
The following credentials can be retrieved from your organizations Microsoft Entra admin center
Azure tenant ID
Client ID
Client secret
In addition to the above credentials, your organization will also need to retrieve the URL for your:
Server instance.
Finding this value will depend on whether your organization deploys Microsoft Dynamics 365 using a cloud-based solution or on-premise deployment.
Enable Microsoft Dynamics 365 (Current) integration
Once the Contact Point Consent table/entity is properly configured and your organization's credentials are retrieved from Microsoft Dynamics 365, navigate to the Didomi console and click Integrations on the left-hand panel.
Click Manage.
Locate Microsoft Dynamics 365 on the subsequent page (it should not be labelled Legacy) and click the card.
If your organization does not find the card for the current Microsoft Dynamics 365 integration please contact your account manager.
Additionally, organizations who are migrating from Microsoft Dynamics 365 (Legacy) to Microsoft Dynamics 365 (Current) will find two cards for the integration. Ensure your organization selects the card not labelled Legacy,.
The configuration of the Microsoft Dynamics 365 (Current) integration is comprised of three steps:
Settings
In the Settings step of the integration configuration, use the provided fields to input your organization's retrieved Microsoft Dynamics 365 credentials.
Click Save settings when finished.
Options
In the Options step of the integration configuration, your organization can enable Upsert mode if desired. Upset mode authorizes Didomi to create new profiles when pushing end-user preferences to Microsoft Dynamics 365.
If Upsert mode is enabled, Didomi will check if the end-user’s organization_user_id (provided when the end-user submits their preferences) matches a msdynmkt_contactpointvalue in Microsoft Dynamics 365. If no match is found, Didomi will create a new user in Microsoft Dynamics 365 and push the organization_user_id to the msdynmkt_contactpointvalue field
Click Save options when finished.
Mapping
The Mapping step of the integration configuration will populate the purposes and any nested preferences configured for your organization. For any purpose or preference that should be pushed into the Contact Point Consent table, use the provided drop-down menu to select the appropriate mapping.
Review the table below for more information on how purposes and preferences map to your Microsoft Dynamics 365 (Current) configuration.
Purpose
Purposes configured in your organization's Didomi account will target
the Purpose (msdynmkt_purpose) column of the Contact Point Consent table.
Mapping options for purposes will include any configured attributes for the column by msdynmkt_purposeId.
Preference
Preferences configured in your organization's Didomi account will target
the Topic (msdynmkt_topic) column of the Contact Point Consent table.
Mapping options for preferences will include any configured attributes for the column by msdynmkt_topicId.
Select the drop-down menu inline with a purpose or preference and select the value options from the list. Repeat as necessary.
Click Save mapping when finished.
The Didomi/Microsoft Dynamics 365 (Current) integration is successfully enabled.
To test the integration, navigate to where the Didomi preference widget is deployed and submit your selections. Check Microsoft Dynamics 365 and ensure that your selections are reflected appropriately in the Contact Point Consent table.
Last updated