Start free trial
Start free trial
How-to 5 steps 4 min read Updated 11 November 2026

How to make sure every Microsoft 365 workspace has an owner

Find the Teams, sites and groups with no owner, one owner or a leaver as owner, and keep every workspace accountable to a named person.

Torsten Mandelkow Works with
How-to

What is workspace ownership in Microsoft 365?

A Microsoft 365 workspace has an owner when at least one active, named person is accountable for its members, its content and its lifetime. To make sure every workspace has one, flag workspaces with no owner, one owner or a disabled owner, and assign a replacement.

In short

  • Ownerless workspaces are where access drifts, content ages and nobody answers for either.
  • Require at least two active owners per workspace.
  • Handle leavers before the account closes, with the manager as the fallback.
  • Confirm ownership on a cycle and keep the record.

Step by step

Five steps close the owner gap and stop it from reopening.

  1. Map who owns what

    List every Team, SharePoint site and Microsoft 365 group with its owners, and mark each as healthy, single-owner, ownerless or owned by a disabled account. That map is your starting point and your measure of progress.

    In Rencore:

  2. Set the ownership rule

    Decide the standard: at least two active owners for every workspace, both employees, with guests never serving as sole owner. A simple written rule is enough to check against.

  3. Assign owners where they are missing

    Ask the last known owner or their manager to nominate an owner, and record the answer. Prioritise workspaces with external guests or sensitive content.

    Tip: Use the manager of the last known owner as the default when nobody answers, so no workspace stays ownerless by default.

    In Rencore:

  4. Build ownership into joiner, mover and leaver steps

    When someone leaves or changes role, check which workspaces they own and reassign them before the account is closed. This stops new orphans at the source.

  5. Confirm ownership on a cycle

    Have owners confirm quarterly that they still own the workspace and that its members are right. Escalate unanswered requests and keep the confirmations as evidence.

    In Rencore:

Why workspaces lose their owner

Owners are set once, when a workspace is created, and then left alone. People change roles, leave, or never really took on the job. The workspace carries on, but the person who would have said who still needs access, or whether the project is finished, is gone.

This is the root of several governance risks at once: stale access, oversharing, unmanaged storage and an audit trail with no accountable name. Central governance does not mean IT owning everything. It means every workspace has a named owner and IT can see where that is not true.

Connectors in this How-to

Each connector page in the Rencore docs lists the objects, policies, reports and actions behind these steps.

Common questions about workspace ownership

What risks come from workspaces without an owner?
Without an owner nobody confirms who still needs access, nobody answers for the content and nobody decides when the workspace should be archived. Access drifts, guests stay, files get overshared and storage keeps growing. In an audit you cannot show who was accountable, and Copilot can still surface anything the stale access permits.
How many owners should a Team or site have?
At least two. One owner is a single point of failure: when that person leaves or changes role, the workspace is orphaned overnight. Two named owners give you cover for holidays and departures, and a policy that flags workspaces with fewer than two owners lets you fix the gap before it becomes an ownerless workspace.
What should happen when an owner leaves the company?
The workspace needs a new owner before the account is deleted, not after. Flag workspaces whose owners are disabled or gone, route them to the leaver's manager as a fallback, and let the manager reassign or confirm them. Put the check into your offboarding steps so it is routine and not a clean-up exercise months later.
Do the Microsoft 365 admin center and Entra not cover ownership?
They let you view and change owners one workspace at a time, and Entra can expire groups that owners do not renew. They do not give you a cross-service list of Teams, sites and groups without a working owner, an owner confirmation workflow, or a record of who confirmed what. For that you need a layer that reads ownership across services.
How does Rencore help with workspace ownership?
Rencore Governance has policies that flag Teams without owners, with fewer than two owners, or whose owners have been disabled. Scheduled reviews then ask each owner in Microsoft Teams to confirm, remove or reassign, and every decision is logged with a reason, so you keep a record rather than only a completion percentage.

Last updated 11 November 2026

About the author

Torsten Mandelkow

Torsten is co-founder and CAA at Rencore. During his time as a SharePoint consultant, he always tried to improve and automate the SharePoint development process, first by creating the SharePoint Software Factory (SPSF), and later by creating the SharePoint code analysis tools, today known as SPCAF. After an intermezzo for 3 years at Microsoft, he is now part of the RENCORE team and is responsible for the further technical development of all our tools.

Related

See ownership gaps across your tenant

We will show how workspaces without a working owner are found and how owners confirm in Microsoft Teams, in a short demo.

Request a demoGet started free
Rencore newsletter

Subscribe to our newsletter

Get the latest insights on governing Microsoft 365, Copilot and AI agents, delivered to your inbox.

Loading form