> ## Documentation Index
> Fetch the complete documentation index at: https://docs.sync.cdata.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Microsoft Dynamics 365

You can use the Microsoft Dynamics 365 connector from the CData Sync application to capture data
from Microsoft Dynamics 365 and move it to any supported destination. To do so, you need to add
the connector, authenticate to the connector, and complete your connection.

## Add the Microsoft Dynamics 365 Connector

To enable Sync to use data from Microsoft Dynamics 365, you first must add the
connector, as follows:

<ol>
  <li>Open the **Connections** page of the Sync dashboard.</li>
  <li>Click **Add Connection** to open the **Select Connectors** page.</li>
  <li>Click the **Sources** tab and locate
  the **Microsoft Dynamics 365** row.</li>

  <li>
    Click the **Configure Connection** icon at the end of that row to open
    the **New Connection** page. This action opens the
    **Add Connection** dialog.

    **Note:** If the **Configure Connection** icon is not
    available, click the **Download Connector** icon to install
    the Microsoft Dynamics 365 connector.
  </li>

  <li>Enter a name for your connection in the **Add Connection** dialog.</li>
  <li>Click **Add** to open the **Settings** tab for your connector.</li>
</ol>

For more information about installing new connectors, see
[Connections](https://docs.sync.cdata.com/26.4/en/connections/connections.md).

## Authenticate to Microsoft Dynamics 365

After you add the connector, you need to set the required properties.

**Organizational URL:** Enter the URL to your Microsoft Dynamics 365 organization (for example, [https://orgcb42e1d0.crm.dynamics.com](https://orgcb42e1d0.crm.dynamics.com)).

CData Sync supports authenticating to Microsoft Dynamics 365 in several ways. Select your authentication method below to proceed to the relevant section that contains the authentication details.

* [**AzureAD**](#azure-active-directory)
* [**AzureMSI**](#azure-managed-service-identity)
* [**AzureServicePrincipal**](#azure-service-principal)
* [**AzureServicePrincipalCert**](#azure-service-principal-certificate)

### Azure Active Directory

To connect with an Azure Active Directory (AD) user account, select **AzureAD**
for **Auth Scheme**. CData Sync provides an embedded OAuth application with
which to connect, so no additional properties are required.

### Azure Managed Service Identity

To leverage Azure Managed Service Identity (MSI) when CData Sync is running on an Azure
virtual machine, select **Azure MSI** for **Auth Scheme**. No
additional properties are required.

### Azure Service Principal

To connect with an Azure service principal and client secret, set the following properties:

<ul><li>**Auth Scheme:** Select **AzureServicePrincipal**.</li>
<li>**Azure Tenant:** Enter the Microsoft Online tenant to which you want to connect.</li>
<li>**OAuth Client Id:** Enter the client Id that you were assigned when you registered your application with an OAuth authorization server.</li>
<li>**OAuth Client Secret:** Enter the client secret that you were assigned when you registered your application with an OAuth authorization server.</li></ul>

To obtain the OAuth client Id and client secret for your application:

<ol><li>Log in to the [Azure portal](https://portal.azure.com).</li>
<li>In the left navigation pane, select **All services**. Then, search for and select **App registrations**.</li>
<li>Click **New registrations**.</li>
<li>Enter an application name and select **Any Azure AD Directory - Multi Tenant**.</li>
<li>After you create the application, copy the application (client) Id value that is displayed in the **Overview** section. Use this value as the OAuth client Id.</li>
<li>Navigate to the **Certificates & Secrets** section and select **New Client Secret** for the application.</li>
<li>Specify the duration and save the client secret. After you save it, the key value is displayed.</li>
<li>Copy this value because it is displayed only once. You will use this value as the OAuth client secret.</li>
<li>On the **Authentication** tab, make sure to select **Access tokens (used for implicit flows)**.</li></ol>

### Azure Service Principal Certificate

To connect with an Azure service principal and client certificate, set the following properties:

<ul><li>**Auth Scheme:** Select **AzureServicePrincipalCert**.</li>
<li>**Azure Tenant:** Enter the Microsoft Online tenant to which you want to connect.</li>
<li>**OAuth Client Id:** Enter the client Id that you were assigned when you registered your application with an OAuth authorization server.</li>
<li>**OAuth JWT Cert:** Enter your Java web tokens (JWT) certificate store.</li>
<li>**OAuth JWT Cert Type:** Enter the type of key store that contains your JWT Certificate. The default type is **PEMKEY\_BLOB**.</li>
<li>(Optional) **OAuth JWT Cert Password:** Enter the password for your OAuth JWT certificate.</li>
<li>(Optional) **OAuth JWT Cert Subject:** Enter the subject of your OAuth JWT certificate.</li></ul>

To obtain the OAuth certificate for your application:

<ol><li>Log in to the [Azure portal](https://portal.azure.com).</li>
<li>In the left navigation pane, select **All services**. Then, search for and select **App registrations**.</li>
<li>Click **New registrations**.</li>
<li>Enter an application name and select **Any Azure AD Directory - Multi Tenant**.</li>
<li>After you create the application, copy the application (client) Id value that is displayed in the **Overview** section. Use this value as the OAuth client Id.</li>
<li>Navigate to the **Certificates & Secrets** section and select **Upload certificate**. Then, select the certificate to upload from your local machine.</li>
<li>Specify the duration and save the client secret. After you save it, the key value is displayed.</li>
<li>Copy this value because it is displayed only once. You will use this value as the OAuth client secret.</li>
<li>On the **Authentication** tab, make sure to select **Access tokens (used for implicit flows)**.</li></ol>

## Complete Your Connection

To complete your connection:

1. For **Edition**, select the edition for your version of Microsoft Dynamics 365.

   * **CustomerService**
   * **FieldService**
   * **FinOpsOnline** (default)
   * **FinOpsOnPremise:** For this edition, you also must specify a value for **ADFS Server**. Enter the name of the server that you use to authenticate.
   * **HumanResources**
   * **Marketing**
   * **ProjectOperations**
   * **Sales**
   * **Commerce**

   > [!NOTE]
   >
   > The FinOpsOnline and FinOpsOnPremise editions apply to finance and operations as well as to supply-chain management.

2. Define advanced connection settings on the **Advanced** tab. (In most cases, though, you should not need these settings.)

3. If you authenticate with AzureAD, click **Connect to Microsoft Dynamics 365** to connect to your Microsoft Dynamics 365 account.

4. Click **Create & Test** to create your connection.

## Configure Change Tracking

For Microsoft Dynamics 365, you can set change tracking in [Microsoft Power Apps](https://make.powerapps.com/?utm_source=padocs\&utm_medium=linkinadoc\&utm_campaign=referralsfromdoc).

To set change tracking:

1. Open the Power Apps application and click **Tables**. Then, click the table for which you want to set change tracking.
2. Select **Properties > Advanced options**.
3. Scroll to the list under this paragraph: **Refine how data in this table is used and managed. Options marked with ¹ can't be turned off if enabled.**
4. Select **Track changes** to enable change tracking for your table.

   > [!WARNING]
   >
   > You cannot disable this option after you enable it (according to the paragraph shown in step 3) because the **Track changes** option is marked with the superscript (<sup>1</sup>).

   Change tracking is available only through the API for the CRM editions of Microsoft Dynamics 365. That means the **FinOpsOnline**, **FinOpsOnPremise**, and **HumanResources** editions do not support change tracking.

## More Information

For more information about interactions between CData Sync and Microsoft Dynamics 365, see
[Microsoft Dynamics 365 Connector for CData Sync](https://cdn.cdata.com/help/LJN/synch/default.htm).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.