Microsoft Dataverse + clariBI
Connect Dataverse and Dynamics 365 through clariBI's MCP catalog. Read-only Entra ID OAuth on every table — standard Dynamics 365 Sales/Service entities, custom Power Apps tables, and the relationships between them — behind every analysis you run.
Native Microsoft Dataverse connector via the MCP catalog.
Connect with Entra ID OAuth on your Dataverse environment. The AI engine respects your existing Dataverse row-level security and table permissions — the same access your Power Apps users see. Microsoft 365 Copilot USL and Dynamics 365 Premium licenses cover Dynamics data access at no per-call Copilot Credit cost.
What is Microsoft Dataverse?
Microsoft Dataverse is the data layer behind Power Apps, Power Pages, Power Automate, Dynamics 365 Sales, Service, Customer Insights, and any custom business app a team has built on the Power Platform.
clariBI reaches your Dataverse environment through the official Microsoft Dataverse MCP server: list_tables, describe_table, read_query (SELECT-only — Dataverse rejects non-SELECT server-side), Search, and Fetch. Write tools (create_record, update_record, delete_record, schema mutations) are filtered out at the catalog layer and never reachable through clariBI.
Learn more at Microsoft Learn
Connect Microsoft Dataverse in three steps
Enable Dataverse MCP for your environment
A Power Platform administrator enables the MCP server and the allowed-clients list in the target environment. (Power Platform admin centre → Environments → MCP server.) Find your Dataverse organization name — it's the prefix in your URL (e.g. contoso.crm.dynamics.com → org name is contoso).
Paste the org name in clariBI
In clariBI Data Sources → MCP Servers, find Microsoft Dataverse, paste your org name, and click Connect. clariBI builds the endpoint as https://<org>.crm.dynamics.com/api/mcp.
Sign in with Entra ID, ask questions
Authorize on the Microsoft sign-in screen. clariBI inherits the row-level + column-level security of the connected account. Ask "Which Opportunities closed-won last quarter and what was the average close cycle?" or "How many Cases were resolved within SLA in November?" — the AI engine queries Dataverse alongside Stripe, HubSpot, and your other sources.
What you can analyze
Out of the box with the Microsoft Dataverse MCP connector:
- Dynamics 365 Sales: pipeline, win rate, close cycle, top accounts
- Dynamics 365 Service: case volume, SLA compliance, first-touch resolution
- Custom Power Apps tables and your team's bespoke business objects
- Account-level rollups across multiple Dataverse tables
- Cross-source: Dataverse Opportunities ↔ Stripe revenue ↔ support tickets
- Table-level health: row counts, recency, column completeness
Microsoft Dataverse is one of 60+ vendors in the clariBI MCP catalog. See the full list →
What the AI engine can call
Microsoft's Dataverse MCP exposes a deliberately small, SQL-centric surface. clariBI uses the five read-side tools; the row-mutation, schema-mutation, and delete tools are filtered out at the catalog layer.
| Tool | What the planner gets back |
|---|---|
list_tables | Every Dataverse table in the environment (Dynamics 365 entities + custom Power Apps tables). clariBI calls this first to ground analyses in real table names rather than guessing from D365 conventions. |
describe_table | T-SQL schema for a specified table including columns and types. Lets the planner pick valid column names before running a query. |
read_query | Executes a SELECT statement against Dataverse. Dataverse rejects non-SELECT statements server-side so this stays read-only by Microsoft's own validation. The primary tool for aggregations, filters, and joins. |
Search | Keyword search across records in Dataverse. Useful when you have an account name or a stub identifier and need to find the row. |
Fetch | Retrieves the full content of one record by entity name and ID. Drill-down tool for any record surfaced by read_query or Search. |
Excluded at the catalog layer (clariBI never reaches these): create_record, update_record, delete_record, Create Table, Update Table, Delete Table.
Cross-source questions Dataverse unlocks
Dataverse holds the same business objects (Accounts, Opportunities, Cases) that Power BI dashboards consume — but unlike a dashboard, clariBI can join them to anything else you've connected. Stripe revenue, Plain support tickets, Calendly meetings, the dbt Semantic Layer — all reachable from one question.
Dynamics 365 Sales × Stripe
"For closed-won Opportunities in Q3, what's the actual Stripe revenue and the gap vs estimated value?"
Planner: read_query on Dataverse Opportunity table (filter: StateCode=Won, ActualCloseDate in Q3) → join to Stripe customers by email → sum amount_paid in the same window → compute delta vs EstimatedValue.
Dynamics 365 Service × Plain
"Which accounts have open Dynamics Cases AND open Plain threads — and what's the combined SLA risk?"
Planner: read_query on Dataverse Cases (filter: status=open) → lookup_mcp_entities on Plain by account email → merge by account → rank by combined SLA breach risk.
Custom Power Apps × everything
"Pull our custom 'Customer Tier' field from the cs_customer table and re-tier every Stripe customer."
Planner: list_tables to find cs_customer → describe_table for the schema → read_query for tier + email → join to Stripe customers → surface re-tier candidates.
Microsoft Dataverse connector FAQ
Which licence do I need?
A Power Platform environment with the MCP server enabled (your Power Platform admin enables this). For Dynamics 365 access without per-call Copilot Credit billing, a Dynamics 365 Premium licence (Sales/Finance/Supply Chain/Service Premium) or Microsoft 365 Copilot User Subscription License (USL) covers the cost.
How does the row-level security work?
Entra ID OAuth ties the connection to a specific user. Dataverse applies the same row-level, column-level, and table-level security that user sees in Power Apps. clariBI can't see rows the user can't see — there's no service-account elevation.
Can clariBI create, update, or delete Dataverse records?
No. The Dataverse MCP exposes create_record, update_record, delete_record, and the corresponding schema-mutation tools, but clariBI's catalog filters them out. The planner only sees list_tables, describe_table, read_query, Search, and Fetch.
Why does the connect modal ask for an "org name"?
Each Dataverse environment has its own MCP endpoint at https://<org>.crm.dynamics.com/api/mcp. The org name is the subdomain prefix — find it as the first segment of any URL you use to reach your environment. clariBI substitutes it into the endpoint template at connect time.
Does this replace Power BI?
No. Power BI ships beautifully laid-out dashboards. clariBI handles the ad-hoc questions that the dashboards don't answer — usually because they touch data from another system (Stripe, HubSpot, Plain, dbt). Most teams run both: Power BI for the executive view, clariBI for the "yes, but actually…" follow-up.
Start your free trial and connect Dataverse in a minute
Entra ID OAuth, read-only, dashboards in seconds.
Start free trial