Send email lists to Microsoft Dynamics

Note

This topic contains information about configuring a destination that sends query results to Microsoft Dynamics using orchestrations. To configure a destination that sends audiences to Microsoft Dynamics using campaigns see this topic .

Microsoft Dynamics is a customer relationship management (CRM) software application that is focused on the supporting sales, marketing, and services. It is part of the Microsoft Dynamics family of business applications.

Note

This destination uses the Microsoft Dynamics Web API .

Get details

Review the following details before configuring credentials for Microsoft Dynamics and before configuring Amperity to send email lists to Microsoft Dynamics.

	Credential settings Client ID and client secret A client ID and client secret that has permission to access your instance of Microsoft Dynamics. The expiration date for the client secret must be set to “expires in 1 year”, “expires in 2 years”, or “never expires”.
	Required configuration settings Azure active directory ID The Active Directory tenant ID that is associated with your Microsoft Azure subscription. Dynamics URL The URL for your instance of Microsoft Dynamics. The URL must be the full URL, including https://. For example: https://<tenant-name>.crm.dynamics.com Dynamics entity (Required at orchestration) The entity type that defines the schema for data that is sent from Amperity. Operation (Required at orchestration) The operation to perform. Use “Upsert” to create or update records. Use “Delete” to remove all records. ID field (Required at orchestration) The field to use for upsert or delete operations.
	Microsoft Dynamics configuration An application user that is assigned to a role with an access level that allows that user to modify and update records. (Some use cases require a user to delete records.) Admin credentials for portal.azure.com (if the customer wants Amperity to configure Microsoft Dynamics on their behalf). Note A single tenant account type should be all that is required for Amperity to send data to Microsoft Dynamics.

Build Azure application

An application for Microsoft Dynamics must be created in Microsoft Azure. This is the location to which query data is sent by Amperity.

To build the Azure application

1. Go to portal.azure.com, and then log in with Admin credentials.

2. Open Azure Active Directory, and then click App registrations.

3. Click New Registration. The Register an application page opens.

4. Enter a name, such as “Amperity integration with Microsoft Dynamics”, specify the account type (single tenant should be fine), and then click Register. (You should leave the redirect URI setting blank.)

5. The application page opens. The client ID and Azure Active Directory ID are shown on the page.

   Important

   The Azure Active Directory ID is often referred to as the tenant ID.

6. On the application page, click Certificates & secrets, and then click New client secret.

7. Add a description for the secret, specify if the secret “expires in 1 year”, “expires in 2 years”, or “never expires”, and then click Add.

8. Copy the secret that is generated.

Add application user

An application user with permission to modify and update records is required.

Warning

Only one application user may be created for each Microsoft Dynamics client ID.

To add the application user

1. Go to the customer’s instance of Microsoft Dynamics, and then log in with Admin credentials. The URL for Microsoft Dynamics is similar to “<tenant-name>.crm.dynamics.com”.

2. Click Settings, then System, and then Security.

3. On the Security page, click Users, and then click Application Users.

4. Click New.

5. In the New User dialog box enter the user name, the application ID (which is the same as the Microsoft Dynamics client ID), full name, and primary email address.

   Note

   The URI for the application ID and the Azure Active Directory Object ID are both completed automatically.

6. Assign the user a role. Click Manage Roles, and then select a role with an access level that allows that user to modify and update records. (Some use cases require a user to delete records.)

Configure credentials

Configure credentials for Microsoft Dynamics before adding a destination.

An individual with access to Microsoft Dynamics should use SnapPass to securely share “client ID” and “client secret” details with the individual who will configure Amperity.

To configure credentials for Microsoft Dynamics

	From the Settings page, select the Credentials tab, and then click the Add credential button.
	In the Credentials settings dialog box, do the following: From the Plugin dropdown, select Microsoft Dynamics. Assign the credential a name and description that ensures other users of Amperity can recognize when to use this destination.
	The settings that are available for a credential are determined by the credential type. For the “dynamics” credential type, configure settings, and then click Save. Client ID and client secret A client ID and client secret that has permission to access your instance of Microsoft Dynamics.

Add destination

Use a sandbox to configure a destination for Microsoft Dynamics. Before promoting your changes, send a test audience, and then verify the the results in Microsoft Dynamics. After the end-to-end workflow has been verified, push the destination from the sandbox to production.

To add a destination for Microsoft Dynamics

	Open the Destinations page, and then click the Add destination button. To configure a destination for Microsoft Dynamics, do one of the following: Click the row in which Microsoft Dynamics is located. Destinations are listed alphabetically and you can scroll up and down the list. Search for Microsoft Dynamics. Start typing “micro”. The list will filter to show only matching destinations. Select “Microsoft Dynamics”.
	Select the credential for Microsoft Dynamics from the Credential drop-down, and then click Continue. Tip Click the “Test connection” link on the “Configure destination” page to verify that Amperity can connect to Microsoft Dynamics.
	In the “Destination settings” dialog box, assign the destination a name and description that ensures other users of Amperity can recognize when to use this destination. Configure business user access By default a destination is available to all users who have permission to view personally identifiable information (PII). Enable the Admin only checkbox to restrict access to only users assigned to the Datagrid Operator and Datagrid Administrator policies. Enable the PII setting checkbox to allow users with limited access to PII access to this destination. Restricted PII access is enabled when the Restrict PII access policy option that prevents users who are assigned to that option from viewing data that is marked as PII anywhere in Amperity and from sending that data to any downstream workflow.
	Configure the following settings, and then click “Save”. Azure active directory ID The Active Directory tenant ID that is associated with your Microsoft Azure subscription. Dynamics URL The URL for your instance of Microsoft Dynamics. The URL must be the full URL, including https://. For example: https://<tenant-name>.crm.dynamics.com Dynamics entity The entity type that defines the schema for data that is sent from Amperity.
	After this destination is configured, users may configure Amperity to use orchestrations to send query results Microsoft Dynamics.

Common Data Service Web API

Note

Microsoft Dynamics is a complex system. Even though Amperity has a built-in connector that supports sending data to entities within Microsoft Dynamics, there are more than 400 possible entities to which you can send data, such as sending segments to Dynamics 365 Marketing, with each of these entities having its own schema that requires a unique mapping of data in a data template.

The Common Data Service Web API (version 8.2 and higher or version 9.0) is the API to which Amperity can send data.

• Microsoft Dynamics is not strict about required fields, in that you may choose to not send fields to Microsoft Dynamics even when they are marked as required.

• Microsoft Dynamics is strict about extra fields, in that you should not send fields to Microsoft Dynamics that do not already exist in the entity’s schema. Use the include section in the data template mapping to drop fields that should not be sent to Microsoft Dynamics.

Review the entities in the Common Data Service Web API prior to configuring a data template. Some of the entities that are more focused toward marketing and user activity include Contact , List , Campaign , CampaignActivity , CampaignResponse , or CustomerAddress . Any of the entities found in the Web API EntityType Reference may be configured as a destination, depending on your use case.