Connect Campaign and Microsoft Dynamics 365

In this page, you will learn how to connect Campaign Classic to Microsoft Dynamics CRM 365.

Possible deployments are:

• via Web API (recommended). Refer to the section below to learn steps to set up the connection with Microsoft Dynamics.
• with Office 365. Refer to this video to learn key steps to set up this integration.
• for an On-premise deployment, apply Office 365 key steps.

Data synchronization is carried out via a dedicated workflow activity. Learn more.

Implementation steps

To connect Microsoft Dynamics 365 to work with Adobe Campaign via Web API, you need to apply the following steps:

In Microsoft Dynamics CRM:

1. Get Microsoft Dynamics Client ID
2. Generate Microsoft Dynamics Client Secret
3. Configure permissions
4. Create an App User
5. Encode the private key

Learn more in this section

In Campaign Classic:

1. Create a new external account
2. Configure the external account with Microsoft Dynamics settings
3. Use the configuration wizard to map tables and synchronize enumerations
4. Create the synchronization workflow

Learn more in this section

Configure Microsoft Dynamics CRM

To generate the access token and keys to setup the account, you need to login to Microsoft Azure Directory using a Global administrator credentials. Then follow the steps outlined below.

Get Microsoft Dynamics Client ID

To get the Client ID, you need to register an App in Azure Active Directory. Client ID is the same as Application ID.

1. Navigate to Azure Active Directory > App Registrations, and click New Application Registration.
2. Give a unique name which can help identify an instance, such as adobecampaign<instance identifier>.
3. Choose Application type as Web app / API.
4. Use http://localhost for Sign-on URL.

Once you save, you get an Application ID which is the Client Identifier for Campaign.

Learn more in this page.

Generate Microsoft Dynamics Client Secret

The client secret is the key which is unique to the Client ID. To get the certificate key identifier, follow the steps below:

1. Navigate to Azure Active Directory > App Registrations and select the Application which was created earlier.

2. Click on Certificates and Secret.

3. Click on Upload certificate and then browse and upload your public certificate generated.

4. To generate the certificate you can use openssl.

   For example:

   - openssl req -x509 -sha256 -nodes -days 365 -newkey rsa:2048 -keyout '<'private key name'>' -out '<'public certificate name'>
   

5. Click on the manifest link to get the certificate key identifier and the key ID.

Configure permissions

You need to configure the Required Permissions for the app that was created.

1. Navigate to Azure Active Directory > App Registrations and select the Application which was created earlier.
2. Click Settings on the top left.
3. On Required Permissions, click Add and Select an API > Dynamics CRM Online.
4. Then click Select, enable Access Dynamics 365 as organization users checkbox and click Select.

Create an App User

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

1. Click Azure Active Directory > Users and click New User.
2. Give a proper name that you want use and the username should be an email format.
3. Choose Dynamics 365 Administrator in the Directory Role.

Step 2: Assign a proper license to the created user

1. From Microsoft Azure, click on Admin app.
2. Go to Users > Active Users and click on the newly created user.
3. Click on Edit product licenses and select the Dynamics 365 Customer Engagement Plan.
4. Click Close.

Step 3: Create an application user on Dynamics CRM

1. From Microsoft Azure, navigate to Settings > Security > Users.

2. Click on drop down, select Application users and click New.

3. Use the same username as the user created on active directory above

   NOTE

   Using the same name throws duplicate key error, so until we get a confirmation as whether this step is needed, use a different username and proceed.

4. Assign the Application ID for the application you created earlier.

5. Click on Manage Roles and choose the System administrator role to the user.

Configure Campaign

To connect Microsoft Dynamics 365 and Campaign, you need to create and configure a dedicated External Account in Campaign.

1. Navigate to Administration > Platform > External accounts.

2. Create a new external account, select the type Microsoft Dynamics CRM and the Enable option.

3. Select the Web API deployment type:

   Adobe Campaign Classic supports the Dynamics 365 REST interface with OAuth protocol for authentication with a Certificate or Password Credentials.

   Use the settings defined previously in Azure Directory to configure the external account.

   

   NOTE

   Microsoft Dynamics CRM External account configuration is detailed in this section.

4. Click the Microsoft CRM configuration wizard… link: Adobe Campaign automatically detects the tables from the Microsoft Dynamics data template.

   

5. Select the tables to be recovered.

   

6. Click Next to start creating the corresponding schema.

   

   NOTE

   To approve the configuration, you must disconnect/reconnect to the Adobe Campaign console.

   You can check that the matching data schema becomes available in Adobe Campaign.

   

7. Click the Synchronizing enumerations… link to start synchronizing enumerations between Adobe Campaign and Microsoft Dynamics.

   

Campaign and Microsoft Dynamics are now connected. You can set up data synchronization between the two systems. Learn more in the Data synchronization section.

Configure Microsoft Dynamics CRM Office 365 integration

Watch this video to learn how to integrate Dynamics 365 with Adobe Campaign Classic, in the context of an Office 365 deployment.

Supported field data types

For Microsoft Dynamics 365 supported/unsupported attribute types are listed below: