Power BI for Dynamics 365
How Power BI integrates with Dynamics 365 — pre-built apps, Dataverse and F&O connectors, Microsoft Fabric, and where the data actually lives.
Power BI is the default analytics layer for any Dynamics 365 customer. Microsoft ships pre-built Power BI apps for every major Dynamics 365 product, and customers extend or replace them with their own. The biggest design choice is where the data sits — and there are now three serious answers.
Pre-built Power BI apps. From the Power BI app marketplace, install Microsoft's published apps for Sales, Customer Service, Finance, Business Central, Supply Chain, Field Service, and Project Operations. Each app contains a curated dataset, dashboards, and reports tuned to the source product. Out of the box, these answer 80% of the typical analytical questions and are the right starting point even if you eventually replace them.
Direct connectors. Power BI has first-class connectors to:
- Dataverse — direct query against the Dataverse SQL endpoint or import via the Dataverse connector. The right pattern for CRM-side reporting where data volumes are modest and you want live numbers.
- Business Central — REST API and OData connectors. Fast for moderate volumes; for years of history, prefer the data lake export.
- F&O entity store / data lake — historical fact-table extracts for large reporting needs.
Microsoft Fabric and OneLake. The strategic direction. Synapse Link for Dataverse streams Dataverse changes into OneLake near-real-time; Synapse Link for F&O does the same for Finance/SCM. The result is a Fabric lakehouse containing both CRM and ERP data, queryable with Power BI's DirectLake mode for fast performance without import refreshes. For mid-to-large customers, this is becoming the default analytics architecture.
Embedding. Power BI reports embed inside Dynamics 365 model-driven apps as system charts or as embedded reports in dashboards. Embedded reports respect row-level security configured in Power BI.
Row-level security. Power BI supports row-level security (RLS) that scopes data per user — typically by mapping a Dataverse business unit or territory to an RLS role. Configure it in Power BI Desktop, deploy to the service, and reports show each user only their data.
Performance. Import models are fastest for end users but require scheduled refresh. DirectQuery is live but slower and load-sensitive. DirectLake bridges the two, querying OneLake parquet without import. Pick deliberately per dataset.
Costs. Power BI Pro per user, Premium per user, or Premium capacity. Pre-built apps require at least Pro for end users; large embedded scenarios usually justify a Premium capacity.
Operational reality. Don't build a custom Power BI model the day before go-live. Start with Microsoft's app, evolve from real user questions, and migrate to Fabric when scale demands it.
Related guides
- Power BI dataflows vs datamartsPower BI dataflows, datamarts, semantic models, and Fabric items — when to use each, how they relate, and the path Microsoft's Fabric strategy is pushing data work toward.
- Power BI deployment pipelinesHow Power BI deployment pipelines automate Dev/Test/Prod promotion of reports, semantic models, and dataflows — configuration, rules, and the ALM patterns.
- Power BI gateway for on-prem dataHow the on-premises data gateway bridges Power BI to on-prem data sources — installation, configuration, security, and the patterns for hybrid analytics on Dynamics 365 data.
- Power BI incremental refreshHow Power BI incremental refresh works — partitioning by date, range parameters, the refresh policy, and the patterns for large datasets.
- Power BI paginated reportsHow paginated reports differ from interactive Power BI reports — SSRS lineage, design tool, when pixel-perfect matters, and the operational role of paginated reports alongside interactive.