What are inactive and orphaned workspaces?
Also known as
Definition
Every Teams channel, SharePoint site, and Microsoft 365 Group was created for a reason. Over time, those reasons expire. Projects end. Teams reorganize. People leave. But the workspaces stay. Microsoft 365 doesn't clean them up automatically, and without a process to review them, they accumulate.
Inactive workspaces are the ones nobody is using anymore.
Orphaned workspaces are the ones nobody is responsible for.
These often overlap: a workspace that went quiet after its owner left has both problems at once. Together they make up a large share of what’s called Microsoft 365 sprawl: spaces, content, and accounts that consume storage and licenses the organization keeps paying for.
tip
When in doubt, archive rather than delete. Archiving makes a workspace read-only and removes it from active search without destroying anything. You can always delete later.
Why it matters
Inactive and orphaned workspaces create clutter and real costs: storage, licenses, governance gaps, and search noise that affects everyone working in the tenant.
- Migration: Migrating workspaces nobody uses carries old clutter into a new environment.
- Governance & security: Orphaned workspaces have no one accountable for the content or access inside them. Guests may still have access. Sensitive files may be sitting in a site nobody reviews.
- AI readiness: Copilot surfaces content based on what users can access. Inactive sites with stale or sensitive content become part of AI search results.
What we see out there
Paying for storage nobody uses.
Organizations regularly discover large numbers of inactive Teams and SharePoint libraries that have aged past 180 days. Storage they're paying for, content nobody is managing, and no automated way to do anything about it.
Migration surfaces workspaces teams aren't sure what to do with.
Often there's no shared agreement on what archive, keep, and delete actually mean for the organization, so every workspace becomes a judgment call that stalls the project.
Frequently asked questions
How long before a workspace is considered inactive?
There's no universal Microsoft standard. ShareGate identifies a workspace as inactive after 180 days with no user-generated activity across its associated workloads.
Who should decide what happens to an inactive workspace?
The owner. IT can flag a workspace as inactive and surface it for review, but the decision about whether to keep, archive, or delete it belongs to the person who knows what it was used for. If you can't get a response from an owner, IT makes the call. And if there's no owner at all, that's an orphaned workspace and needs to be handled separately.
Should we delete or archive inactive workspaces?
Archive first if you're unsure. Archiving makes the workspace read-only without destroying anything: content is preserved and it can be reactivated if needed. With Microsoft 365 Archive, archived sites also stop being used by Copilot.
What if the content needs to be retained?
Inactivity and retention requirements are separate decisions. A workspace can be inactive and still need to keep its content for regulatory, legal, or compliance reasons. Archiving is usually the right answer: the workspace goes read-only and content is preserved. If a retention label or legal hold has been applied, check with your compliance team before archiving or deleting anything.
