Episode Details
Back to Episodes
SharePoint Cleanup Strategy: The Blob Storage Fix for Hoarding and Bad Search
Season 1
Published 5 months ago
Description
(00:00:00) SharePoint's Confidence Illusion
(00:00:14) The Relevance Problem in SharePoint
(00:00:32) The Dangers of Duplicate Files
(00:01:39) Governance Beyond Checkboxes
(00:02:46) The Warehouse District Solution
(00:06:50) The Permission Puzzle
(00:09:24) The Delegated "On Behalf Of" Model
(00:12:35) The Three-Step Offload Process
(00:19:11) Measuring Success and Scaling Up
(00:21:15) Key Takeaways and Call to Action
In this episode of M365.fm, Mirko Peters shows how to stop SharePoint from behaving like a digital landfill — without starting a political war over deleting files. If your environment is full of Final_v7 documents, fake “Archive” folders, and confused users opening the wrong version every day, this conversation gives you a concrete, admin‑ and security‑approved pattern: offloading stale drafts and duplicates from SharePoint to Azure Blob Storage with a full audit trail and one‑click restore.
WHAT YOU WILL LEARN
SharePoint doesn’t hurt your users because it runs out of space; it hurts them because it loses signal. When every draft, duplicate, and “just in case” copy lives forever in the same libraries, your ranking signals collapse: search, Copilot, and even manual browsing star
(00:00:14) The Relevance Problem in SharePoint
(00:00:32) The Dangers of Duplicate Files
(00:01:39) Governance Beyond Checkboxes
(00:02:46) The Warehouse District Solution
(00:06:50) The Permission Puzzle
(00:09:24) The Delegated "On Behalf Of" Model
(00:12:35) The Three-Step Offload Process
(00:19:11) Measuring Success and Scaling Up
(00:21:15) Key Takeaways and Call to Action
In this episode of M365.fm, Mirko Peters shows how to stop SharePoint from behaving like a digital landfill — without starting a political war over deleting files. If your environment is full of Final_v7 documents, fake “Archive” folders, and confused users opening the wrong version every day, this conversation gives you a concrete, admin‑ and security‑approved pattern: offloading stale drafts and duplicates from SharePoint to Azure Blob Storage with a full audit trail and one‑click restore.
WHAT YOU WILL LEARN
- Why your SharePoint and Copilot results feel “wrong” even though search and indexing are technically working
- How duplicates, pseudo‑archives, and friendly hoarding distort ranking signals and bury the real canonical document
- Why you don’t have a storage problem — you have a relevance and governance problem
- How a simple architecture fixes it: an SPFx ListView Command Set for “Move to Blob,” an Azure Function that copies files server‑to‑server, Azure Blob Storage as the warehouse, and Azure Table Storage as the immutable ledger
- Why delegated auth with On‑Behalf‑Of flow passes security review, and why global application permissions don’t
- How to build practical identification rules for duplicates and stale drafts using hashes, last access, edit frequency, and age
- How the move process actually works: copy → hash verify → ledger entry → delete, with SharePoint recycle safety
- How one‑click restore rehydrates files (with metadata) so users stop fearing cleanup and start trusting the system
- The measurable payoff: better search precision, cleaner Copilot answers, lower storage costs, and fewer “Which version is the right one?” arguments
SharePoint doesn’t hurt your users because it runs out of space; it hurts them because it loses signal. When every draft, duplicate, and “just in case” copy lives forever in the same libraries, your ranking signals collapse: search, Copilot, and even manual browsing star