Activate your CRM data on cross-channel communication: learn how to pass on contacts from Microsoft Dynamics 365 to Adobe Campaign, and share campaign performance data (sends, opens, clicks, and bounces) back from Adobe Campaign to Microsoft Dynamics 365.
Once configuration is done, data synchronization between systems is carried out via a dedicated workflow activity. Learn more.
Supported Microsoft Dynamics versions are detailed in Campaign Compatibility matrix.
Follow the steps below to configure a dedicated external account to import and export Microsoft Dynamics 365 data into Adobe Campaign.
For each system, these steps need to be performed by an administrator.
Steps in this documentation will guide you through creating integrations/registrations that involve assigning permissions and/or admin access. It is your responsibility to ensure these steps comply with your company policies before performing, and to perform them carefully.
To connect Microsoft Dynamics 365 to work with Adobe Campaign via Web API, log on to Microsoft Azure Directory using a Global administrator credential, and follow the steps below:
To get the Application (client) ID, you need to register an App in Azure Active Directory.
Once you save, Microsoft Azure Directory assigns a unique Application (client) ID to your app. You will need this ID later on in configuring Dynamics 365 in Adobe Campaign.
Learn more in Microsoft Dynamics 365 documentation.
To get the Certificate key identifier (customKeyIdentifier) and the Key ID (keyId), you must upload a certificate. Certificates can be used as secrets to prove the application’s identity when requesting a token. Also can be referred to as public keys.
Follow the steps below:
The Certificate key identifier (customKeyIdentifier) and the Key ID (keyId) are needed in Campaign to configure your Microsoft Dynamics 365 CRM external account using the Certificate CRM O-Auth type.
To generate the certificate, you can use openssl.
- openssl req -x509 -sha256 -nodes -days 365 -newkey rsa:2048 -keyout '<'private key name'>' -out '<'public certificate name'>
You can change the number of days, here
-days 365, in the code sample for a longer certificate validity period.
You must then encode the certificate in base64. To do so, you can use the help of a Base64 encoder or use the command line
base64 -w0 private.key for Linux.
Step 1: Configure the Required Permissions for the app that was created.
trueand click Save.
Step 2: Grant admin consent
For more information on this, refer to Azure documentation.
This step is optional with Password credentials authentication.
The App user is the user that the application registered above will use. Any changes made to Microsoft Dynamics using the App registered above will be done via this user.
Step 1: Create a non-interactive user on azure active directory
Step 2: Assign a proper license to the created user
Step 3: Create an application user on Dynamics CRM
First, you must create the Microsoft Dynamics 365 external account.
Browse the Administration > Platform > External accounts node of the Campaign explorer and create an external account.
Select Microsoft Dynamics CRM external account in the Type section.
Select the authentication method in the CRM O-Auth type drop-down list.
To configure the Microsoft Dynamics CRM external account to connect with Adobe Campaign with Password Credentials, provide the following details:
To configure the Microsoft Dynamics CRM external account to connect with Adobe Campaign with a Certificate, provide the following details:
Select the Enable option to activate the account in Campaign.
To approve the setup, log off and back on to the Adobe Campaign Client Console.
You can now configure tables to synchronize.
Make sure to add to the allowlist two URLs: the server URL and
login.microsoftonline.com. To perform this, contact your Adobe representative.
Once the schema is created, you can synchronize enumerations automatically from Dynamics 365 to Adobe Campaign.
Adobe Campaign and Microsoft Dynamics 365 are now connected. You can set up data synchronization between the two systems.
To synchronize data between Adobe Campaign data and Microsoft CRM, create a workflow and use the CRM connector activity.
Learn more about data synchronization in this page.
For Microsoft Dynamics 365 supported/unsupported attribute types are listed below:
|Basic types : boolean, datetime, decimal, float, double, integer, bigint , string||Yes|
|Money (as double)||Yes|
|memo, entityname , primarykey, uniqueidentifier (as strings)||Yes|
|Status, picklist (we store the possible values in enumerations), state (string)||Yes|
|owner (as string)||Yes|
|Lookup (only single entity reference lookups)||Yes|