For the complete documentation index, see llms.txt. This page is also available as Markdown.

Microsoft Dynamics 365 (Legacy)

Didomi allows you to update your Microsoft Dynamics 365 Contact attributes with the preferences collected through your Preference Management Platform (PMP).

Implementation

Connection

Didomi connects to Microsoft Dynamics Dataverse on your behalf through the following parameters:

  • Client ID

  • Client secret

  • Server instance

  • Azure tenant ID

Options

Upsert mode

You can choose allowing Didomi to create contact in Microsoft Dynamics 365, by setting upsert_mode to true. Otherwise, when a consent is collected but the organization_user_id value does not match with any contact in Microsoft Dynamics 365, the consent update will not be propagated.

Mapping

Didomi uses the entity contact of Microsoft's Dataverse and sends the contact attribute property when updating a contact. Hence consent events are mapped to Microsoft Dataverse's contact attributes.

Configuration

Property
Description
Required

Client ID

A client ID of the created Azure Enterprise application

Yes

Client secret

A client ID of the created Azure Enterprise application

Yes

Azure tenant ID

Tenant ID of your Azure app settings

Yes

Server Instance

Your REST API endpoint

Yes

Upsert mode

By setting upsert_mode to true you allow Didomi to create contacts in Microsoft Dynamics

No, Default value = false

Mappings

Mapping for properties between Didomi and Microsoft Dynamics Dataverse

Yes

Example

Last updated