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 | Report Master site inventory / M365 usage reports | 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: inactive site policies, the SharePoint admin centre, and Microsoft 365 Archive. 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 disable self-service creation for standard users. 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 inventory with Report Master
Report Master exports a full site inventory to Excel in a single operation, covering last activity date, storage used, primary admin, and file count for every site collection in the tenant. The resulting workbook is pivot-ready: 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 to surface orphans in seconds.
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.
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 at full price.
When you archive a site:
- The site becomes read-only. Users cannot add, edit, or delete content.
- The site's storage consumption shifts to the archive storage tier, which is typically billed at a lower rate than active storage.
- Content remains searchable and is accessible to users with existing permissions.
- The site can be reactivated to full read/write mode if needed.
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 label or hold is applied. In the Microsoft Purview compliance portal, verify that no retention label is active on the site's content. Attempting to delete a site under a hold will fail or leave content in an inconsistent state.
- 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 feature handles the operation in a single pass rather than processing sites one at a time through the admin centre UI.
- 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 while keeping content searchable and restorable. 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. Combine that with a quarterly inactive site review and an automated inactive site policy, which can notify owners and optionally archive sites after a configurable inactivity period.
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.