What is site lifecycle management?
Also known as
Definition
Every SharePoint site, Teams workspace, and Microsoft 365 group starts with a purpose. Over time, that purpose ends. Projects finish, Teams reorganize, and people leave. But the workspaces stay, because Microsoft 365 doesn't clean them up automatically.
Site lifecycle management is what keeps that from becoming a problem. It's a defined process for what happens to a workspace at every stage: who owns it when it's created, how it gets reviewed when it goes quiet, what happens when the owner leaves, and when it should be archived or deleted.
It's not only about deletion. A workspace might move from active to read-only when a project ends, stay archived for compliance reasons, or get reviewed and renewed when a team confirms it's still needed. Lifecycle management covers all of those decisions, not just the final one.
tip
Define your lifecycle states before running a cleanup. Active, inactive, archived, and deleted mean different things in different organizations. Agreeing on what each state means and who decides makes the process repeatable.
Why it matters
Without a lifecycle process, workspaces accumulate. The cost is storage, licenses, governance gaps, and search noise that affects everyone in the tenant.
- Migration: Sites with no clear owner, no active users, and no defined purpose are the hardest migration decisions. Lifecycle management before a migration turns those judgment calls into a defined process: move it, archive it, or leave it behind.
- Governance & security: An ownerless workspace has no one accountable for its content or access. Guests may still have access. Sensitive files may be sitting in a site nobody reviews. Lifecycle management puts accountability behind every workspace.
- AI readiness: Inactive sites with stale or sensitive content become part of AI search results.
Commonly confused with: Deletion
Site lifecycle management is often treated as a cleanup project: finding inactive sites and deleting them. But deletion is just one possible outcome. A workspace might be archived when a project ends, renewed when an owner confirms it's still needed, or restructured when a team changes. Lifecycle management covers the full range of those decisions.
What we see out there
No process for what happens next.
Most organizations can identify inactive workspaces. What's harder is having a defensible process for what happens next. Archive it? Delete it? Ask the owner? Without defined lifecycle states and clear owner actions, every workspace becomes a one-off judgment call.
Ownership gaps are the most common blocker.
When the person who created a workspace leaves, nobody takes over. The site stays active, access doesn't get reviewed, and IT inherits the accountability. Assigning a second owner at creation is one of the simplest lifecycle controls that gets skipped most often.
Frequently asked questions
Who owns site lifecycle?
IT sets the policies and the tooling. But the decision about whether a workspace is still needed belongs to its owner: the person who knows what the content is for. If a workspace has no owner, IT has to make the call. That's why ownership assignment at creation matters: it determines who's accountable for every lifecycle decision that follows.
When should a site be archived?
When it's no longer actively used but still has business or compliance value. A completed project site, an inactive team, a workspace whose owner has left—these are reasons for archiving rather than deletion. Archiving makes a workspace read-only and removes it from active search without destroying anything. With Microsoft 365 Archive, archived sites are also excluded from Copilot.
What happens to group-connected sites?
Every group-connected SharePoint site has a Microsoft 365 group behind it. Archiving or deleting the site affects the group and every connected resource: the shared mailbox, Planner boards, and any Teams workspace connected to it. Lifecycle decisions on group-connected sites need to account for all those dependencies, not just the SharePoint site itself.
How often should sites be reviewed?
It depends on risk and activity. High-traffic sites with external guests or sensitive content need more frequent reviews. Inactive internal sites can go longer. The goal isn't one review schedule for everything, it's matching the cadence to the risk of what's inside the workspace.
