Storage Metrics

The Storage Metrics tab provides a detailed breakdown of how storage is consumed across a SharePoint Online site. It identifies which document libraries and folders are using the most space, how much is consumed by version history, and when content was last modified.

What Is Measured

The version size metric is particularly useful for identifying libraries where version history has been allowed to grow unchecked, consuming significant quota.

Options

Folder Depth

⚠️ Note: Higher folder depth settings require more API calls and take longer to complete. A depth of 1 or 2 is sufficient for most use cases.

Include Sub-Sites

When enabled, the tool scans all sub-sites beneath the selected site and appends their library data to the report. Each entry is prefixed with the sub-site URL.

Running the Analysis

1. Connect (see Connection and Profiles).
2. Switch to the Storage Metrics tab.
3. Set the folder depth (0 = library-level only).
4. Optionally enable Include sub-sites.
5. Choose CSV or HTML output.
6. Click Analyze.

Output Formats

CSV

UTF-8 with BOM, semicolon-delimited. Filename pattern: Storage_<SiteName>_<YYYYMMDD>.csv

Columns: SiteUrl, Library, FolderPath, TotalSizeMB, VersionSizeMB, ItemCount, LastModified

HTML

The HTML report is a self-contained interactive document including:

• Summary charts — bar charts showing total size and version size per library
• Collapsible folder tree — click a library or folder to expand/collapse its children
• Sortable table — click column headers to sort by size, count, or date
• Color coding — libraries where version size exceeds a threshold are highlighted in amber

Filename pattern: Storage_<SiteName>_<YYYYMMDD>.html

Interpreting the Results

Identifying Storage Hogs

Sort the table by Total size (MB) descending. The top entries are your largest consumers. Cross-reference with Item count to determine whether a library is large due to many small files or few large files.

Understanding Version Bloat

A high Version size relative to Total size indicates that a library's version history policy is not configured optimally. Consider:

• Setting a maximum number of major versions (e.g., 10–50) on large libraries.
• Running a version cleanup script using PnP.PowerShell.

Stale Content

The Last modified column highlights libraries that have not been touched in a long time. These may be candidates for archiving or deletion after review with content owners.

Tips

• Use folder depth 1 to find which top-level folders inside a library drive the most usage.
• Combine with the Permissions Report to identify large, stale libraries with overly broad permissions.
• The CSV output can be loaded into Power BI to build tenant-wide storage dashboards.