Power BI Dynamics 365 integration built on Dataverse
Power BI Dynamics 365 integration connects the apps that run sales, service and finance to reports the whole company can read. Most Dynamics 365 apps keep their records in Microsoft Dataverse, so Power BI reads them through the Dataverse connector. Because both products come from Microsoft, sign-in and security line up well. Still, table choice and storage mode decide whether reports feel quick.
- Dataverse connector first
- Import or DirectQuery
- Security roles respected
Last updated
How does Power BI Dynamics 365 integration connect?
Sales, Customer Service and Field Service all store data in Dataverse. So the usual route is the Dataverse connector in Power BI Desktop. You pick an environment, then choose tables such as account, opportunity or incident.
The connector talks to a SQL-style endpoint that Dataverse exposes. An admin must switch that endpoint on in the environment settings first. After that, Power Query sees tables and columns much like a database. For the connector itself, including custom tables your makers add, see Power BI Dataverse integration.
Finance and Supply Chain Management work a little differently. Microsoft has deprecated their Export to Data Lake feature, which stops on November 30, 2026. Their data now reaches Power BI through Azure Synapse Link for Dataverse or Link to Microsoft Fabric. Business Central uses its own connector, covered under Power BI Business Central integration.
Dynamics 365 areas worth reporting on
Each app adds its own tables, and one model can combine several of them.
Sales pipeline
Opportunities, quotes and activities show what will close, while owner fields tie each deal to a seller.
Customer service
Case volume, first response and resolution time tell a service lead where the queue builds up.
Field service
Work orders and bookings reveal travel time and repeat visits, so planners can adjust routes.
Finance figures
Ledger and budget data sit beside the pipeline, which lets a CFO compare forecast with booked revenue.
Marketing journeys
Lead sources and campaign responses then link to won deals through the contact and account tables.
Custom tables
Anything your makers built in Dataverse also appears in the connector with its own columns and choices.
Should a Dynamics 365 model use import or DirectQuery?
The Dataverse connector supports both modes. Import copies data into the model, so visuals answer fast and DAX has full freedom. However, numbers are only as fresh as the last refresh.
DirectQuery sends a query to Dataverse each time a visual loads. That keeps data current and can pass the viewer's identity through. As a result, Dataverse security roles limit what each person sees. But heavy pages feel slower, and Dataverse applies its own query limits.
Many teams mix the two. For example, large history tables load by import while a small open-cases table stays live. When volumes grow very large, a link from Dataverse to Azure Synapse or Fabric often works better than either mode alone, and Microsoft Fabric consulting covers that design.
Common Power BI Dynamics 365 integration mistakes
These six problems slow many Dynamics 365 reports, and each one has a plain fix.
- Loading whole tables with hundreds of unused columns
- Showing choice codes instead of their labels
- Leaving the SQL-style endpoint switched off
- Mixing up time zones on date and time columns
- Rebuilding the same measures in every report
- Forgetting inactive records in the totals
Our Power BI Dynamics 365 integration process
Four stages take the work from first look to handover, and you approve each one.
Map apps and tables
First we list which apps are in use and which tables answer your questions, then note any custom columns.
Pick the storage mode
Next we test import against DirectQuery on real volumes, so the choice rests on measured load times.
Model and secure
Then we shape a star schema, write shared measures and decide whether security lives in Dataverse or in the model.
Publish and coach
Finally the reports go to a workspace app, and your analysts learn how to extend the model safely.
Questions on Dynamics 365 reporting with Power BI
Is a gateway needed for Power BI and Dynamics 365 online?
No. Dynamics 365 online and Dataverse run in the Microsoft cloud, so the Power BI service connects directly. Refresh uses an organizational account that you store in the semantic model settings. A gateway only matters when the same model reads an on-premises system too, for example an older ERP database that still runs in your server room.
Does the old Dynamics 365 connector still work in Power BI?
Microsoft still lists a legacy Dynamics 365 Online connector, which reads data through OData. However, Microsoft's own guidance points new work to the Dataverse connector instead. It is faster, supports DirectQuery and handles choices better. So moving an older report to the newer connector is usually the first improvement worth making.
Can each seller see only their own Dynamics 365 records?
Yes, and there are two ways to do it. With DirectQuery and single sign-on, Dataverse security roles filter the rows for each viewer. With import, we write row-level security rules in the model that follow the owner or business unit. Which route fits depends on report speed and on how complex your role setup is.
Does Business Central use the same connector?
No. Business Central has its own connector in Power BI Desktop, because it exposes data through API pages and web services. The modeling ideas stay the same, but the tables and the setup differ. So if your company runs Business Central for finance and Dynamics 365 Sales for the pipeline, one model can still read both.
How does a Dynamics 365 integration project with Power BI start?
It starts with a free assessment call of thirty minutes. You show us which apps you run and one report that frustrates people. Afterwards we send a written quote that fixes the scope. Since the build happens in your own Microsoft tenant, your admin only needs to grant a consultant access to the environment.
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.