Measure Killer Measure Killer

Find what your Excel users are consuming from your semantic model

Once you've identified the Excel users of a Power BI semantic model, collect their .xlsx files and drop them into Measure Killer to see exactly which columns and measures they reference.

What you get

For every Excel file added to the analysis, Measure Killer tells you exactly which columns and measures from the semantic model that workbook is using. The Excel file appears in the usage tree alongside Power BI reports and Paginated reports, so a column flagged as “unused” really means unused — not “unused in reports but pulled into someone’s pivot table”.

Prerequisite — identify the users first

This page assumes you already have the list of Excel users from the previous step. If you don’t, start there: Identify Excel users of a Power BI semantic model. The activity log gives you names; this step needs the actual files.

Collect the Excel files

The activity log tells you who is connecting, not what’s in their workbook. To analyse the contents, you need the file itself. Two practical routes:

  1. Ask the users directly — send the list from the previous step and ask them to share their working files (or the OneDrive / SharePoint links).
  2. Pull from the tenant — if the files live in a managed SharePoint / OneDrive location, your tenant admin can fetch them centrally.

Live “Analyze in Excel” workbooks without local data still work — Measure Killer reads the connection definition and the PivotTable fields. Refreshed workbooks where someone has imported the data into the worksheet won’t show up as connected and won’t help here.

Add the files to the analysis

  1. Open Measure Killer in a mode that analyses the semantic model — typically Shared model online (for a model in the Power BI Service) or Single model and report (for a local file).
  2. Load the semantic model as you normally would.
  3. Drag the .xlsx files into the Measure Killer window, or use Load a file and select them.
  4. Run the analysis.

Each Excel file is added to the dependency tree as its own connected artifact, just like a .pbix report.

Read the results

In the execution log / selection view you’ll now see Excel files listed next to the regular Power BI reports for the same semantic model — with Views, Opens and Avg. Load (s) populated where the activity log has data, plus a Workspace tag (or Local File for files added from disk).

Combine that with Measure Killer’s standard column- and measure-level usage output: any column or measure used by at least one Excel file gets the same “used” status as if it had been referenced from a Power BI visual — so cleanup decisions for the model factor in Excel consumption automatically.

Common workflows

  • Pre-cleanup confirmation — before deleting a column the reports don’t use, add the active Excel files and confirm none of them depends on it.
  • Migration planning — when consolidating two models, see which Excel workbooks point at which model and which fields are at stake.
  • Audit “shadow” usage — measure how much business analysis lives in Excel rather than in governed reports, then decide whether to migrate it.

Limitations

  • Workbooks where users copy/pasted values out of a refreshed connection can’t be detected from the file alone — the live connection is what Measure Killer reads.
  • Files protected by sensitivity labels that block local opening can’t be parsed on the desktop tool — see Trust & security for the same caveat that applies to .pbix analysis.