Connect to Microsoft Dataverse

The Dataverse source enables changes to tables in Microsoft Dataverse to be mapped into graph nodes that can be referenced by a continuous query.

Source Requirements

App registration

The Dataverse source authenticates with Dataverse using OAuth, you must first register an application in your Microsoft Entra ID tenant.

Registering your application establishes a trust relationship between your app and the Microsoft identity platform. The trust is unidirectional: your app trusts the Microsoft identity platform, and not the other way around. Once created, the application object cannot be moved between different tenants.

Follow these steps to create the app registration:

1. Sign in to the Microsoft Entra admin center as at least a Cloud Application Administrator.

2. If you have access to multiple tenants, use the Settings icon in the top menu to switch to the tenant in which you want to register the application from the Directories + subscriptions menu.

3. Browse to Identity > Applications > App registrations and select New registration.

4. Enter a display Name for your application. Users of your application might see the display name when they use the app, for example during sign-in. You can change the display name at any time and multiple app registrations can share the same name. The app registration’s automatically generated Application (client) ID, not its display name, uniquely identifies your app within the identity platform.

5. Select Register to complete the initial app registration.

When registration finishes, the Microsoft Entra admin center displays the app registration’s Overview pane. You see the Application (client) ID. Also called the client ID, this value uniquely identifies your application in the Microsoft identity platform.

Next, you need to add credentials to the application. Credentials allow your application to authenticate as itself, requiring no interaction from a user at runtime.

1. In the Microsoft Entra admin center, in App registrations, select your application.
2. Select Certificates & secrets > Client secrets > New client secret.
3. Add a description for your client secret.
4. Select an expiration for the secret or specify a custom lifetime.
5. Select Add.
6. Record the secret’s value for use in your client application code. This secret value is never displayed again after you leave this page.

For more information see Use OAuth authentication with Microsoft Dataverse

Create and bind Dataverse user account to the registered app

The first thing you must do is create a custom security role that will define what access and privileges this account will have within the Dataverse organization. More information: Create or configure a custom security role

After you have created the custom security role, you must create the user account which will use it.

The procedure to create this user is different from creating a licensed user. Use the following steps:

1. Navigate to Settings > Security > Users

2. In the view drop-down, select Application Users.

3. Click New. Then verify that you are using the Application user form. If you do not see the Application ID, Application ID URI and Azure AD Object ID fields in the form, you must select the Application User form from the list.

4. Add the appropriate values to the fields:

   Field	Value
   User Name	A name for the user
   Application ID	The Application ID value for the application registered with Microsoft Entra ID.
   Full Name	The name of your application.
   Primary Email	The email address for the user.

5. Associate the application user with the custom security role you created.

More information: Manually create a Dataverse application user

Enable change tracking

For each table that you wish to observe, you need to enable Track Changes under the properties of that table in the Power Apps builder. Also, take note of the internal system name of the tables that you wish to observe.

Configuration Settings

kind: Source
apiVersion: v1
name: my-source
spec:
  kind: Dataverse
  properties:
    endpoint: https://xxxxx.api.crm4.dynamics.com/
    clientId: 00000000-0000-0000-000000000000
    secret: xxxxxx
    entities:
      - msdyn_customerasset

The following table describes the Dataverse specific properties: