# Embedding Power BI reports inside D365 Finance and Operations workspaces > Source: https://netray.co/erp-help/dynamics-d365fo-power-bi-embedded-how-to > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: ERP Help ## 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. ## Kind how-to ## System dynamics ## Erp Microsoft Dynamics 365 Finance and Operations (F&SCM) ## Module Power BI integration / workspaces ## Query how to embed Power BI reports in D365 finance and operations workspace ## Alternate Queries - embedded power bi dynamics 365 finance and operations - D365FO Power BI tile setup - how to configure Power BI reports D365 workspace - D365 finance and operations entity store Power BI ## Applies To Dynamics 365 Finance and Operations (Finance, Supply Chain Management), with a Power BI workspace and appropriate licensing. ## Steps ### Set up embedded Power BI reporting **Items:** Confirm 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. In System administration > Setup > Power BI, register the Power BI workspace (App workspace) that holds the reports you want available inside D365FO. Publish 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. In 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. For 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. Set 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. Test 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. ## Sections ### Entity store versus direct report publishing **Body:** 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 **Body:** 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 **Body:** 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. ## 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. ## Ai Angle 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. ## Faq ### Do users need a full Power BI Pro license to see embedded tiles? **Answer:** 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? **Answer:** 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? **Answer:** 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? **Answer:** 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. ## Search terms D365FO Power BI embed, D365 workspace Power BI tile, entity store Power BI D365, D365 finance operations Power BI setup, aggregate measurements Power BI, D365 Power BI row-level security, D365FO analytical reporting, Power BI workspace registration D365 --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json