SharePoint Dashboard Integration: Embedding Power BI for Enterprise Analytics

Why SharePoint Dashboard Integration Matters

Data-driven decisions require data accessibility. When dashboards live only in the Power BI service, adoption suffers because users must navigate to a separate application, remember which workspace contains which report, and switch between Power BI and their daily collaboration tools. Embedding Power BI dashboards in SharePoint puts analytics where people already work — in their intranet, department sites, and project portals.

SharePoint dashboard integration transforms SharePoint from a content management platform into a business intelligence hub. Executive dashboards on the intranet home page, departmental KPIs on team sites, project health metrics embedded in project portals — this is how modern enterprises make data accessible to every employee, not just analysts.

EPC Group has implemented SharePoint dashboard integrations for Fortune 500 enterprises across healthcare, finance, and government. Our Power BI consulting and SharePoint consulting practices work together to deliver dashboard experiences that are secure, performant, and adopted by users across the organization.

The Power BI Web Part: How It Works

Microsoft provides a native Power BI web part for SharePoint Online that enables seamless embedding without custom development. The web part renders an interactive Power BI report directly in a SharePoint page, preserving all interactivity including filters, slicers, cross-filtering between visuals, drillthrough, and bookmarks.

Setup Requirements

Before embedding Power BI in SharePoint, ensure these prerequisites are met. First, the Power BI report must be published to the Power BI service (app.powerbi.com) in a workspace — reports in "My Workspace" cannot be shared or embedded. Second, users who will view the embedded report must have either a Power BI Pro license, a Power BI Premium Per User license, or the report must reside in a Premium capacity workspace (which allows free Microsoft 365 users to view reports). Third, the SharePoint page must be a modern page — classic SharePoint pages do not support the Power BI web part. Fourth, the Power BI tenant setting "Allow SharePoint Online publish" must be enabled in the Power BI admin portal.

Step-by-Step Embedding Process

The embedding process is straightforward. In Power BI service, open the report you want to embed and click Share, then select Embed report and choose SharePoint Online. Copy the embed URL that Power BI generates. In SharePoint, edit the target page, click the plus icon to add a web part, search for "Power BI" and select it. Paste the embed URL into the web part configuration panel. Optionally configure the web part to show a specific report page, hide the navigation pane, hide the filter pane, or show the report as a full-width page. Save and publish the SharePoint page.

Row-Level Security Pass-Through

Row-Level Security (RLS) is the cornerstone of secure dashboard embedding. When RLS is configured in the Power BI data model, each user who views the embedded report sees only the data rows their role permits. This happens automatically — the Power BI web part passes the user's Azure AD identity to the Power BI service, which evaluates the RLS rules and filters data accordingly.

This is critical for enterprise scenarios. A regional sales dashboard embedded on the sales team's SharePoint site shows each salesperson only their territory's data. An HR dashboard on the intranet shows managers only their direct reports' metrics. A financial dashboard shows each department head only their budget and actuals. Without RLS, you would need separate reports for each role — creating a maintenance nightmare and increasing the risk of data exposure.

Configuring RLS for SharePoint Embedding

RLS configuration happens in Power BI Desktop before publishing. Define roles using DAX filter expressions on fact and dimension tables. Common patterns include department-based filtering (filter data where Department equals the user's department from a lookup table), region-based filtering (filter data where Region matches the user's assigned region), and manager hierarchy filtering (filter data based on the reporting chain in the org hierarchy). After publishing to Power BI service, assign Azure AD users or security groups to each RLS role. Test by using the "View as role" feature in Power BI service before embedding in SharePoint. EPC Group designs RLS architectures that are scalable and maintainable — using security group-based assignments rather than individual user assignments to simplify ongoing management.

Performance Optimization for Embedded Dashboards

Power BI reports embedded in SharePoint load within the SharePoint page context, which means they compete with other web parts for page load time. Slow dashboards degrade the entire page experience and drive users away. Optimization is essential.

Data Model Optimization

• Use Import mode over DirectQuery — Import mode loads data into the Power BI model, resulting in sub-second query performance. DirectQuery sends queries to the source database on every interaction, which can take seconds per visual. Use DirectQuery only when data must be real-time and the source database is optimized for analytical queries.
• Create aggregation tables — For large datasets (millions of rows), create pre-aggregated summary tables for dashboard-level metrics. Detailed data remains available for drill-through but does not slow down the initial dashboard load.
• Remove unused columns and tables — Every column in the data model consumes memory. Remove columns that are not referenced by any visual or calculation.
• Optimize DAX measures — Complex DAX measures that iterate row-by-row (SUMX, FILTER) are slower than simple aggregations (SUM, AVERAGE). Evaluate whether complex measures can be pre-calculated in the data source.

Report Design Optimization

• Limit visuals per page to 8-10 — Each visual generates a separate query. Pages with 15+ visuals create visible loading delays. Split complex dashboards across multiple pages with clear navigation.
• Use bookmarks for state management — Instead of multiple similar pages, use bookmarks to toggle between views (e.g., monthly vs. quarterly, by region vs. by product).
• Configure initial filter state — Set default filters to show the most relevant data (current month, user's region) to reduce the initial data volume rendered.
• Enable query caching — In Power BI Premium, query caching stores results for reuse across users, dramatically improving load times for shared dashboards.

Mobile-Responsive Dashboard Design

SharePoint pages are responsive, and the Power BI web part adapts to the page width. However, Power BI report visuals do not automatically reflow for mobile screens — you must design a mobile-specific layout in Power BI Desktop. The mobile layout designer in Power BI Desktop lets you arrange visuals for portrait orientation on phone screens. Best practices include prioritizing the most important KPIs at the top of the mobile layout, using card visuals and KPI visuals that are readable at small sizes, minimizing the use of tables and matrices (which require scrolling on mobile), and ensuring slicer selections are touch-friendly with large tap targets.

For organizations using Viva Connections, Power BI data can also be surfaced through adaptive cards on the Viva Connections dashboard — providing quick KPI snapshots without loading a full report.

Alternative: SharePoint Native Dashboards

Not every dashboard needs Power BI. SharePoint provides native dashboard capabilities that work well for operational metrics and simple KPIs. SharePoint list formatting uses JSON to apply conditional formatting, color coding, and progress bars to list views. This is ideal for project trackers, status dashboards, and simple KPI lists. The Quick Chart web part creates basic bar and pie charts directly from SharePoint list data — no Power BI license required. Power Apps embedded in SharePoint via the Power Apps web part can display formatted data from SharePoint lists, Dataverse, or external APIs with custom layouts.

EPC Group recommends native SharePoint dashboards for operational lists (project status, task tracking, approval queues) and Power BI for analytical dashboards (financial reporting, sales analytics, executive KPIs, anything requiring data from multiple sources or complex calculations).

Governance for Embedded Dashboards

Dashboard embedding creates governance considerations that must be addressed. Data access governance requires ensuring that embedding a report in SharePoint does not inadvertently expose data to users who should not see it — RLS is essential. Report lifecycle management means establishing processes for updating, versioning, and retiring embedded reports so users are not viewing stale data. Performance monitoring involves monitoring embedded report load times and query performance using Power BI Premium metrics (if available) or user feedback. Licensing compliance means tracking which users access embedded reports to ensure proper Power BI licensing and avoid compliance issues.

EPC Group includes dashboard governance as part of every SharePoint implementation and Power BI engagement, ensuring that embedded analytics are secure, maintained, and properly licensed.

Why EPC Group for SharePoint Dashboard Integration

EPC Group brings unique depth to SharePoint dashboard integration because we have dedicated practices in both Power BI consulting and SharePoint consulting. Most firms have separate teams for BI and collaboration — at EPC Group, our consultants work across both platforms to deliver integrated solutions. Our founder Errin O'Connor is the author of the Microsoft Press Power BI bestseller, and our team has delivered enterprise BI and SharePoint implementations for Fortune 500 organizations across healthcare, finance, and government.

Frequently Asked Questions