Power BI for Dynamics 365: Connect, Customize, and Track What Matters for SMEs

What 'Power BI for Dynamics 365' Actually Means

Power BI integrates with Dynamics 365 to deliver interactive reports, dashboards, data exploration, and embedded analytics directly inside D365 workspaces. The emphasis is on data exploration (filtering, drilling, and pivoting) rather than static reports you export once and forget.

The architecture matters more than the marketing. Dynamics 365 is not one product; it is a family of apps that sit on different data platforms, and Power BI connects to each one differently. Customer engagement apps (D365 Sales, Customer Service, Marketing) run on Dataverse. Finance and operations apps (F&O) use an operational Entity store optimized for analytics. Business Central exposes data through API pages and OData web services.

This split shapes everything that follows: how you connect, how fast the data refreshes, how much you can query, and what ready-made content already exists. Treat the analytical layer as a decision you make per app family, not a single switch you flip once. This guide covers all three families; for Business Central specifically (connectors, default reports by functional area, and KPIs), see our dedicated Business Central Power BI deep dive.

Connect D365 Sales, Customer Service & Marketing (Dataverse)

For D365 apps built on Dataverse, Power BI Desktop connects via Get Data then Dataverse. You use the environment URL (typically of the form org.crm.dynamics.com) and choose between Import mode (cached data with scheduled refresh) or DirectQuery (real-time queries against Dataverse).

Under the hood, the Dataverse connector relies on the Tabular Data Stream (TDS) endpoint. Two prerequisites catch SMEs off guard: the TDS endpoint must be enabled in the Power Platform Admin Center under Settings, Product, Features, and TCP ports 1433 and 5558 must be open on any firewall between your users and Microsoft's services. Without both, the connector fails silently or with a generic timeout.

There is a real performance ceiling. Dataverse TDS endpoint queries have a hard result-size limit of 80 MB per query (the connector raises 'Return records size cannot exceed 83886080'). For large datasets, filter early in your Power Query steps, select fewer columns, or switch to Import mode for heavy reporting workloads. This is the most common reason a 'fast' DirectQuery dashboard feels sluggish at month-end.

Connect D365 Finance & Operations (Entity store)

D365 Finance & Operations connects to Power BI primarily through the Entity store, an operational data store optimized for reporting that is included with the application. From Power BI Desktop, you can use DirectQuery against the Entity store for near-real-time, large-volume analytical reporting without caching data in the Power BI service.

To pin Power BI tiles and reports into F&O workspaces so users see them where they work, an admin does a one-time setup. It requires an Entra ID (Azure AD) app registration with delegated permissions for Power BI resources, plus configuration in the D365 Power BI configuration page (System Administration, Setup, Power BI). This is the step most SMEs underestimate: it is a security and governance task, not a reporting task, and it usually needs whoever owns your Microsoft 365 tenant.

Once configured, embedding is per-workspace. Users view pinned content inside F&O without leaving the app, which is where the productivity gain actually shows up (not in PowerBI.com, but in the ERP screen they already live in). Note: F&O's PowerBI.com integration is cloud-only; it is not supported in on-premises deployments.

Connect D365 Business Central

Business Central connects to Power BI through the dedicated Dynamics 365 Business Central connector in Power BI Desktop (Get Data, Online Services, Dynamics 365 Business Central). It exposes data via API pages (API V2.0 is recommended) or OData web services. Business Central online is pre-enabled for Power BI; on-premises deployments require additional Entra ID registration.

Avoid the legacy path. Microsoft deprecated the legacy Power BI content packs for Dynamics 365 Business Central effective September 1, 2019. They have known issues, no longer receive updates, and are not the supported way to get BC data into Power BI. The supported replacement is Power BI template apps distributed through Microsoft AppSource; these are maintained, versioned, and what your partner should be installing.

The same deprecation applies on the F&O side: Microsoft's deprecated-features documentation lists the Cost management, Financial performance, and Retail channel performance content packs as replaced by analytical applications and Entity store-based integration. Future investment is focused on the Entity store and Lifecycle Services (LCS) analytical workspaces. Any guide still pointing you at 'content packs' for F&O or BC is out of date.

Default Dashboards & Template Apps You Can Install Today

You do not have to build from scratch. Microsoft publishes ready-made Power BI content for every D365 app family; the trick is knowing which library to pull from.

Business Central publishes dedicated template apps (now 'Power BI apps') covering the major functional areas: Finance, Sales, Purchasing, Inventory and Inventory Valuation, Manufacturing, and Projects. Each bundles a semantic model and multiple reports. For the full per-area report inventory and the KPIs worth tracking, see our Business Central Power BI guide.

Finance & Operations delivers ready-made Power BI content through the Lifecycle Services (LCS) Shared assets library and embedded analytical workspaces. The catalog includes Warehouse performance (on-time receipt, shipping percentage, inventory accuracy), Purchase spend analysis, Sales and profitability performance, Financial performance, Actual vs budget, Cash overview, and Production performance.

For customer engagement apps, Microsoft publishes Sales Insights and Customer Service analytical content, and partners publish additional template apps through AppSource. For an SME, the practical play is to install the relevant template apps first, give finance and operations leads two weeks to live in them, and only then commission custom reports for the gaps. Most 'custom reporting' requests disappear once people can actually drill into a well-built default dashboard.

Building Custom Power BI Reports on Dynamics 365 Data

Custom reporting is where SMEs get the most long-tail value, and where the architecture decisions from the connection section bite. Start in Power BI Desktop, which is free for authoring. The decisions that determine whether your custom report performs are made before you build a single visual.

Choose your storage mode deliberately. Import mode gives the best performance and the richest DAX, but data is cached and only as fresh as your last scheduled refresh. DirectQuery keeps data fresh against Dataverse or the F&O Entity store, but every visual becomes a live query, so the 80 MB TDS ceiling and the Entity store's analytics-oriented design both matter.

Filter early in Power Query. Push filters back to the source wherever possible so you are not pulling millions of rows into the model only to display a subset. This is the single highest-impact habit for keeping custom D365 reports fast.

Model with star-schema discipline. D365 sources give you flat transactional tables; resist the urge to report off them directly. Build a date table aligned to your fiscal calendar, conformed dimensions for customer, item, and vendor, and a single fact table per process. Publish to a workspace backed by the right capacity, then pin the key visuals back into the D365 workspace or Role Center so the dashboard lives where users already work.

Power BI + Dynamics 365 Licensing in 2026

Licensing is where SMEs lose money and time. Power BI Free (sometimes included with BC) only works in a personal workspace and cannot install or share template apps. To install a Dynamics 365 Power BI app, share a report, or be a recipient of shared content, every user needs Power BI Pro.

Dynamics 365 entitlements do not include Power BI Pro for everyone. Business Central Essentials and Premium grant BC entitlements, not Power BI Pro. The same applies to D365 Sales, Customer Service, and F&O user subscriptions. Budget Power BI Pro as a separate line item for every user who will open, share, or author a report.

At scale, the alternative to per-user Pro is Microsoft Fabric capacity (F-SKUs). Microsoft retired Power BI Premium per capacity P-SKUs in July 2024 for new purchases, moving customers to Fabric capacities. Fabric makes semantic model capacity a single purchased resource rather than a per-user gate, which can be cheaper once you have tens of report consumers.

Two more traps to plan around: each company in a BC tenant that you want to report on needs its own semantic model configuration (cross-company consolidation needs a custom or multi-company model), and refresh frequency is license-tier dependent. Budget licensing and refresh design before you build, not after.

What an SME Should Actually Track

Most SMEs install the apps, then stare at the Overview page and move on. The value is in the KPIs behind the reports, narrowed to the three to five that map to this quarter's operating priorities.

Liquidity: current, quick, and cash ratios come from the Finance app; trend them monthly against your operating expense run-rate rather than an industry benchmark. Cycle time: Days Sales Outstanding and Days Payable Outstanding come from the aged receivables and payables reports; a five-day DSO improvement on a mid-sized SME is real cash. Working capital: inventory turnover and days-of-supply come from the Inventory app.

On the F&O side, the analytical workspaces give you warehouse on-time receipt and shipping percentage, production performance, and cash overview out of the box. Pin the three to five that map to current operating priorities to a workspace tab and review them weekly. The trap is defining too many KPIs; the discipline is picking the few that move the needle and ignoring the rest until next quarter.