Microsoft Copilot
What is an unmanaged Microsoft 365 workspace?
An unmanaged Microsoft 365 workspace is a team, site or group that nobody owns or uses. It keeps consuming storage and licences, and no one is accountable for removing it. You stop the cost with an inventory, an owner for each workspace and archiving what is no longer needed.
In short
- Workspaces are created easily and retired rarely, so the bill only grows.
- The cost sits in storage, in licences nobody uses and in the time spent finding out who owns what.
- Owners decide what to keep; IT sets the policy and measures the result.
- Archive on a cycle, and keep the record of what was removed and why.
Step by step
Five steps move you from a one-off cleanup to a routine that keeps the cost down.
-
Inventory every workspace
List all Teams, SharePoint sites and Microsoft 365 groups, with owner, last activity and the storage each one holds. You cannot cut what you cannot see, and the list is also your baseline for measuring savings.
-
Give every workspace an owner
Flag workspaces with no owner, only one owner or an owner whose account is disabled, and assign a new one. The owner is the person who answers for the cost of keeping the workspace.
Tip: Start with the workspaces that hold the most storage, since each decision there recovers the most.
-
Define what inactive means
Agree a rule per workspace type, for example no messages and no content changes for six months. A written rule turns an argument into a list.
-
Ask the owner, then archive
Send each flagged workspace to its owner to keep, archive or reassign. Archive what is not confirmed, and delete only after an approval where a person should sign off.
In Rencore: -
Report the saving
Track the storage and the number of workspaces retired each cycle, and share it with finance, so the effort is visible as a cost result and not only as housekeeping.
In Rencore:
Why unmanaged workspaces get expensive
Creating a team, a site or a group takes a minute. Retiring one takes a decision, and a decision needs an owner. When projects end and people move on, the workspace stays: its files, its version history, its recordings and its guests keep counting against your storage and your licences.
The cost is rarely one big item. It is the sum of many small workspaces that each look harmless, plus the hours IT spends working out who owns them. The fix is therefore less a cleanup project than an operating habit: know what exists, know who owns it, and review it on a schedule.
Connectors in this How-to
Each connector page in the Rencore docs lists the objects, policies, reports and actions behind these steps.
Last updated 11 November 2026
