Embedded Power BI Reports in a Model-Driven App
Reviewed by Errin O'Connor, Founder & Chief AI Architect
EPC Group configures Power BI reports inside Dynamics 365 model-driven apps so users see live analytics on the same screen as CRM records. We handle Power BI control configuration, row-level security, filter context, and capacity planning. No context switching. No separate BI tool login.
Key Facts
- 1,500+ Power BI deployments completed by EPC Group consultants.
- Microsoft Fabric F SKU list prices, East US, pay-as-you-go: F2 ($263/mo), F4 ($526/mo), F64 (~$8,410/mo).
- Main-form embedding uses a Power BI control added to the form XML through an exported solution.
- Row-level security (RLS) applies even when reports are embedded — enforced at the model level.
- Microsoft consulting since 1997. Microsoft Solutions Partner — core designations.
Embed Power BI Reports in a Model-Driven App
Why embed Power BI in model-driven apps?
Model-driven apps in Power Apps (and Dynamics 365) show records from Dataverse. Users work a record — an account, a case, a work order. They need analytics on that same record. Without embedded Power BI, they switch tabs or open a separate tool.
Embedded Power BI keeps the insight at the point of decision. Adoption rates improve. Data-driven actions happen faster. IT teams manage one fewer separate tool.
- Healthcare: patient outcome trends alongside clinical records.
- Financial services: portfolio performance inside CRM account pages.
- Manufacturing: supply chain metrics on production work orders.
How to embed Power BI in a model-driven app
Microsoft documents a form XML method for main forms: the Power BI control is added outside the form designer (Microsoft Learn, accessed 2026-11-22). The setup follows four steps.
- Step 1 — Enable Power BI embedding: turn on Power BI visualization embedding for the environment; it is off by default.
- Step 2 — Add a placeholder: in a development environment, add the table's main form to a solution and add a placeholder subgrid where the report should appear.
- Step 3 — Replace the control XML: export the solution as unmanaged, replace the subgrid control in customizations.xml with the Power BI control (workspace ID, report ID and report URL), and add a PowerBIFilter element to filter on a column of the current record.
- Step 4 — Import, publish and test: import the solution, publish, open a test record, and check that the report filters to that record and respects RLS.
Filter context and record linking
The most valuable configuration is passing the current record's ID or field value as a filter to the embedded report. This makes the report show data for only that record.
EPC Group tests filter behavior across three edge cases before any deployment goes live:
- No data match — the report shows a meaningful empty state, not a blank visual.
- Large result sets — the report stays responsive in import mode or Direct Lake, checked on the largest records before go-live.
- Security boundaries — RLS applies correctly; users never see records outside their scope.
Row-level security in embedded reports
RLS is not optional in enterprise deployments. It must hold even when the report is embedded inside a model-driven form.
The Power BI report enforces RLS at the semantic model level, and Power Apps security roles and privileges do not change the data an embedded report shows (Microsoft Learn, accessed 2026-11-22). Without RLS, every user sees what the creator of the semantic model would see. Users see only the rows their role allows when RLS is in place.
- Define RLS roles in Power BI Desktop.
- Map roles to Microsoft Entra ID security groups.
- Verify with a non-admin test account inside the app.
- Log access in Microsoft Purview for audit defensibility.
Capacity and performance planning
Embedded Power BI reports run on your Power BI capacity (or Fabric F-SKU). Choose the right tier before deployment.
- F2 ($263/mo) — small workloads; 3 GB max memory per Direct Lake model (Microsoft Learn, Direct Lake overview, accessed 2026-11-22).
- F4 ($526/mo) — twice the capacity units of F2, with the same 3 GB Direct Lake memory limit.
- F64 (~$5,003/mo with a one-year reservation) — the smallest F SKU where viewers with a free license and a viewer role can read Power BI content (Microsoft Learn, Microsoft Fabric licenses, accessed 2026-11-22).
F SKU prices are Microsoft list prices for East US (pay-as-you-go per month; the one-year reservation for F64), read from the Azure Retail Prices API on 2026-11-22. They vary by region.
To reduce capacity pressure on embedded reports:
- Keep the number of visuals per page low.
- Use import mode unless real-time data is required.
- Place the Power BI control on a non-default tab so the report is not part of the first form load.
- Review capacity sizing on a set schedule as report usage and model size grow.
Frequently asked questions
What apps support embedded Power BI?
Model-driven apps built on Dataverse, including Dynamics 365 Sales, Customer Service and Field Service, can show a Power BI report on a main form or a dashboard. Main-form embedding uses a Power BI control added to the form XML through an exported solution. Canvas apps and SharePoint pages use a different embedding approach.
Do embedded reports require a Power BI Pro license?
Usually yes: each viewer needs a Power BI Pro or Premium Per User license, unless the report sits on a Fabric capacity of F64 or larger, or a Power BI Premium P capacity, where a viewer with a free license and a viewer role can read it (Microsoft Learn, Microsoft Fabric licenses). At Microsoft list prices, Pro is $14.00 and Premium Per User $24.00 per user per month, paid yearly (Power BI pricing page, accessed 2026-11-22).
Can I filter an embedded report by the current record?
Yes. Add a PowerBIFilter element to the Power BI control in the form XML and alias a column of the current record, such as its name or ID, to a matching column in the Power BI semantic model. Both fields must have the same data type, for example text in Dataverse and text in Power BI.
Does RLS still apply when Power BI is embedded?
Yes, and it is the control to rely on. Power BI row-level security still applies inside the form, while Power Apps security roles and privileges do not change what the embedded report shows. Without RLS, every user sees the data the creator of the semantic model would see. Define RLS roles in the semantic model and map them to Microsoft Entra ID security groups.
What is the difference between "App Owns Data" and "User Owns Data"?
"User Owns Data" means each user signs in to Power BI with their own account; model-driven forms work this way, signing users in with their Power Apps credentials. "App Owns Data" means the application authenticates for everyone through a service principal, so end users need no Power BI license; it is used with Power BI Embedded for custom web apps and ISV scenarios.
How is an embedded Power BI project scoped?
EPC Group scopes it from the number of forms and apps, the reports to embed, the row-level security roles and whether the capacity must change. Acceptance is a test record on each form that filters the report to that record, and a non-admin test account that sees only its permitted rows. The timeline and fee are set in the statement of work after a scoping call.
Configure Power BI in your Dynamics 365 environment
Talk to an EPC Group Power BI architect: request a scoping call, or call (888) 381-9725. See also Power BI and Dynamics 365 integration.
Last updated by Errin O'Connor, Founder & Chief AI Architect, EPC Group
Power BI Strategy: 2026 Considerations for Embedded Power BI Reports In A Model Driven App
Power BI Copilot grounds itself on the semantic model, NOT the underlying source data. That means Copilot answers are only as accurate as the DAX measure definitions, the field metadata (display folders, descriptions, hierarchies), and the synonyms taxonomy. In practice, the difference between a Copilot deployment that analysts keep using and one they abandon is whether the semantic model was Copilot-prepared: measure descriptions written, synonyms defined, and hierarchies and display folders curated before the first prompt is typed.
Power BI capacity sizing starts with the F SKU list prices above: F2 and F4 share a 3 GB Direct Lake model-memory limit (Microsoft Learn, Direct Lake overview, accessed 2026-11-22), and F64 is the smallest F SKU where viewers with a free license can read Power BI content (Microsoft Learn, Microsoft Fabric licenses, accessed 2026-11-22). Revisit sizing when report usage or model size grows.
Decision factors EPC Group evaluates
- Copilot grounding quality assessment of semantic-model metadata
- Direct Lake mode adoption for Fabric-resident semantic models
- License optimization audit (Pro vs Premium Per User vs F-SKU)
- Row-level security via service principal authentication
- Capacity sizing decision (F2/F4/F64+) tied to peak concurrent users and refresh window
See related EPC Group services or schedule a discovery call.
Related reading
- Embedding Power BI Dashboards in SharePoint for Organization-Wide Access
- Emergency Power BI Support from Senior Microsoft Architects
- EPC Group Reports 216 Microsoft 365 Tenant-to-Tenant Migrations and Details Every Route
- EPC Group Reports 50-Plus Microsoft 365 GCC High Migrations in a Year, Details Every Route to GCC
- EPC Group vs Algoscale for Power BI Consulting (2026)
- Power BI Consulting Services
- Microsoft Fabric Consulting
- AI Governance Consulting
- SharePoint Consulting Services
- Microsoft 365 Consulting
- Azure Cloud Services
- Microsoft & AI Consulting Firm Rankings