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.
Posted 
Governance card about site and environment sprawl from self-service creation.
By Power Platform Governance
1 min read
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.
This post is licensed under CC BY 4.0 by the author.