Decompose your volume down to the files — interactively, from any angle
The Files page answers one question from every direction: where is the volume, and which files make it up? Total volume sits at the centre of the analysis, beside file count and version count. You decompose it by whatever matters and, because the grain of the model is the file, every path you follow ends at the actual files — ready to export and migrate. You drive all of it by clicking: there is no query language and nothing to write.
—-
The Decomposition Tree — follow the volume
The Decomposition Tree is the main tool. Put a measure at the centre — Total Volume MB (or version count, or file count) — and break it apart one level at a time, in any order you choose: by source and folder path, by job run, by file type, by volume / version / age bucket, by sensitivity or retention label, by content type. At each node Power BI can suggest the most revealing next split (the AI split), or you pick. Keep expanding down the heaviest branch until the files that explain the number are in front of you.
★ Use it when you don’t yet know where the answer lives. You are not building a report — you are following the volume down until the cause is exposed: the one library, the one owner, the version bloat, the dormant content.
A Tree Map gives the same weighting at a glance — proportional rectangles, biggest = most volume — when you want the overview before you drill.
—-
Slice by anything — every metadata column, every job
The page carries slicers for everything: file status / result, job type and job run (Run History), source and destination, sensitivity and retention labels, the volume / version / age buckets — and any custom SharePoint metadata column in your tenant, through the cascading ColumnName → ValueText slicers (powered by the cg_FileMetadata view). Pick Department, then Finance, and the entire page re-filters to that set.
Every selection cross-filters the whole page. Select three file types and everything narrows to those three; click a single slice of a chart and the page — including the file list — shows only those files; combine slicers to corner exactly the set you want.
★ Multi-value columns are first-class citizens. A file whose
Tagscolumn holds"Finance; Legal; Audit"counts under each of those values when you slice — no string-matching, noLIKE %Finance%workarounds.
—-
The File details table — the files in focus
The File details table is the per-file view of whatever is currently in focus. As you decompose and slice, it always lists the actual files behind the current selection — not aggregates, the files themselves.
For that set it reports the three numbers the whole report turns on: how many files, how many versions they hold between them, and their total volume. So at any point — for exactly the slice you are looking at — you can read the file count, the version load and the size side by side.
Each row also carries a link to that file’s Run History item in Microsoft Teams. With access to the team you can click straight through to the run that produced the file, and on to the job behind it, to review, modify or re-run it.
ℹ When a file was changed in the source after it had already been migrated, its row is highlighted yellow — your delta-migration candidates, visible at a glance. See File status & the run-history model for how this is detected.
From the files in focus to a migration. Once the table holds the right files, export it to CSV with the button at the top-right of the table. That CSV becomes the input to a Multi-Source Migration — the files you isolated by analysis, gathered from wherever they live across SharePoint, OneDrive and FileShare, and migrated to a single destination. See Multi-Source Migration for the full procedure.
—-
Look up one file
Right-click any file row, chart slice, tree-map rectangle or decomposition node → Drill through → Single File to see everything the database knows about that one file: identity and full path, current status and whether the source changed since migration, sizing and version counts, all labels, every metadata value, and its complete action history. Each Run History entry there links straight into Microsoft Teams, where — with access to the team — you can open the job behind it to review, modify or re-run it.
—-