Skip to main content
Technical Preview

Overview

A client-mode connector for a curated eight-operation slice of the Dataverse Web API used by Dynamics 365 / Power Platform: WhoAmI, account CRUD helpers, contacts, and EntityDefinitions. It is meant for ERP/CRM edge bridges, not the full Dynamics surface. Set BASE_ADDRESS to the customer org URL (for example https://contoso.crm.dynamics.com, or .crm4.dynamics.com for many EU tenants).
Dataverse requires an Azure AD Bearer access token for the org resource. A placeholder org host does not resolve. Unauthenticated global discovery returns HTTP 400 without a tenant.

Basic Syntax

Events

List endpoints accept OData query options ($select, $filter, $top, $orderby) when you extend the ENDPOINT or append them in a custom variant.

Auth

Azure AD Bearer plus Dataverse OData headers:
string
required
Azure AD access token for the Dataverse org resource (audience = org URL). Obtain via client credentials or a delegated OAuth 2.0 flow. Prefer a Hub secret. Never commit the token.
string
Account GUID. Required on Getaccount and Updateaccount.
string
Contact GUID. Required on Getcontact.
High-level token flow (no secrets in the template):
  1. Register an Entra ID app with permission to the Dynamics / Dataverse API (or use an existing app registration).
  2. Acquire a token with client credentials (app-only) or a delegated user flow against the org resource URL.
  3. Publish the access token as api_token on the MQTT request payload (or inject from Hub secret upstream).
WhoAmI:
Get account:
Create account (connector body is {payload}; include name):

Try it

  1. Set BASE_ADDRESS to your org URL and add the connector on your broker.
  2. Publish token JSON to integrations/dynamics365/request/Whoami.
  3. Subscribe to integrations/dynamics365/response/Whoami.
  4. Accounts / contacts: include accountid or contactid as needed.
Last modified on October 25, 2026