Configure an MS Dynamics integration

Who can use this feature?

A connection is an authentication mechanism to allow Totango to integrate with another system. Each connector has different requirements for connection. You can reuse connections to support multiple integration jobs. 

CRM integrations are a closed system; you cannot reuse CRM connections for other integration families. 

MS Dynamics configuration is based on OAuth credentials and requires a dedicated connected app configured in MS Dynamics.

1. Create an app in MS Dynamics

Creating a connected app in MS Dynamics is needed for creating an authentication endpoint. The new app informs MS Dynamics of this new authentication entry point and includes the relevant authentication configuration. 

  1. Sign in to the Azure portal using an account with administrator permission. You must use an account in the same Office 365 subscription (tenant) as you intend to register the app with. You can also access the Azure portal through the Office 365 Admin center by expanding the Admin centers item in the left navigation pane and selecting Azure Active Directory.
  2. Navigate to Azure Active Directory > App registrations.
  3. Click + New application registration.Azure App Registration
  4. In the Register an application page, enter your Totango app registration information:
    • In the Name section, enter a meaningful application name like "Totango main data sync".
    • Select "Accounts in any organizational directory" option from the supported account types section.
    • Keep the Redirect URI to https://app.totango.com/auth/connector/callback.
    • Click on Register to create the application.
      mceclip0.png
  5. On the app Overview page, hover over Application (client) ID value, and select the Copy to clipboard icon to copy the value. You'll need to specify this in your application's authentication code or app.config file where appropriate.mceclip2.png
  6. Select Manifest tab. In the manifest editor, set the allowPublicClient* property to true and click on Save button.
    mceclip3.png
  7. Select API permissions tab, and click on Add a permission.
    mceclip4.png
  8. Select Dynamics CRM under the Microsoft APIs tab.     
    mceclip5.png
  9. Click on Delegated permissions, select the user_impersonation option, and click Add permissions.
    mceclip1.png
  10. Select Certificates & secrets tab, click on New client secret. Add a meaningful description and select expires Never.

    Copy the client secret now to use later in the Totango connector. You will not be able to copy it later.

    mceclip6.png
    mceclip7.png

This completes the registration of your application in Azure Active Directory.

2. Create an application user

When your Azure app set up is complete, create an application user.

  1.  Navigate to your Dynamics 365 org > Settings > Security.
  2. Change the view to Application Users and then click +New.
  3. Make sure to change the form to “APPLICATION USER”, where you will only need to fill the “Application ID” field. Use the application ID you created from your Azure app in the previous steps.
  4. Once you create the app user, make sure to give it a custom Security role that has the access you want this user to have.

3. Create an MS Dynamics connector in Totango

In the event that your network is behind a firewall, you will need to whitelist our servers so that we may retrieve information from your data warehouse.

  1. In Totango, click Settings from the left nav.
  2. Expand Data Management > Customer Data Hub.
  3. From the list of active connectors (left), choose CRMs.
  4. From the list of available connectors, hover over MS Dynamics, and click Connect (or View Integrations).
    mceclip8.png
  5. Enter a name and description for the connection. Because you can have multiple connections with a connector (using different authentication profiles), a name and description helps you identify the connection later.
  6. Enter the connection details:
    • Client ID: Azure Active directory application ID
    • Client secret: Azure Active directory application secret (copied it in the previous steps). This is the value, not the Secret ID.
    • Organization domain: MS-Dynamics CRM domain. Should contain the full URL (https://{org_id}.crm.dynamics.com). See below.
    • Directory (tenant) id: Azure tenant ID
      mceclip9.png
  7. Click Test and Save Connection.
    mceclip10.png
  8. Enter your MS Dynamics credentials when prompted, unless you are already connected in a different tab of the browser (e.g., the OAuth configuration will take the credentials stored in your active browser session).

You can now set up an integration using the connection.

Filtering for MS Dynamics is done with OData filtering language.

Was this article helpful?

0 out of 0 found this helpful

Have more questions? Submit a request