Power BI Dataverse integration for Power Platform data
Power BI Dataverse integration connects the tables behind Power Apps and Dynamics 365 to a semantic model. Microsoft documents a Dataverse connector for this, and it supports both Import and DirectQuery. However, the connector relies on an environment setting called the TDS endpoint. So an administrator must enable that setting before the first query can run.
- Native connector
- TDS endpoint required
- Readable choice labels
Last updated
How does Power BI Dataverse integration connect to tables?
The Dataverse connector asks for the environment address and an organizational sign-in. It then shows the tables that the signed-in person may read. Because access follows Dataverse security roles, a report author sees no more than the platform allows.
Behind the scenes, the connector talks to Dataverse through a SQL-style endpoint. Microsoft calls it the TDS endpoint. Therefore the environment must have that feature switched on, and the network must allow its ports.
Import mode copies rows into the model on a schedule. DirectQuery leaves them in Dataverse and reads on demand. We usually start with Import, since it gives faster pages, and add DirectQuery only where freshness matters.
Dataverse details that surprise report builders
These three quirks explain most of the confusion in a first report.
Choice columns
A choice stores a number and shows a label. So the query must pick the label column, or charts fill with codes.
Lookups and owners
A lookup holds a key to another table. We model these as relationships instead of flattening every name into one wide table.
System columns
Every table carries many platform columns. We remove the ones no report needs, because a narrow table refreshes faster.
What happens when Dataverse tables get large?
The connector works well for everyday volumes. But very large tables can hit query limits or make refresh slow. In that case, reading the operational store directly stops being the best route.
Microsoft offers Azure Synapse Link for Dataverse for this situation. It exports table data to Azure Data Lake Storage and keeps it in step. Then Power BI reads the exported copy instead of the live environment.
We do not suggest that route on day one. Instead, we measure refresh times first and trim columns and rows. Often that is enough, and the simpler design stays easier for your team to run. For reports on the sales, service or finance apps built on these tables, see the Power BI Dynamics 365 integration page. The same model can feed a Power BI sales dashboard.
Setup checks for Power BI Dataverse integration
Your Power Platform administrator can confirm most of these in a few minutes.
- The TDS endpoint is on for the environment
- Report authors hold read roles on each table
- Refresh uses an account that will not expire
- Choice labels load, not only their codes
- Inactive rows have a clear filter rule
- Row-level rules in the model match business units
How we run a Power BI Dataverse integration project
Four stages, each closed with a demo, take you from tables to trusted reports.
Read the app
First we open the app with a user and learn which tables and columns carry the real process.
Fix the scope
Then the written quote names the tables, the measures and the pages. As a result, both sides know where the work ends.
Model and test
We build the model in your own tenant and test every role with real accounts before anyone relies on it.
Hand over
Finally, your makers get a walkthrough, so new columns in the app can reach the report without outside help.
Questions about Dataverse as a Power BI source
Is there a native Power BI connector for Dataverse?
Yes. Microsoft lists a Dataverse connector in the Power Query connector reference. It supports Import and DirectQuery for semantic models. The environment needs the TDS endpoint enabled, and the user needs read permission on the tables. Microsoft's page lists the current prerequisites, so we check it at the start of each project.
Does Power BI respect Dataverse security roles?
During authoring, yes, because the author signs in with their own account. But an imported model holds a copy of the rows. Therefore readers of the report see whatever the model allows. So we add row-level security in the model to mirror the rules that matter, and we test it per role.
Is Dataverse reporting the same as Dynamics 365 reporting?
Largely, since many Dynamics 365 apps store their data in Dataverse. The same connector reads both. However, each app adds its own tables and naming. We treat a sales app and a custom canvas app as different models, even when they share one environment.
Do we need a gateway for Dataverse?
Usually not. Dataverse is a cloud service, so the Power BI service reaches it directly in a standard setup. However, strict network policies can change that picture. We confirm the route with your administrator before scheduling refresh, and we note the result in the handover document.
How do we get started with Power BI Agency?
Book the free 30-minute assessment. One of our consultants reviews your environment and one report idea, and then says what the job involves. We are a division of Sataware Technologies, independent of Microsoft, working online. Also, we answer within 2 hours. The number is (480) 485-7373.
Let's build your first dashboard together.
Tell us what you report on today. A consultant replies within 2 hours with next steps.
Trusted partners
Microsoft Solutions Partner · AWS Partner
Cloud & AI Platforms
Azure SQL, Microsoft Fabric and the data pipelines behind your reports.
AI Business Solutions
Power BI reporting on your Dynamics 365, Business Central and Power Platform data.
Security
Row-level security and Entra ID sign-in on every report and workspace.
Amazon Web Services
Power BI on your AWS data, with connectors for Redshift, Athena and S3.