The SharePoint Site Sprawl Problem
Diesen Beitrag auf Deutsch lesen
Why self-service site creation trades an IT bottleneck for a retirement problem, and how to pair creation policy with lifecycle reviews from day one.
TL;DR
Self-service site creation removes IT bottlenecks but makes retirement the hard part: sites pile up with unclear owners and no activity for years. The fix isn’t blocking creation — it’s naming conventions and sensitivity levels set upfront, plus regular ownership reviews that catch sites whose owner has left the company.
Original by Josiah Opiyo, on Microsoft 365 & Power Platform Community Blog. Read the original
This is our own summary, not a republication or full translation.
Governance takeaway
- Admins/CoE: pair any self-service creation policy with a recurring ownership-attestation review from day one — retiring an orphaned site years later costs far more than checking ownership quarterly.
- Makers: spinning up a new site, app, or environment should set naming conventions and sensitivity levels at creation time, not after governance comes looking for it.
- Leadership/Business: read sprawl as a lifecycle-cost problem rather than a request-friction one — blocking creation doesn’t fix it, but skipping lifecycle review guarantees it.
Frequently asked questions
Why is uncertainty the real problem with many SharePoint sites?
Because as sites multiply, basic questions stay unanswered: where does content belong, who owns the site, is the content still relevant, who has access, and is there a duplicate space for the same purpose?
What causes sprawl in SharePoint even though IT wants to avoid it?
Self-service creation was introduced to avoid IT bottlenecks. Creating is easy while retiring is hard.
Does a high number of SharePoint sites automatically mean poor governance?
No. A large number of sites says nothing about quality on its own.