A mature Microsoft 365 tenant does not just accumulate sites: it manages them from creation through to deletion. Without that discipline, you end up with hundreds of orphaned sites, wasted storage quota, broken permissions, and content no one can find or vouch for. The four-phase lifecycle below gives you a repeatable framework.
| Phase | Goal | Key tool | Frequency |
|---|---|---|---|
| 1. Provision | Create sites with a named owner and a defined purpose from day one | SharePoint admin centre site creation policy | Per-request |
| 2. Monitor | Identify sites approaching end of active use before they become orphaned | Active sites export / M365 usage reports / inactive site policy | Quarterly |
| 3. Archive | Retain content at reduced cost for compliance or future reference | Microsoft 365 Archive | Per-decision |
| 4. Decommission | Remove sites with no active content or business value | SharePoint admin centre / Space Master bulk delete | Per-decision |
What is SharePoint site lifecycle management?
SharePoint site lifecycle management is the process of governing a site from creation to deletion: setting creation standards, monitoring for inactivity, archiving sites no longer actively used, and decommissioning sites whose content no longer serves a business need. Without a lifecycle policy, tenants accumulate orphaned sites that waste storage, pollute search results, and create permission risk for data that nobody is actively governing.
Microsoft 365 provides several built-in tools to support lifecycle management: the SharePoint admin centre, Microsoft 365 Archive, and, with SharePoint Advanced Management (included with Microsoft 365 Copilot licences), site ownership, inactive site and site attestation policies. The four phases below show how to put them to work.
Phase 1: Provisioning sites consistently
Governance problems usually start at creation. A site created without a named owner, a clear purpose, or a naming standard is difficult to manage from day one. Getting provisioning right is cheaper than cleaning up later.
Controlling who creates sites
By default, any Microsoft 365 user can create SharePoint team sites and communication sites, which generates unchecked sprawl in most organisations. You have two practical options.
- Restrict self-service creation. In the SharePoint admin centre, go to Settings > Site creation and clear Users can create SharePoint sites. That stops site creation from SharePoint and OneDrive, but not the creation of Microsoft 365 groups (each of which gets a team site) from Teams or Outlook; restricting those is a separate Microsoft 365 group creation setting. Route site requests through a form or approval workflow so that an admin or designated approver can verify the business need before a site is created.
- Require an owner and a purpose at creation time. Whether creation is open or gated, ensure every new site has a primary admin who is a current employee (not a shared mailbox or former employee) and a short description of what the site is for. This metadata is your primary triage signal in Phase 2.
Teams-connected SharePoint sites are created whenever someone creates a new Microsoft Teams team. If your organisation allows open Teams creation, you are implicitly allowing open SharePoint site creation. Apply the same governance policy to both.
Applying naming conventions and sensitivity labels at creation
A consistent naming convention makes sites findable and auditable. A format like [Department]-[Project]-[Year] produces site names that immediately communicate scope and age. Sensitivity labels applied at creation drive default sharing and access settings automatically, reducing the risk that a new site is created with overly broad external sharing before anyone has a chance to review it.
Every SharePoint site that exists but serves no owner, no team, and no business process is a governance liability. The lifecycle framework converts that liability into a deliberate decision.
Phase 2: Monitoring and reviewing active sites
Identifying sites that are drifting toward inactivity before they become orphaned is less work than cleaning up after they already are. A quarterly review cadence works for most organisations.
Identifying inactive sites
The SharePoint admin centre provides a last-activity column on the Active sites view, and Microsoft 365 usage reports include a 180-day site activity export. Both surfaces show you which sites have had no file interactions in the selected period. The detailed guide on finding inactive SharePoint Online sites walks through both methods step by step, including how to interpret the data and what to do with borderline cases.
Key signals to watch across your active site list:
- No file activity in 90 or more days, combined with a site owner who has left the organisation
- Sites consuming more than 10 GB of storage with no activity in the past year
- Sites with no sensitivity label and external sharing enabled but zero external user activity
- Sites created more than two years ago with no recorded owner review
Running a quarterly site review
On the Active sites page, select Export to save the list as a CSV with last activity, storage used and primary admin for every site. You can sort by last activity, filter to sites above a storage threshold, and cross-reference the primary admin column against your active employee list. With SharePoint Advanced Management, a site ownership policy and an inactive site policy in simulation mode give you owner counts and a wider activity measure in their reports, and in active mode they run monthly without you.
Run the export at the start of each quarter. Keep the previous quarter's file alongside the new one so you can see which sites have moved from active to inactive since the last review. For the storage side, ShareMaster's Tenant Storage Metric report breaks each site's usage down by library and shows how much of it is version history.
See what Report Master exports
Phase 3: Archiving sites that have reached end of active use
Not every inactive site should be deleted. Some contain content required for compliance, ongoing legal matters, or possible future reference. Microsoft 365 Archive provides a cost-efficient way to retain these sites without consuming your active storage quota.
When you archive a site:
- The site is no longer directly accessible to anyone. It keeps its content, metadata and permissions, but users cannot open it until it is reactivated.
- Its storage moves from active storage to archive storage. Microsoft lists archive storage at $0.05 per GB per month, and only charges for it once active plus archived storage exceeds your tenant's quota.
- Admin search, Purview content search and eDiscovery still reach the content, and Microsoft states that archived content isn't used by Microsoft 365 Copilot.
- Only a SharePoint or Global Administrator can reactivate it, from Archived sites in the SharePoint admin centre.
If people still need to read the content, set the site to read-only instead; that keeps it browsable but saves no storage.
Archive is the right choice when the site has a designated owner (or a compliance reason that substitutes for one), when you cannot confirm that deletion is safe, or when a legal hold or retention label prevents deletion. For the full step-by-step process, see the guide on archiving SharePoint sites with Microsoft 365 Archive.
Record every archiving decision in a governance log: the site URL, the reason for archiving, the date, the approver, and the expected review date. A log entry costs almost nothing; reconstructing that context six months later when someone asks why a site is read-only costs a significant amount of admin time.
Phase 4: Decommissioning and deleting sites
Deletion is appropriate when a site has no active content, no compliance hold, and stakeholders have given explicit sign-off. Deleted sites sit in the admin recycle bin for 93 days and can be restored during that window - after that, the content is gone permanently.
- Confirm no retention policy, label or hold applies. In the Microsoft Purview portal, check retention policies, retention labels and eDiscovery holds that cover the site. SharePoint blocks deleting a site that a compliance policy is holding, with the message that a compliance policy is blocking the deletion.
- Notify and collect approval from the site owner or their manager. Email approval from the person responsible for the site content provides a defensible audit trail if questions arise later.
- Run a final permissions report. Before deleting, export the site's permissions to confirm no external users retain access to content that will persist in the admin recycle bin for 93 days. The SharePoint permissions audit guide covers how to do this efficiently across multiple sites.
- Delete through the SharePoint admin centre. Select the site in Active sites and choose Delete. The site moves to the admin recycle bin immediately and is restorable for 93 days.
- Bulk delete with Space Master for large clean-up runs. When you are decommissioning dozens of sites in a single project, Space Master's Bulk Delete Sites removes a whole selection in one pass rather than one at a time through the admin centre UI. Run it with an account holding both SharePoint Administrator and Groups Administrator; each removed site is still restorable from Deleted sites within the usual 93 days.
- Record the deletion in your governance log. Note the site URL, deletion date, approver, and whether any content was exported or transferred before deletion.
Frequently Asked Questions
What is SharePoint site lifecycle management?
SharePoint site lifecycle management is the process of governing a site from creation through to deletion. It covers setting creation standards, monitoring for inactivity, archiving sites that are no longer active but must be retained, and decommissioning sites whose content no longer serves any business need. Without a lifecycle policy, tenants accumulate orphaned sites that waste storage, pollute search results, and introduce permission risk.
When should you archive a SharePoint site instead of deleting it?
Archive when the site is inactive but the content may still be needed: for compliance, legal reference, or future review. Microsoft 365 Archive reduces storage cost and keeps the site intact for an admin to reactivate, although users cannot open it until then. Delete only when stakeholders have confirmed the site contains nothing required for compliance or future use.
How do you prevent SharePoint site sprawl?
Restrict self-service site creation through the SharePoint admin centre and require a named owner and a business purpose at creation time. Pair that with a quarterly review of dormant sites and, if your licences include SharePoint Advanced Management, an inactive site policy that emails owners and, after three unanswered notices, locks the site to read-only or archives it.
How long does content stay in a deleted SharePoint site before it is permanently removed?
When you delete a site through the admin centre, it moves to the SharePoint admin recycle bin and is retained for 93 days. A global or SharePoint administrator can restore it at any point during that window. After 93 days, the site and all its content are permanently deleted.