Send data tables to Microsoft Dataverse

Note

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

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.

Microsoft Azure must be configured for your Power Apps application, after which your Power Apps application must be added to the Microsoft Power Platform.

Get details

Review the following details before configuring credentials for Microsoft Dataverse and before configuring Amperity to send table rows that match a table schema to Microsoft Dataverse.

Credential settings Azure tenant ID Required The Microsoft Azure tenant ID for your instance of Microsoft Dataverse. Azure client ID and client secret Required A client ID and client secret for Microsoft Azure that has permission to access your instance of Microsoft Dataverse.

Required configuration settings Power Apps environment region Required The environment region for your Power Apps application. For example: “crm”. Power Apps environment name Required The environment name for your Power Apps application. For example: “socktown”. Dataverse table logical name Required at orchestration The table name in Microsoft Dataverse. This is the table to which the connector will write data. For example: “abc123_customers”.

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.

Configure credentials

Configure credentials for Microsoft Dataverse before adding a destination.

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

To configure credentials for Microsoft Dataverse

	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 Dataverse. 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 “microsoft-dataverse” credential type, configure settings, and then click Save. Azure tenant ID Required The Microsoft Azure tenant ID for your instance of Microsoft Dataverse. Azure client ID and client secret Required A client ID and client secret for Microsoft Azure that has permission to access your instance of Microsoft Dataverse.

Add destination

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

To add a destination for Microsoft Dataverse

	Open the Destinations page, and then click the Add destination button. To configure a destination for Microsoft Dataverse, do one of the following: Click the row in which Microsoft Dataverse is located. Destinations are listed alphabetically and you can scroll up and down the list. Search for Microsoft Dataverse. Start typing “micro”. The list will filter to show only matching destinations. Select “Microsoft Dataverse”.
	Select the credential for Microsoft Dataverse 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 Dataverse.
	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”. Power Apps environment region Required The environment region for your Power Apps application. For example: “crm”. Power Apps environment name Required The environment name for your Power Apps application. For example: “socktown”. Dataverse table logical name Required at orchestration The table name in Microsoft Dataverse. This is the table to which the connector will write data. For example: “abc123_customers”. Truncate table? Required at orchestration Select Truncate? to truncate the table before loading data.
	After this destination is configured, users may configure Amperity to use orchestrations to send query results Microsoft Dataverse.