# Microsoft Dynamics 365

{% hint style="success" %}
**Available for:** Preference Management Platform (PMP)

**Premium Feature:** Microsoft Dynamic 365
{% endhint %}

Microsoft Dynamics 365 is a cloud-based suite of enterprise applications that combines CRM and ERP capabilities to help businesses manage sales, customer service, finance, operations, and more. Didomi currently supports two versions of a Microsoft Dynamics 365 integration:

<table><thead><tr><th width="193.86669921875">Version</th><th>Description</th></tr></thead><tbody><tr><td><a href="/pages/Q7s5Qjzes67Ky9g441cw"><strong>Legacy</strong></a></td><td><p>The original version of the Microsoft Dynamics 365 integration whereby end-user preferences were managed directly on the Contact table/entity within Microsoft. Microsoft Dynamics 365 has since replaced this method with <a href="https://learn.microsoft.com/en-us/dynamics365/customer-insights/journeys/real-time-marketing-compliance-settings#compliance-profiles">Compliance Profiles</a> and <a href="https://learn.microsoft.com/en-us/dynamics365/developer/reference/entities/msdynmkt_contactpointconsent4">Contact Point Consent table/entity</a>.  </p><p></p><p></p><p><mark style="background-color:$warning;"><strong>Note</strong>: Currently, maintained for existing organizations that have implemented the Microsoft Dynamics 365 integration with Didomi. These organizations are strongly encouraged to</mark> <a href="#migration-to-microsoft-dynamics-365-current"><mark style="background-color:$warning;">update and migrate their integration</mark></a> <mark style="background-color:$warning;">to utilize the <strong>Current</strong> iteration of the Didomi/Microsoft Dynamics 365 integration.</mark></p></td></tr><tr><td><a href="/pages/A3gCOSfxogslxA8lIrHK"><strong>Current</strong></a></td><td><p>Leverages Microsoft Dynamics 365's current method of managing end-user preferences via <a href="https://learn.microsoft.com/en-us/dynamics365/customer-insights/journeys/real-time-marketing-compliance-settings#compliance-profiles">Compliance Profiles</a> and <a href="https://learn.microsoft.com/en-us/dynamics365/developer/reference/entities/msdynmkt_contactpointconsent4">Contact Point Consent table/entity</a>.  </p><p></p><p><mark style="background-color:$warning;"><strong>Note</strong>: Organizations implementing the Microsoft Dynamics 365 integration will implement this version of the integration by default.</mark></p></td></tr></tbody></table>

### Migration to Microsoft Dynamics 365 (Current)

For organizations who have implemented Microsoft Dynamics 365 (Legacy), Didomi strongly urges you to upgrade the integration to the most current version. In this section, we provide an overview of the migration process:

* [Contact table vs Contact Point Consent table](#contact-table-vs-contact-point-consent-table)
* [Historical records migration](#historical-records-migration)

#### Contact table vs Contact Point Consent table

A significant shift between the legacy and current version of Microsoft Dynamics 365 is how Microsoft organizes and stores end-user consent and preferences data. Review the table for more information:

<table><thead><tr><th width="136.066650390625">Version</th><th width="198.60009765625">MS Dynamics 365 Entity</th><th>Structure</th></tr></thead><tbody><tr><td>Legacy</td><td>Contact</td><td>End-user consent and preferences stored on the Contact entity/table with each purpose and preference stored as a separate column in a single row for the end-user.</td></tr><tr><td>Current</td><td>Contact Point Consent</td><td>End-user consent and preferences stored on the Contact Point Consent entity/table with each purpose and preference stored as distinct row.</td></tr></tbody></table>

#### Historical records migration

Didomi currently does not support a native way to automatically migrate your historical end-user preference records in Microsoft Dynamics 365 to the Contact Point Consent table/entity used in the current method.&#x20;

Please contact your Microsoft Dynamics 365 representative for more information and assistance.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.didomi.io/integrations/marketing-automation/microsoft-dynamics-365.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.