Study guide
5.4 Embedding Power BI Reports, Dashboards & Tiles
Microsoft Power Platform Functional Consultant PL-200
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Dataverse Tables, Relationships & Core Columns
1.1 Dataverse Table Types, Properties & Ownership 1.2 Table Relationships & Cascading Rules 1.3 Column Types, Formats, Primary Keys & Alternate Keys 1.4 Rollup, Calculated & Formula Columns with Power Fx
2 Chapter 2: Dataverse Data Management & Governance
2.1 Dataverse Search, Quick Find & Relevance Indexing 2.2 Auditing Configuration & Log Management 2.3 Duplicate Detection Rules & Settings 2.4 Bulk Record Operations, Data Import, Export & Templates
3 Chapter 3: Dataverse Security Model & Access Control
3.1 Business Units, Ownership Models & Modern BU Matrix 3.2 Security Roles, Privileges & Depth Levels 3.3 Teams Architecture: Owner, Access, and Microsoft Entra (AAD) Group Teams 3.4 Column-Level Security & Hierarchy Security Models
4 Chapter 4: Model-Driven App Fundamentals & Information Architecture
4.1 Model-Driven App Design, Site Map Navigation & Modern App Designer 4.2 Form Types: Main, Quick Create, Quick View & Card Forms 4.3 View Configuration, System Views, Personal Views & Filters
5 Chapter 5: Advanced Model-Driven App Components & Custom Pages
5.1 Custom Pages & Modern Commanding with Power Fx 5.2 Form Component Controls & Specialized UX Elements 5.3 Embedding Canvas Apps in Model-Driven Forms 5.4 Embedding Power BI Reports, Dashboards & Tiles
6 Chapter 6: Canvas Apps Structure, Formulas & Data Operations
6.1 Canvas App Architecture, Screens, Containers & Controls 6.2 Power Fx Formulas, Delegation & Data Source Limits 6.3 Variables (Context, Global), Collections & State Management 6.4 Triggering Power Automate Cloud Flows from Canvas Apps
7 Chapter 7: Power Pages Site Design, Navigation & Content
7.1 Power Pages Design Studio & Site Structure 7.2 Power Pages Templates, Styling & Responsive Layouts 7.3 Web Pages, Navigation Menus & Content Snippets
8 Chapter 8: Power Pages Data Integration, Forms & Web Roles
8.1 Power Pages Lists, Basic Forms & Advanced Forms 8.2 Table Permissions, Web Roles & Page Access Security 8.3 External Identity Providers & Authentication Configuration
9 Chapter 9: Power Automate Cloud Flow Fundamentals & Triggers
9.1 Cloud Flow Types: Automated, Instant, Scheduled & Desktop Overview 9.2 Dataverse Connector Triggers & Operational Filters 9.3 Standard Connectors, Custom Connectors & Connection References
10 Chapter 10: Cloud Flow Actions, Expressions & Logic Controls
10.1 Logic Controls: Conditions, Switches, Apply to Each & Do Until Loops 10.2 Variables, Data Operations & Dynamic Content Manipulation 10.3 Power Automate Expression Language (WDL / Functions) 10.4 Error Handling, Configure Run After & Scope Controls
11 Chapter 11: Business Process Flows & Guided Processes
11.1 Business Process Flow Architecture, Stages, Steps & Data Steps 11.2 Branching Rules & Multi-Entity Business Process Flows 11.3 BPF Action Steps, Workflows & Cloud Flow Execution 11.4 BPF Security Roles, Order & Process Lifecycle
12 Chapter 12: Classic Workflows, Business Rules & Modern Logic Extensibility
12.1 Classic Dataverse Workflows: Real-Time vs. Background (Async) 12.2 Business Rules: Scope & Actions 12.3 Low-Code Plug-ins in Dataverse: Automated vs. Instant 12.4 Troubleshooting Automations, Run History & Analytics
13 Chapter 13: Power Platform Environment Architecture & Security
13.1 Environment Types: Default, Sandbox, Production, Trial, Developer 13.2 Environment Governance, Groups, Routing & Capacity Management 13.3 Data Loss Prevention (DLP) Policies & Connector Classifications
14 Chapter 14: Application Lifecycle Management (ALM) & Solutions
14.1 Unmanaged vs. Managed Solutions & Solution Layering Mechanics 14.2 Solution Components, Dependencies, Publishers & Prefixes 14.3 Exporting, Importing, Upgrading & Patches 14.4 Solution Checker, App Checker & ALM Best Practices
15 Chapter 15: Enterprise Interoperability & Service Integration
15.1 Exchange / Server-Side Synchronization & Email Integration 15.2 SharePoint & OneDrive Document Management Integration 15.3 Microsoft Word & Excel Document Templates
16 Chapter 16: Copilot, AI Capabilities & Exam Strategy
16.1 Copilot Studio & Generative AI across Power Platform 16.2 AI Builder Prebuilt & Custom Models in Apps and Flows 16.3 PL-200 Exam Strategy, Time Management & Question Analysis
5.4 Embedding Power BI Reports, Dashboards & Tiles
Key Takeaways Explain This Topic AI
Power BI embedding in Model-Driven Apps requires enabling the environment feature setting 'Power BI visualization embedding' in the Power Platform Admin Center.
The Power BI Report PCF control enables embedding interactive reports directly on model-driven forms with dynamic row-level contextual filtering using JSON filter parameters.
System Dashboards in Dataverse can host embedded Power BI reports and tiles, packaged inside solutions for enterprise Application Lifecycle Management (ALM).
The 'Visualize this view' capability empowers end users to generate instantaneous AI-assisted Power BI exploratory reports directly from any model-driven entity grid.
Security boundaries operate independently: Dataverse security roles govern table privileges, whereas Power BI workspace permissions, Row-Level Security (RLS), and Power BI Pro/PPU licensing govern report rendering.
Last updated: August 2026
Embedding Power BI Reports, Dashboards & Tiles
Executive leadership and operational teams require deep analytical insights combined with transactional workflows. While native Dataverse charts and dashboards provide quick summaries of operational records, complex business intelligence—such as multi-source data mashups, historical trend forecasting, time-intelligence calculations, and advanced interactive visualizations—requires Microsoft Power BI .
Microsoft Power Platform provides deep native integration between Dataverse and Power BI. For the PL-200: Microsoft Power Platform Functional Consultant exam, you must master the prerequisites for enabling Power BI embedding, how to configure the Power BI Report PCF control on forms with contextual row-level filtering, how to build Power BI System Dashboards, and how to govern security and solution ALM.
1. Environment Prerequisites & Enabling Power BI in PPAC
Before any Power BI report, dashboard, or tile can be embedded within model-driven apps, the capability must be enabled at the environment level in the Power Platform Admin Center (PPAC) . +-----------------------------------------------------------------------------------+
- | POWER BI EMBEDDING ENVIRONMENT ACTIVATION |
- | |
- | [PPAC: admin.powerplatform.microsoft.com] |
- | | |
- | v |
- | Environments ---> [Select Environment] ---> Settings |
- | | |
- | v |
- | Product ---> Features ---> [Power BI visualization embedding] = [ ON ] |
- | | |
- | v |
- | Enables cross-origin iframe embedding and Entra ID Single Sign-On (SSO) |
- +-----------------------------------------------------------------------------------+
- Step-by-Step Administrative Activation
Sign in to the Power Platform Admin Center ( admin.powerplatform.microsoft.com ).
Navigate to Environments and select the target environment.
Select Settings from the top command bar, expand Product , and select Features .
Under the Power BI section, toggle Power BI visualization embedding to On .
Click Save at the bottom of the page.
Important
Prerequisite Impact: If 'Power BI visualization embedding' is disabled in PPAC, all embedded Power BI report controls on forms and system dashboards will fail to render, displaying a configuration error or blank container to end users.
Licensing Requirements
Viewing Embedded Reports: Users must possess a valid Power BI Pro license, Power BI Premium Per User (PPU) license, or the report must reside in a workspace backed by a Power BI Premium Capacity / Microsoft Fabric Capacity (F64+ or P-SKU).
Dataverse Access: Users must also have an assigned Dataverse Security Role providing read access to the model-driven app.
2. Embedding Power BI Reports on Model-Driven Forms (PCF Control)
To display an interactive Power BI report directly on a record form (e.g., displaying an Account's 3-year revenue breakdown on the Account form), consultants use the Power BI Report PCF Control ( Microsoft.PowerBI.ReportControl ). +-----------------------------------------------------------------------------------+
- | POWER BI FORM CONTROL CONTEXTUAL FILTERING |
- | |
- | [HOST FORM: Account "Alpine Ski House" (ID: 4f8a-9b2c...)] |
- | +------------------------------------------------------------------------------+ |
- | | Account Name: Alpine Ski House | Account Number: AC-401 | |
- | | | |
- | | +-- SECTION: Power BI Embedded Revenue Analytics --------------------------+ | |
- | | | [Power BI Report Control] | | |
- | | | Parameter: PowerBIReportPath = "https://app.powerbi.com/..." | | |
- | | | Filter: {"Filter": "[Accounts].[accountid] eq '{RecordID}'"} | | |
- | | | | | |
- | | | +----------------------------------------------------------------------+ | | |
- | | | | (Renders Power BI visual filtered ONLY to Alpine Ski House records!) | | | |
- | | | +----------------------------------------------------------------------+ | | |
- | | +--------------------------------------------------------------------------+ | |
- | +------------------------------------------------------------------------------+ |
- +-----------------------------------------------------------------------------------+
- Control Properties & Parameters
When adding the Power BI Report control to a form column or section in the form designer, the consultant configures three primary properties:
PowerBIReportPath : The URL path of the Power BI report (e.g., https://app.powerbi.com/groups/workspaceId/reports/reportId/ReportSection ).
PowerBIReportParameters (Contextual Row-Level Filtering): A JSON filter string or URL filter string that binds the report's dataset to the currently open record.
PowerBIReportProperties : JSON settings controlling UI elements, such as showing or hiding the filter pane, navigation tabs, and bookmarks bar.
Contextual Row-Level Filtering Syntax
To ensure the embedded report dynamically displays data only for the record currently open on the form, the consultant defines a JSON filter parameter referencing the host record's primary key or unique code: {
- "Filter": "[Accounts].[accountid] eq '{RecordID}'",
- "Alias": {
- "Accounts": "dataverse_accounts_table"
- }
- }
{RecordID} is a system token automatically substituted at runtime with the 128-bit GUID of the currently active model-driven record.
Alternatively, filtering by specific text columns (such as Account Number) can be passed using URL filter syntax: $filter=Customer/AccountNumber eq '{accountnumber}'
3. System Dashboards vs. Power BI Dashboards
Model-driven apps support two distinct dashboard architectures: native Dataverse System Dashboards and Power BI System Dashboards . +-----------------------------------------------------------------------------------+
- | DASHBOARD ARCHITECTURAL COMPARISON |
- | |
- | [NATIVE DATAVERSE SYSTEM DASHBOARD] [POWER BI EMBEDDED SYSTEM DASHBOARD] |
- | - Real-time Dataverse SQL query - Aggregates multi-source datasets |
- | - Standard charts, lists, timelines - High-fidelity interactive visuals |
- | - Governed 100% by Dataverse Security - Governed by Dataverse + Power BI RLS |
- | - Native solution component - Solution component + Workspace link |
- | - Included in standard Power Apps license - Requires Power BI Pro / PPU / Fabric |
- +-----------------------------------------------------------------------------------+
- Detailed Comparison
Capability Native Dataverse System Dashboard Power BI Embedded System Dashboard
Data Source Scope Dataverse tables only (Single environment) Multi-source (Dataverse, SQL, SAP, Web APIs, Excel)
Visualization Fidelity Basic bar, line, pie charts and views High-fidelity maps, decomposition trees, gauges, KPIs
- Data Freshness Real-time transactional queries Scheduled refresh or DirectQuery via TDS endpoint
- Solution ALM 100% Native Solution component Solution component (uses Environment Variables)
- Licensing Cost Included with Power Apps / Dynamics 365 Requires Power BI Pro / PPU / Premium Capacity
Security Enforcement Dataverse Security Roles & BU depths Dual: Dataverse App Access + Power BI Workspace Roles
Creating a Power BI System Dashboard in Solutions
In the Maker Portal ( make.powerapps.com ), open your Solution.
Select New > Dashboard > Power BI Embedded .
In the dashboard dialog, select the Power BI Workspace and the target Power BI Report or Power BI Dashboard .
Save and publish all customizations. The dashboard now appears in the model-driven app's dashboard selector for all authorized users.
4. 'Visualize This View' (Power BI Quick Reports)
In modern model-driven apps, end users do not need to wait for business intelligence developers to author custom reports. The Visualize this view feature provides instant, AI-assisted data exploration directly from any active entity grid. +-----------------------------------------------------------------------------------+
- | 'VISUALIZE THIS VIEW' WORKFLOW |
- | |
- | [Model-Driven View: Active Opportunities] |
- | | |
- | +---> Command Bar: Click ['Visualize this view'] |
- | | |
- | v |
- | [Power BI Quick Report Engine] |
- | - Automatically analyzes view columns and active filters |
- | - Generates interactive charts, summary KPI cards, and slicers |
- | - Allows users to customize fields on the fly |
- | | |
- | v |
- | [Save Option] ---> Save to personal Power BI workspace for future access |
- +-----------------------------------------------------------------------------------+
Triggering: On the command bar of any table view (e.g., Active Accounts, Open Invoices), users click Visualize this view .
Behavior: Power BI automatically creates an exploratory quick report based on the view's current column definitions and active user filters.
Interactivity: Users can modify visual types, add fields to axes and legends, filter records, and optionally Save the generated report into their personal Power BI workspace.
5. Security Boundaries & Solution ALM for Power BI
Implementing Power BI in enterprise environments requires understanding the dual security model and managing multi-environment Application Lifecycle Management (ALM). +-----------------------------------------------------------------------------------+
- | DUAL SECURITY LAYER MODEL |
- | |
- | [LAYER 1: DATAVERSE SECURITY] |
- | - Evaluates Model-Driven App Access & Security Roles |
- | - If User has Role: Model-Driven Form / Dashboard Shell renders |
- | |
- | [LAYER 2: POWER BI SERVICE SECURITY] |
- | - Evaluates Power BI Workspace Role / App Sharing & Entra ID SSO |
- | - Evaluates Power BI Row-Level Security (RLS) on the dataset |
- | - If User has Power BI access: Visuals render data |
- | - If User LACKS Power BI access: "Report Not Available" / 403 Error displayed |
- +-----------------------------------------------------------------------------------+
- Managing ALM with Power BI Environment Variables
When deploying solutions across Development, Test, and Production environments, Power BI Workspaces and Report IDs typically differ.
Best Practice: Utilize Power BI Environment Variables in Dataverse Solutions.
Mechanics: Instead of hardcoding the Workspace GUID and Report GUID into the dashboard or form control, bind the properties to Power BI Environment Variables. When importing the managed solution into Test or Production, administrators specify the target environment's corresponding workspace and report IDs without modifying the underlying solution components.