Send data to Microsoft Dataverse

Microsoft Dataverse is secure, cloud-based table storage for business applications, such as those belonging to the Microsoft Power Platform (Power BI, Power Apps, Power Automate, Power Virtual Agents, and Power Pages), Microsoft 365, Microsoft Azure, Dynamics 365, and other standalone applications.

This topic describes the steps that are required to send table rows that match a table schema to Microsoft Dataverse from Amperity:

1. Get details

2. Configure your Microsoft application

3. Add webhook destination

4. Add data template

How this destination works

Use Microsoft Dataverse to send rows of data from Amperity, and then add them to tables in Microsoft Dataverse. The connector will validate each row of data that is sent from Amperity against the table schema in Microsoft Dataverse. Only rows that validate against the table schema will be added to the table.

A Microsoft Dataverse destination works like this:

1. Use a query to build a table with rows of data that match the schema of a table in Microsoft Dataverse. The column names, data types, and column order must match the schema that is defined in Microsoft Dataverse.

2. Configure the Microsoft Dataverse destination in Amperity.

3. Validated table rows are sent to Microsoft Dataverse.

Get details

Amperity can be configured to send table rows that match a table schema to Microsoft Dataverse.

	Microsoft Azure must be configured for your Power Apps application, after which your Power Apps application must be added to the Microsoft Power Platform. You will need to provide your Azure tenant ID, Azure client ID, and your Azure client secret.
	The environment region, environment name, and logical table name for your Power Apps application. For example: “crm” (region), “acme” (name), and “abc123_acme” (table name).

Configure your Microsoft application

To send data to Microsoft Dataverse, you need to configure an application in Microsoft Azure to create the application and directory IDs and a client secret, after which you must add your application to the Microsoft Power Platform.

To configure your application in Microsoft Azure

1. Log in to your Microsoft Azure account.

2. Open Azure Active Directory, and then App Registrations.

3. Click New Registration, and then enter the name for your application. Leave all other settings as the default, and then click Register.

4. The application overview page contains the following IDs:

   Application (client) ID

   Directory (tenant) ID

5. From the left-side navigation, click Authentication, then Add a platform, and then Web.

6. On the next page, in the Redirect URI field, enter: https://app.amperity.com.

7. Under Implicit grant and hybrid flows, enable the Access tokens (used for implicit flows) option, and then click Configure.

8. From the left-side navigation, click Certificates & Secrets, select the Client secrets tab, and then click New client secret.

9. From the left-side navigation, click API Permissions, select Add a permission, select Dynamics CRM, select user_impersonation, and then click Add permissions.

To add your application to the Microsoft Power Platform

1. Open the Microsoft Power Platform console, click Environments, and then click on your environment.

2. Click Settings, then Users and permissions, and then Application users.

3. Click New app user, and then select the application you just created, your business unit, and then under Security roles click the Edit button.

4. Select the following settings:

   Service Reader

   Service Writer

   and then click Save.

5. Click Create.

Add destination

Configure Amperity to send table rows that match a table schema directly to Microsoft Dataverse.

To add a destination

	Open the Destinations tab to configure a destination for Microsoft Dataverse. Click the Add Destination button to open the Destination dialog box. Enter a name for the destination and provide a description. For example: “Microsoft Dataverse” and “This sends table rows that match a table schema to Microsoft Dataverse”. From the Plugin drop-down, start typing “micro” to filter the list, and then select Microsoft Dataverse.
	Credentials allow Amperity to connect to Microsoft Dataverse. The credential type is set automatically. You may use an existing credential or you may add a new one. Select an existing credential from the Credential drop-down. – or – Select Create a new credential from the Credential drop-down. This opens the Credential dialog box. Enter the name for the credential, and then add a description. Microsoft Dataverse has the following settings: Azure Active Directory tenant ID Azure client ID Azure client secret When finished, click Save.
	Each destination has settings that define how Amperity will deliver data to Microsoft Dataverse. These settings are listed under the Settings section of the Destination dialog box. The following settings are specific to Microsoft Dataverse: Setting Description Environment region The environment region for your Power Apps application. For example: “crm”. Environment name The environment name for your Power Apps application. For example: “acme”.
	Business users are assigned to the Amp360 User and/or AmpIQ User policies. (Amp360 User allows access to queries and orchestrations and AmpIQ User allows access to segments and campaigns.) A business user cannot select a destination that is not visible to them. Business users – including users assigned to the DataGrid Operator policy – may have restricted access to PII. What is restricted access to PII? 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. You can make this destination visible to orchestrations and allow users with restricted access to PII to use this destination by enabling one (or both) of the following options:
	Review all settings, and then click Save. Important You must configure a data template for this destination before you can send data to Microsoft Dataverse.

Add data template

A data template defines how columns in Amperity data structures are sent to downstream workflows. A data template is part of the configuration for sending query and segment results from Amperity to an external location.

To add a data template

	From the Destinations tab, open the menu for a destination that is configured for Microsoft Dataverse, and then select Add data template. This opens the Add Data Template dialog box. Enter the name of the data template and a description. For example: “Microsoft Dataverse” and “Send table rows that match a table schema to Microsoft Dataverse.”.
	Verify business user access to queries and orchestrations and access to segments and campaigns. A business user may also have restricted access to PII, which prevents them from viewing and sending customer profile data. If business user access was not configured as part of the destination, you may configure access from the data template.
	Verify all configuration settings. Note When the settings required by Microsoft Dataverse were are not configured as part of the destination, you must configure them as part of the data template before making this destination available to campaigns.
	Under Template Settings, verify all template settings and make any required updates. Dataverse Table Logical Name The table name in Microsoft Dataverse. This is the table to which the connector will write data. For example: “abc123_customers”. Important Select Truncate? to truncate the table before loading data.
	Review all settings, and then click Save. After you have saved the data template, and depending on how you configured it, business users can send query results to Microsoft Dataverse.