Embedding Power BI reports inside D365 Finance and Operations workspaces
how to embed Power BI reports in D365 finance and operations workspace
Also searched as
- D365FO Power BI tile setup
- how to configure Power BI reports D365 workspace
- D365 finance and operations entity store Power BI
Short answer
D365 F&SCM can show Power BI tiles and full reports directly inside workspaces and forms, backed by either the entity store (aggregate measurements over BYOD) or embedded reports published from Power BI Desktop. Configuration happens under System administration > Setup > Power BI, then reports are attached to workspaces through personalization.
Applies to: Dynamics 365 Finance and Operations (Finance, Supply Chain Management), with a Power BI workspace and appropriate licensing.
Set up embedded Power BI reporting
- 1Confirm the Azure AD tenant used by D365FO and Power BI is the same tenant, and that users have Power BI licenses covering embedded report consumption.
- 2In System administration > Setup > Power BI, register the Power BI workspace (App workspace) that holds the reports you want available inside D365FO.
- 3Publish the target reports/datasets to that Power BI workspace from Power BI Desktop, using a dataset connected either to the entity store (aggregate measurements/BYOD) or another supported data source.
- 4In D365FO, go to the target workspace's personalization options and add a Power BI tile or embedded report control, selecting the registered report from the list the system now exposes.
- 5For entity store-backed reports, confirm the relevant aggregate measurements are enabled and the entity store processing (full or incremental) has run recently - stale processing is the most common cause of an embedded report showing old numbers.
- 6Set row-level security in the Power BI dataset if different users should see different scoped data (e.g. by legal entity or sales territory) rather than relying on D365FO security alone for the embedded view.
- 7Test with a user who has both the D365FO workspace access and the correct Power BI workspace role (Viewer at minimum) - missing Power BI access shows as a blank tile, not an obvious error.
Entity store versus direct report publishing
The entity store is D365FO's in-database analytical layer: aggregate measurements and aggregate dimensions are processed into star-schema-like structures optimized for reporting, and Power BI (or any BI tool) can connect to it directly for near-real-time analytics without hitting OLTP tables.
Reports can also be built against other sources (OData entities, Data Lake exports) and simply published to the linked Power BI workspace for embedding - useful when the numbers needed are not modeled in the entity store yet, though typically at higher latency than entity store-backed reports.
Why an embedded tile shows blank or stale data
A blank tile almost always means the signed-in user lacks a role (at least Viewer) in the underlying Power BI workspace - D365FO workspace access and Power BI workspace access are two separate permission systems that both have to line up.
Stale numbers on an entity store-backed report point to entity store processing not having run recently; check the processing schedule and history under System administration > Setup > Entity store rather than assuming the report or dataset itself is broken.
Row-level security considerations
D365FO's own security roles do not automatically restrict what an embedded Power BI report shows - the report pulls from its own dataset, so anyone with Power BI workspace access to that report sees whatever the dataset returns unless row-level security (RLS) roles are defined in Power BI itself.
For reports showing financially sensitive or legal-entity-scoped data, define RLS in the Power BI dataset mapped to the signed-in user's identity, rather than assuming D365FO's data security policies extend into the embedded report.
Common pitfalls
- !Assuming D365FO record-level security automatically applies inside an embedded Power BI report - it does not unless RLS is configured in the Power BI dataset.
- !Publishing the report to the wrong Power BI workspace, so it never appears in the list D365FO offers during personalization.
- !Forgetting entity store processing needs to run on a schedule - a report can look correctly configured but show months-old numbers.
- !Mixing users across different Azure AD tenants for D365FO and Power BI, which silently breaks the embedding even though both systems look configured.
- !Not testing with a representative low-privilege user before rollout, missing that most users lack the Power BI Viewer role on the workspace.
How an ERP-grounded AI assistant handles this
ERPray can sit alongside entity store-backed Power BI reports and answer ad hoc questions in natural language (top overdue customers this week, margin trend by product group) grounded directly in D365FO data, complementing fixed embedded tiles for the questions nobody thought to build a report for in advance.
Frequently asked questions
Do users need a full Power BI Pro license to see embedded tiles?
It depends on capacity and licensing model - reports on a Premium/Fabric capacity workspace can often be viewed without individual Pro licenses, while Pro-workspace reports generally require each viewer to have a Power BI Pro license.
Can I embed a Power BI report on a form, not just a workspace?
Yes - D365FO supports Power BI tiles and embedded reports on selected workspaces and some forms via personalization, though the exact control availability depends on the version and the form's design.
Why does the report work for me but not for a colleague?
Almost always a Power BI workspace role mismatch - check that the colleague has at least Viewer access in the specific Power BI App workspace the report was published to, separate from their D365FO security role.
How current is entity store data compared to live transactions?
It depends on the processing schedule - incremental processing can run frequently (e.g. hourly) but is not instantaneous, so entity store-backed embedded reports typically lag live transactional data by however long since the last successful processing run.
Related
Setting up Electronic Reporting (ER) formats in D365 Finance and Operations
Electronic Reporting (ER, also called GER - Global Electronic Reporting) is the D365 F&SCM framework used to generate country-specific tax reports, e-invoices, and payment files without X++ code. You build it in three layers: a data model, a model mapping to source tables, and a format that renders the mapped data. Work is done under Organization administration > Electronic reporting.
Error fixFixing "There are currently no batch servers available for processing" in D365 F&SCM
This message means the batch framework cannot find any AOS instance flagged as a batch server and available for the batch group the job is assigned to. The fix is almost always in server configuration (System administration > Servers) or batch group assignment, not in the batch job itself.
How-toHandling OData 429 Too Many Requests throttling in D365 Finance and Operations
D365 F&SCM protects shared AOS capacity by throttling OData and custom service calls, returning HTTP 429 with a Retry-After header once a client sends too many requests too quickly. The durable fix is to honor Retry-After with backoff and redesign high-volume or frequent-polling integrations to use batching, business events, or Data management instead of tight request loops.
Error fixFixing "Cannot create a record in (table). The record already exists" in D365 F&SCM data entity imports
This is the standard kernel duplicate-key exception, thrown when the Data Management Framework tries to insert a staging row into a target table whose unique or alternate key already matches an existing record. It almost always means the entity's insert-vs-update logic did not recognize the target row as an update, not that you have a true accidental duplicate in your source file.
Error fixFixing "You do not have the following permissions on TableData (table): (permission)" in Business Central AL
This runtime error means the current user's assigned permission sets do not grant the required Insert, Modify, Delete, Read, or Execute right on that specific table. It is most common right after installing or updating a custom AL extension, because Business Central checks object-level permissions even for tables an extension owns.
Error fixFixing "The CIL object was not found" in Dynamics AX 2012
This error appears when the AOS tries to execute compiled CIL for a class or method that has not actually been regenerated since a code change was imported or edited, so the .NET runtime has nothing matching to run. The fix is a full compile followed by a full CIL generation and an AOS restart, not just a partial or incremental rebuild.
AI for ERPAI for Dynamics 365 Finance and Supply Chain beyond Copilot
AI for D365 Finance and Supply Chain beyond Microsoft Copilot: private LLM grounded on data entities and OData, on-prem-capable via Local Business Data.
Stuck on Microsoft Dynamics 365 Finance and Operations (F&SCM)?
Talk to engineers who work inside Microsoft Dynamics 365 Finance and Operations (F&SCM) every week, and who build private AI that answers these questions from your own ERP data.