Pin a Tile to a Power BI Dashboard from Excel - What Actually Works

Almost every finance team we work with has a spreadsheet that the leadership team loves more than any dashboard. Somebody built a tidy summary tab three years ago, it still works, and now the CFO wants it sitting next to the sales numbers on the Monday dashboard. Copy and paste holds for about a week. Then the numbers drift, somebody sends a screenshot to the board, and nobody can say which version is right.

Power BI has a feature that lets you pin ranges straight from an Excel workbook onto a dashboard. It's genuinely useful, and for the right job it saves a lot of pain. It's also less magic than the marketing suggests. Here's what we've seen work, what trips people up, and when I'd still push a team towards a proper semantic model instead.

Get the workbook somewhere Power BI can see it

Pinning doesn't work from a file sitting on someone's desktop. The workbook needs to live in OneDrive for work or school, or in another group-shared document library, and you connect it to the Power BI service from there. In practice that means uploading the file to OneDrive, going to My workspace in Power BI, choosing Upload, then OneDrive - Business, and picking the file.

What you get is a linked, read-only version of the workbook inside Power BI. You can sort and filter it in the browser, but those changes don't save back to the file and can't be pinned. If you need to change something, select Edit in the top right. That opens the workbook in Excel Online or desktop Excel, and your changes save back to OneDrive. Tiles take a few minutes to catch up.

My view: this is the step people skip, and then they wonder why the dashboard looks stale. The tile reflects the saved workbook, not whatever you were looking at in the browser ten minutes ago.

Pinning a range

Highlight the cells you want. Select the pin icon. Choose an existing dashboard from the dropdown, or type a name to create a new one. Select Pin, and a confirmation appears in the top right. Select Go to dashboard and you're there.

The range can include plain data, charts, tables, PivotTables, PivotCharts and other Excel objects. You can also pin an entire worksheet if the layout is already presentation-ready.

Clicking the tile opens the linked workbook in Power BI, which means the viewer needs read access to the file on the owner's OneDrive. Anyone without permission gets an error. This catches out executives all the time. They get sent the dashboard link, click the tile, and get locked out because nobody shared the workbook with them. Sort out the sharing before you send the dashboard round, not after the first complaint.

Tables and PivotTables

Pinning a table or PivotTable follows the same steps, with one thing to get right. For a table, select the whole range and include the headers. For a PivotTable, include every visible part of it, including any filters you've placed above the grid.

The tile then shows the entire table, and changes in the source flow through. Add a row to the workbook and it appears on the dashboard. Filter the source and the tile filters too. That's the appeal. It's also where the surprises come from. We've seen someone sort a table in Excel to make it read better before a meeting, and the dashboard changed overnight without anyone noticing.

Our rule is simple. Pin from a sheet built for presentation, not from the analysis tab with twelve helper columns and three scratch calculations. If you need a clean view for the dashboard, build a summary sheet whose only job is to feed the tiles. It takes ten minutes and saves a lot of "why does this number look different?" messages.

A worked example

One client had a sales pipeline workbook that the sales ops lead maintained by hand every Friday. The leadership team wanted three things on the dashboard: total pipeline by stage, the weighted forecast for the quarter, and a table of the top twenty deals. We pinned the stage summary as a range, the forecast as a single cell range with a large font, and the top twenty as a table.

It worked well for about six weeks. Then the sales ops lead started sorting the top twenty table by close date to check something, forgot to sort it back, and the dashboard showed a different top twenty for a fortnight before anyone spotted it. The fix wasn't technical. We moved the top twenty calculation onto a dedicated sheet with formulas that sort it automatically, and locked the layout. The lesson stuck with us: the more hands touch a source, the more the dashboard becomes a function of human habit.

What won't show up

Power BI renders workbook tiles using Excel Services. Some Excel features aren't supported in the Excel Services REST API, so they won't appear on the tile even though they look fine in the workbook. Microsoft's documentation calls out sparklines, icon set conditional formatting and time slicers in particular.

We've had teams build a lovely KPI row with arrow icons, then wonder why the arrows disappeared on the dashboard. The formatting was correct in Excel. It just doesn't carry across. If you're designing a tile specifically for the dashboard, swap the icon sets for plain coloured cells or text indicators, and test the result in the service rather than trusting the sheet preview.

Test every tile before you show it to anyone. Pin it, open the dashboard, click through to the workbook, and look at what came out the other side. It takes two minutes and it's the most useful habit I can recommend here.

Where this fits and where it doesn't

For a one-off leadership view, or a small team that already lives in Excel and wants a few numbers on a shared dashboard, pinning from Excel is a sensible move. It costs nothing extra, the people involved already know the tool, and it stops the screenshot emails going around the building.

It's a poor foundation for anything that needs to grow. Once the workbook has forty tabs, a dozen people editing it, and data arriving through a manual export every Tuesday, you're maintaining a fragile reporting process with a shiny front end. At that point I'd rather move the data into a semantic model in Microsoft Fabric or Power BI, with the Excel logic rebuilt as measures and the source refreshed automatically. It takes longer up front. It saves a great many Monday mornings afterwards.

The question I'd ask before pinning anything is this: who updates the source, and how will they know the dashboard depends on them? If the honest answer is "nobody has thought about it", you've got a process problem to solve before you've got a dashboard problem.

A quick checklist

• Store the workbook in OneDrive for work or school, or a group-shared library. Never on a laptop.
• Confirm that everyone who will click through has read access to the workbook.
• Pin from a presentation sheet, not a working sheet.
• Avoid sparklines, icon sets and time slicers if the tile needs to match what people see in Excel.
• Check the tile after your first edit, and again a few minutes later, since the refresh isn't instant.
• Write down who owns the source file and who to call when the numbers look wrong.

If you're not sure whether a workbook is ready for a dashboard or needs rebuilding first, our Power BI consultants see this question constantly. For larger reporting estates, the Microsoft Fabric team can help plan the move from spreadsheet to a governed semantic model.

The original reference is Microsoft's How to pin a tile to a Power BI dashboard from Excel. It's short, and worth reading alongside this if you're setting it up for the first time.