Pinning an Entire Report Page to a Power BI Dashboard - When Live Page Tiles Make Sense
Here's a conversation I've had more than once with a CFO or operations manager. They've got a Power BI report they love. One page in particular, the summary page, is the thing they check every morning. They want it on their dashboard, but when someone on their team pinned the visuals one at a time, the dashboard ended up looking like a jigsaw puzzle with half the pieces missing. The slicers didn't come across. The layout was wrong. Something felt off.
The fix is usually simple: pin the entire report page as a single live tile instead of pinning visuals individually. It's a feature that's been in Power BI for years, and plenty of people still don't know it exists.
This post covers how it works, what you gain and lose, and when I'd use it. Microsoft's documentation is Pin an entire report page to a dashboard if you want the official steps.
Visual tiles versus live page tiles
When you pin a single visual from a report, you get a tile on the dashboard that shows that one visual. It reflects the filters that were applied at the time you pinned it, and clicking it takes you to the report. It's static in the sense that you can't interact with it on the dashboard. You look at it, and if you want to do anything, you click through.
When you pin a whole page, you get what Microsoft calls a live tile. The entire page shows up as one tile, layout and all. And unlike visual tiles, the live page tile is interactive. Slicers on the page work inside the tile. You can change a slicer selection right there on the dashboard and the page updates. Cross-filtering between visuals works too.
The other big difference is how changes flow through. If the report author edits the page (adds a visual, rearranges things, changes a colour), the live tile picks up those changes. With individually pinned visuals, if someone changes or deletes the source visual, the dashboard tile can end up stale or broken.
How to do it
The steps are straightforward in the Power BI service:
- Open the report in the Power BI service (not Desktop, pinning only happens in the service).
- Go to the page you want to pin.
- From the menu bar, select the More options (...) menu and choose Pin to a dashboard.
- Choose whether to pin to an existing dashboard or create a new one.
- Select Pin live.
A confirmation appears in the top right, with a link to go to the dashboard. The tile lands on the dashboard and you can resize and move it like any other tile.
You need edit permissions on the report to pin from it. If the report has been shared with you as a read-only viewer, the pin option won't be there. This trips people up when an analyst builds a report, shares it with a manager, and the manager wants to build their own dashboard from it. The usual answer is for the analyst to do the pinning, or for the manager to get build or contributor access in the workspace.
What we've seen work
Executive summary dashboards that combine sources. The best use of dashboards in Power BI, in my opinion, is pulling together pieces from several different reports into one place. A live page tile from the sales report sits next to a couple of visual tiles from the finance report and a KPI from the operations report. You get one screen that cuts across datasets, which a single report can't easily do.
A manufacturing client in Melbourne does exactly this. Their plant manager's dashboard has a live tile of the production summary page (with a working shift slicer), plus individual tiles from the quality report and the maintenance report. Three different semantic models, one view. That's the scenario where dashboards still earn their keep.
Pages designed as compact summaries. Live page tiles look best when the page itself is designed for it. A page with four or five key visuals and a slicer or two, laid out cleanly, reads well as a tile. A dense analytical page with fifteen visuals and tiny tables becomes unreadable once it's squeezed into a dashboard tile.
Keeping the dashboard in sync with the report. If the report is still evolving, a live page tile means you don't have to keep re-pinning visuals every time the author tweaks something. That's a real time saver during the first few months of a reporting rollout, when feedback is coming in weekly.
What to watch out for
The tile is the size of the tile. A full report page shrunk into a dashboard tile is small. You can resize the tile larger, but on a dashboard that's competing with other content, you'll often find the text gets hard to read. Design the source page with that in mind: bigger fonts, fewer visuals, clear titles.
Some dashboard features don't apply. Things that work on individual visual tiles, like data alerts on card and KPI tiles, aren't available on a live page tile. If someone wants an email when revenue drops below a threshold, they'll need a separate card visual pinned on its own for that alert.
Filters at pin time. When you pin a page, the tile reflects the filter and slicer state of the page. Users can then change slicers in the tile itself. It's worth deciding before you pin what the "default" view should be, because that's what people will see first.
Dashboards themselves are a bit of a legacy feature. I'll be honest here. Microsoft hasn't put a lot of investment into dashboards in recent years. The focus has been on reports, apps, Fabric and Copilot. Dashboards still work, and they're still the only way to combine content from multiple reports into one canvas without rebuilding, but I wouldn't build a whole reporting strategy around them in 2026. For many organisations, a well-designed Power BI app with a clear landing report does the job better, and it's easier to manage.
Where dashboards still make sense: cross-report summary views, mobile-friendly overviews for executives, and teams that already have a dashboard habit and don't want to change. For those, live page tiles are the best way to get report content onto the dashboard.
Mobile layout. Dashboards have their own phone view, and live page tiles behave differently on small screens than individual visual tiles. Test on an actual phone before you announce the new dashboard to the leadership team. I've been caught out by this before, and it's never fun when the CEO messages you a screenshot of something unreadable.
Live page tile or just share the report?
This is the real question. If the dashboard is going to contain nothing but one live page tile, you don't need a dashboard. Just share the report, or put it in an app and set that page as the landing page. A dashboard with one live tile is an extra layer of navigation for no gain.
If you're combining that page with content from other reports, or you want the dashboard's specific features (like the mobile phone view or pinned Q&A results), then pinning the page as a live tile is the right move.
My rule of thumb: dashboards are for combining. Reports are for exploring. Live page tiles are the bridge between the two when one report page is the thing everyone needs to see first.
Getting reporting right
The mechanics of pinning are easy. The harder part is designing reports and dashboards that people actually open every day. That comes down to understanding what decisions each audience is making and building for those decisions, rather than putting every metric on screen because it's available.
If you're working through a Power BI rollout and want help designing the reporting layer, our Power BI consultants do this kind of work regularly. We also help with broader business intelligence and AI projects where Power BI is one piece of a larger data platform.