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.

Practitioner reality check: demos often promise “real-time ERP dashboards,” but noisy near-real-time feeds without a clean semantic model and agreed metric definitions just amplify mess. Build the model and ownership first; then decide how fresh the data needs to be.

Connection Paths at a Glance: Dataverse, F&O, Business Central

Use this comparison before you open Power BI Desktop. Choosing the wrong path is the most common reason SMEs rebuild reports six months later.

Dataverse (Sales, Customer Service, Marketing) uses the Power BI Dataverse connector and the TDS endpoint. F&O uses Entity store with DirectQuery for high-volume operational analytics, plus LCS analytical content and workspace embedding. Business Central uses the dedicated Dynamics 365 Business Central connector against API V2.0 (preferred) or OData, with Microsoft-published Power BI apps per functional area.

Cross-family reporting (for example, BC inventory next to D365 Sales pipeline) is not a single connector. You either model each source separately and combine in Power BI (composite models or shared dimensions), or stage data in a warehouse/Fabric lakehouse. SMEs should prove value on one family first, then design the cross-app model deliberately.

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 (live queries against Dataverse). Microsoft recommends Import wherever possible for performance.

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/or 5558 must be open on any firewall between your users and Microsoft's services. If only 5558 is open, append the port to the environment URL (for example org.crm.dynamics.com,5558). Most proxy servers do not handle TDS well.

There is a hard performance ceiling. Dataverse TDS queries have a result-size limit of 80 MB per query (the connector raises “Return records size cannot exceed 83886080”). For large datasets, filter early in Power Query, drop unused columns, or switch to Import. Heavily customized account, contact, or opportunity tables with many lookups and choice columns are frequent offenders—select only the columns you need, or use a constrained blank-query approach documented by Microsoft.

Modeling notes that save hours later: choice columns appear as value + name pairs; filter on the integer value column for stable performance, not the localized label join. Lookups appear as GUID + name; create relationships in Power BI on GUIDs (for example accountid), not display names. Choices (multi-select) are only partially supported and return comma-separated integers without friendly labels.

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 use DirectQuery against the Entity store for high-volume, near-real-time analytical reporting without caching data in the Power BI service—data remains in the application.

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 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 shows up. F&O's PowerBI.com integration is cloud-only; it is not supported in on-premises deployments.

For ready-made content, prefer Lifecycle Services (LCS) Shared assets and Entity store–based analytical applications over marketplace content packs. Microsoft’s future investment is Entity store and LCS workspaces; the older Cost management, Financial performance, and Retail channel performance content packs are deprecated.

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 (Microsoft Marketplace / AppSource), which ship a semantic model, reports, embed pages, and Role Center links.

Each BC Power BI app is two parts: a connector (AL) app preinstalled in BC, and a Power BI template app you install in the service. After install, run the Connect to Power BI assisted setup (or Power BI Connector Setup): fiscal vs standard vs weekly calendar, UTC offset, date table range from accounting periods, work days, data date filters, and workspace mapping for embedded reports. Semantic models take two parameters—Environment and Company (company name is case-sensitive).

Multi-company is a planning item, not an afterthought. Microsoft documents that Power BI apps work per company: install and configure a template app (and typically a workspace) for each company. Cross-company consolidation needs a custom or multi-company model. Also schedule the job queue that runs Update Dim. Set Entries at least weekly (or nightly off-hours) so dimension set entries appear in the apps.

Import vs DirectQuery for Dynamics 365 Data

Storage mode is the decision that determines whether your D365 reports feel snappy or stall at month-end. Make it deliberately before you design visuals.

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 and installing the version that matches your BC major release.

Business Central publishes Power BI apps for Finance, Inventory, Inventory Valuation, Manufacturing, Projects, Purchasing, Sales, Subscription Billing, and Sustainability (current apps target BC 27.0+; Microsoft also publishes version-specific links for BC 26). Each bundles APIs, a semantic model, reports, embed pages, and Role Center/Report Explorer links. Finance, sales, purchasing, inventory, manufacturing, and projects alone already cover dozens of out-of-the-box report pages in recent release waves.

Finance & Operations delivers ready-made Power BI content through the Lifecycle Services 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 shrink once people can drill into a well-built default dashboard.

Starter set for a typical product SME on Business Central: Finance (liquidity, profitability, actual vs budget), Sales (pipeline of posted sales, top customers), Purchasing (vendor spend), Inventory + Inventory Valuation (turns, stock valuation), and Manufacturing only if you run production. On F&O, start with Cash overview, Financial performance, and Warehouse performance. On Sales/Dataverse, start with pipeline and win-rate views before any custom CRM mashup.

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 storage mode deliberately (see the Import vs DirectQuery table). Filter early in Power Query and push filters back to the source so you are not pulling millions of rows only to display a subset. On BC apps, use the Connector Setup date filters and relative-date options so semantic models stay lean.

Model with star-schema discipline. D365 sources give you flat transactional tables; resist reporting 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 key visuals back into the D365 workspace or Role Center so the dashboard lives where users already work.

Security belongs in the model, not as a hope. Row-level security (RLS) uses DAX roles in Desktop that you assign to users or groups in the Power BI service—for example region, salesperson, or company filters. Workspace members often bypass RLS; design who is a Member/Admin versus a viewer of a published app. For multi-company BC, remember company-scoped apps already isolate companies; use RLS inside a company for sales territory or department restrictions.

SME Governance: Workspaces, Certified Datasets, and Upgrades

Without lightweight governance, every manager builds a private copy of “sales truth,” refreshes fail silently, and template upgrades wipe customizations. SMEs do not need a data office; they need a few rules that stick.

Workspace strategy: Microsoft recommends one workspace per BC Power BI app for clean access boundaries, plus multiple admins per workspace so a single leaver does not strand the model. For the embedded experience, consider keeping template app workspaces highly governed and not using them directly for day-to-day embed: copy or customize reports into a single per-company embed workspace so upgrades to the Marketplace template do not destroy your edits.

Dataset ownership: name one owner for each semantic model (usually finance ops or a power user, not “everyone with Pro”). Document Environment and Company parameters, refresh credentials, and the BC user that has Read permission on the underlying tables. Endorsement in the Power BI service (Promoted, then Certified when a steward reviews the model) tells the rest of the org which datasets are safe to build on.

Upgrade path: when Microsoft ships a new BC Power BI app version, the service shows an update banner. Choose deliberately—update workspace and app, update workspace content only, or install a second copy in a new workspace—because updates can overwrite report customizations. Test updates in a sandbox company first when you have heavy custom measures.

Access hygiene: grant viewers app access (or Viewer role), not edit rights on the workspace. Pro is required for the installer, the refresh identity, and each user who opens reports in the service or embedded in BC unless you host content on Fabric capacity F64+ (or equivalent Premium) that allows free consumers.

Power BI + Dynamics 365 Licensing in 2026

Licensing is where SMEs lose money and time. Power BI Free (sometimes available with Microsoft 365) only works in a personal workspace and cannot install or share template apps. To install a Dynamics 365 Power BI app, share a report, refresh a shared semantic model, or be a recipient of shared content, every user needs Power BI Pro—or your content must live on eligible capacity.

Current Microsoft list pricing (paid yearly, marketing prices subject to region): Power BI Pro is $14.00 per user per month; Power BI Premium Per User (PPU) is $24.00 per user per month. Pro-class features include publishing and sharing; Pro scheduled refresh is up to 8 times per day with a 1 GB model size limit on Pro. PPU raises refresh frequency and model limits and unlocks more advanced features.

Dynamics 365 entitlements do not include Power BI Pro for everyone. Business Central Essentials and Premium grant BC rights, 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—including embedded viewers in BC unless you are on capacity that allows free consumers.

At scale, the alternative to per-user Pro for large viewer populations 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. Free viewers of Power BI content without a per-user license generally require F64 or larger (P1 equivalent); smaller F SKUs still need Pro or PPU on each consumer. Publishers still need Pro or PPU even on capacity.

Two more traps: each BC company you report on needs its own semantic model configuration, and refresh frequency is license-tier dependent. Budget licensing and refresh design before you build, not after. Also watch the broader Microsoft stack: Dataverse, Fabric dataflows, and D365 are separate products—stacking them without a license map is a common surprise for SMEs.

Common Pitfalls When Connecting Power BI to Dynamics 365

TDS or firewall misconfiguration on Dataverse: connector timeouts or “unable to connect” usually mean TDS is off, ports 1433/5558 are blocked, a proxy is mangling TDS, or the environment URL includes https:// or a trailing slash. Use the bare org.crm.dynamics.com form.

Hitting the 80 MB TDS result limit: month-end DirectQuery on wide opportunity or account tables fails suddenly. Fix with earlier filters, fewer columns, Import mode, or Microsoft’s constrained-query workaround for extremely wide tables.

Still using content packs: BC packs were deprecated September 1, 2019; F&O packs for cost, financial performance, and retail channel performance are deprecated in favor of Entity store and LCS. Install current Power BI apps instead.

Wrong company or environment parameters on BC: company names are case-sensitive; a silent empty model is often a parameter typo. Multi-company tenants need an install per company, not one workspace “for everything.”

Dimensions missing in BC apps: if dimension set entries never update, the Update Dim. Set Entries job queue is not running. Schedule it weekly or nightly.

Customizations lost on template update: editing reports inside the template app workspace, then accepting an update, overwrites work. Copy reports to a governed embed workspace first.

Licensing surprise at go-live: Free users can author in Desktop but cannot use shared BC apps. Count installers, refresh accounts, and every embedded viewer. Real-time dashboard demos without agreed KPIs and a owned semantic model create noise, not decisions.

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 aged receivables and payables; a five-day DSO improvement on a mid-sized SME is real cash. Working capital: inventory turnover and days-of-supply come from Inventory and Inventory Valuation apps.

On the F&O side, analytical workspaces give you warehouse on-time receipt and shipping percentage, production performance, and cash overview out of the box. On Sales/Dataverse, pipeline coverage, win rate, and sales cycle length beat vanity activity counts. 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. Revisit the set when the operating plan changes—not every time someone asks for a new visual.

Frequently asked questions