Learn how to configure Microsoft Dynamics 365 integration and activate your CRM data on cross-channel communication with Adobe Campaign Standard.
The general description of the Adobe Campaign Standard integration with Microsoft Dynamics 365 is described in this page.
Multiple applications will need to be configured to enable the integration, however, this article will focus on steps required within Dynamics 365.
Before performing the pre-integration setup in this document, it is assumed that you have already provisioned and have admin access to your organization’s Microsoft Dynamics 365 instance. If this has not happened, then you will need to get in contact with Microsoft customer support to complete Dynamics 365 provisioning.
If you are configuring the integration for both staging and production environments, you will need to perform the steps below for both your staging and production Dynamics 365 instances. A few instructions below vary slightly depending if you are configuring a stage or production Dynamics 365 instance (e.g., for production instance, select “prod” for
<stage or prod>)
An OAuth access token allows the integration tool to authenticate with your Microsoft Dynamics 365 instance via web APIs in order to post Campaign Standard experience events to the timeline view of the Microsoft Dynamics 365 interface.
Main steps are outlined in the following video:
To generate the OAuth access token, follow the steps outlined below.
Under your administrator login, login to portal.azure.com.
Click on Azure Active Directory in the left side menu; then click App registrations on the sub menu that appears.
Click New registration at the top of screen.
Fill out the app registration screen:
<stage or prod>
For more information about creating a new application, refer to this section.
Microsoft Azure Directory assigns a unique application (client) ID to your app. You will need this ID later on in configuring Dynamics 365, as well as when you perform the integration tool setup.
From the app overview screen, on the sub menu on the left, click Certificates and Secrets > New client secret
Enter a description, set duration and click OK.
Your client secret is now created. Retain the value temporarily for the completion of the pre-integration setup of the integration tool.
Keep this value as you will need it to complete the integration tool pre-integration setup. It cannot be retrieved afterwards.
From this screen or the app overview screen, click on API permissions in the sub menu on the left. After clicking Add a permission, you need to select Dynamics CRM in the menu.
Then check the box for user_impersonation, and click the Add permissions button.
For more information about permission set up, refer to this section.
This new user is a generic user. It will be used by the application: any change to Microsoft Dynamics 365 using the API will be done by this user. To create it, follow the steps below:
Navigate to your Dynamics 365 instance and log in as Admin.
Click on the gear icon in the upper right corner and click on Advanced Settings. In the top banner, click on the drop down next to Settings, click on Security > Users.
Click on the drop-down menu go to Application Users. Click New.
Ensure drop down next to user icon says USER:APPLICATION USER.
Fill out the screen for the new user. Parameters suggestions:
<your-d365-hostname>" (e.g., email@example.com)
<stage or prod>
For more information about app user creation, refer to this section.
Click on the user icon and upload an Adobe Campaign icon; this is the icon that will be displayed in the Timeline view when new Adobe events appear in Dynamics 365.
Open the user roles list by clicking MANAGE ROLES in the top ribbon.
Scroll down and select System administrator access for this user.
Follow the instructions in this page to find your tenant ID. You’ll need this ID during pre-integration setup in the integration tool.
To integrate the Dynamics 365 App to your Campaign Standard environment, follow the steps below:
If at any time you wish to deactivate these processes, you can do so in this Processes screen.