Microsoft Dataverse integration for construction data
Microsoft Dataverse connector for the Power Platform data layer. Supports entity reads, record creation, single-record lookup, and CRM action execution.
Authentication: OAuth 2.0 via Entra ID service principal
System type: DATAVERSE
Protocol: OData v9.2
API reference: Dataverse Web API
See your Dataverse records in Claude — book a 30-minute call.
Supported resources
Section titled “Supported resources”| Resource | FETCH | PUSH | LOOKUP | EXECUTE |
|---|---|---|---|---|
entities | ✓ Yes | — No | — No | — No |
records | ✓ Yes | ✓ Yes | ✓ Yes | — No |
actions | — No | — No | — No | ✓ Yes |
FETCH on entities lists available entity types. FETCH on records queries entity records with OData filters ($filter, $select, $top, $orderby). LOOKUP retrieves a single record by key. EXECUTE routes CRM actions via Microsoft.Dynamics.CRM.{action}.
Registers this connector fills
Microsoft Dataverse keeps 1 register current in Civil Memory. Each name is the record you ask for, not the system it came from - ask for it in Studio or from your own AI client.
| Register | What it holds | Fields from Microsoft Dataverse |
|---|---|---|
Document listdocument_list | Documents and files in your connected storage. Live, bound to connected storage, but with no published contract yet. | Fills all of 0 |
The full field list, requiredness and an example record for any register are on its published contract. Where more than one system fills a register, the register is the same shape either way.
Integration model
Section titled “Integration model”The adapter acquires an OAuth 2.0 client-credentials token from Entra ID and calls the Dataverse Web API at version v9.2. FETCH on records passes the OData query options through to the service, and LOOKUP resolves a single record by key.
Writes respect simulation mode - a dry run validates the payload without creating a record.
Connection setup
Section titled “Connection setup”Required values:
- Tenant ID
- Client ID - Entra app registration
- Client Secret
- Environment URL - your Dataverse environment URL (e.g.
https://yourorg.crm.dynamics.com)
Security
Section titled “Security”Access type: Read and approved write
Demiton reads entity records and can create records via approved workflows. CRM action execution also occurs only through approved workflows.
Permissions required: Service principal with Dataverse application user access scoped to the specific tables your workflows use. Do not grant system administrator privileges to the Demiton service principal.
Use a dedicated app registration for Demiton and rotate credentials on a regular schedule.
Next steps
Section titled “Next steps”- Connecting a System - step-by-step wizard for setting up the connector
- Business Central - the companion ERP connector for organisations on Dynamics 365
- MCP Server - query Dataverse entities through Claude once connected
- Connect your operation - talk to us about connecting it on Baseline
Talk to the team
Tell us what you run - your ERP, field, payroll and document systems - and we will show you the registers Demiton would fill from them, on your data, in a 30-minute call.