TechRam For IT Leaders
How do you keep track of SharePoint sites, owners and storage?
Tracking a SharePoint estate means four numbers per site: who owns it, how much it holds, when it was last active, and whether anything in it is shared externally. Together they say which sites to keep, which to archive and which nobody has opened in two years.
Why sprawl is structural, not cultural
Every Teams team creates a SharePoint site. Every private channel creates another. Every project that needed somewhere to put files created one, and the person who created it moved on.
Nobody decided to have four hundred sites. Creating one is a single click with no approval step, and owning one confers no authority and appears in no job description. The incentives produce sprawl reliably, and telling people to be tidier doesn’t change them.
The four numbers
One row per site, four columns. Anything else is detail you can add later.
| Number | The question it answers |
|---|---|
| Owner | Who decides what happens to this |
| Storage | What it costs to keep |
| Last activity | Whether anyone still uses it |
| External sharing | Whether anything in it is reachable from outside |
Owner and last activity are the two that make decisions possible. Storage is what makes the decision worth taking. External sharing is what makes it urgent.
Reading the four together
Active, owned, no external links. Leave it alone. This is the majority and it’s fine.
Active, no owner. The most common real problem. Somebody is relying on this and nobody is accountable for it. Name an owner; that’s the whole fix.
Inactive, large. Archive candidates. Read the storage number next to the last-activity date and the case makes itself.
Inactive with live external links. Deal with these first regardless of size. A link into a site nobody is watching is the exposure that doesn’t announce itself.
The part people skip
Producing the list once is a project. Producing it monthly is the thing that matters, because the four numbers are only useful as a trend.
A site that grew 40% this month is a different conversation from one that is merely large. A site that went inactive last month is easy to archive; one that went inactive three years ago has accumulated defenders who will tell you they might need it.
So the deliverable isn’t the list. It’s the monthly report and a named person who reads it, which is what a Run & Improve engagement covers and what a one-off cleanup doesn’t.
Where to start
The Site Governance Dashboard puts the four numbers on one Power BI page you can send to an executive without annotating it. Ask for it on the page and we’ll send the package and the setup notes.
If you would rather have the read done properly across the whole tenant, including the permission model behind the external sharing column, that’s the Environment Baseline.
The service behind this: Run & Improve →
Common questions
01. Why does SharePoint site sprawl happen at all?
Every Teams team creates a site and every private channel creates another. Creating one is a single click with no approval step, and owning one confers no authority and appears in no job description. The incentives produce sprawl reliably, so telling people to be tidier does not change them.
02. Which four numbers do you need per site?
Who owns it, how much it holds, when it was last active, and whether anything in it is shared externally. Owner and last activity make decisions possible, storage makes the decision worth taking, and external sharing makes it urgent.
03. Which sites should you deal with first?
Inactive sites with live external links, regardless of size. A link into a site nobody is watching is the exposure that doesn't announce itself.
04. Is producing the list once enough?
No. The four numbers are only useful as a trend — a site that grew 40% this month is a different conversation from one that's merely large. The deliverable is the monthly report and a named person who reads it.