Surface contextual insights with Power BI
Switching between apps breaks focus. When a sales manager opens an account record and then has to open a separate Power BI tab, navigate to the right workspace, find the right report, and filter it to the right customer, they lose time and context. Embedding Power BI reports directly in Dynamics 365 forms and dashboards removes that friction; the relevant data appears where the work is already happening.
Two approaches: in-form embedding and dashboard embedding
There are two ways to embed Power BI content in Dynamics 365 apps, and they serve different purposes.
In-form embedding places a Power BI report inside a specific form, like an account form, an opportunity form, a case form. The defining capability is row-context filtering. The embedded report automatically filters to show data for the record currently open. When a customer service representative (CSR) opens a specific case, the embedded report shows data for that case. When they navigate to a different case record, the report refreshes and filters accordingly. Manual filtering isn't required.
Dashboard embedding places a Power BI tile on a Dynamics 365 dashboard. This is more appropriate for aggregate views, like a sales pipeline overview, that are relevant to a team or role rather than a specific record.
Both approaches use reports published to a Power BI workspace that your Dynamics 365 users have access to. Power BI hosts the report and renders it within the Dynamics 365 interface. Dynamics 365 displays it, but Power BI owns it.
How row-context filtering works
When you configure an in-form Power BI embed, you specify a filter parameter that links the report to the form. When the form loads, Dynamics 365 passes the current record's identifier (typically the row's unique GUID) to the Power BI report as a URL filter argument.
In the Power BI report, you configure a filter field that maps to that identifier in the underlying data model. The result is that the report renders filtered to just the data associated with the open record.
This becomes especially valuable when the embedded report draws on data beyond what's visible in the Dynamics 365 form itself — external financial data, enterprise resource planning (ERP) data, or transactional data that lives in a separate system but is relevant to the record context.
Use cases across Dynamics 365 apps
Here's how in-form and dashboard embedding applies across the four apps:
| App | Embedding type | Use case |
|---|---|---|
| Dynamics 365 Sales | In-form (Account form) | Pipeline analytics showing historical win rates, average deal size, and revenue trend for the specific account currently open, giving account managers data-driven context without leaving the record |
| Dynamics 365 Customer Service | Dashboard | A CSAT and SLA performance dashboard in the agent queue view, showing team-level metrics for the current shift or queue |
| Dynamics 365 Customer Insights | In-form (Journey record) | Segment performance metrics embedded on a journey record, showing engagement rates and conversion at each stage of the current journey |
| Dynamics 365 Field Service | Dashboard | A technician utilization and work order completion rate dashboard surfaced in the dispatcher workspace for real-time scheduling decisions |
Important
Check your Power BI licensing before configuring embedded reports. If users don't have the required license, the embedded component displays an access error rather than the report. This is a common setup issue that's easy to overlook until you test with an end user rather than an administrator account.
Configuring the embedding
In-form embedding is configured in the form designer in Power Apps. You add a Power BI component to the form layout, then specify the workspace, the report, and the filter parameter to use for row-context filtering. For dashboard embedding, you add a Power BI tile in the Dynamics 365 dashboard designer.
The report loads using the credentials of the signed-in Dynamics 365 user, so that user must also have access to the Power BI workspace where the report is published. Dynamics 365 security roles don't grant Power BI workspace access; those permissions are managed separately in Power BI.
Tip
When testing embedded reports, sign in as a standard licensed user rather than a system administrator. Administrators often have broader Power BI access than typical users, which can mask permission issues during configuration.
Learn more about embedding Power BI reports in model-driven app forms.