Ownerless Microsoft 365 Groups: Why owners stay missing

Microsoft's ownerless group policy emails a team's most active members every week, asking one of them to become the owner. If nobody says yes before the notification period ends, the policy stops and the team stays ownerless: members keep chatting and sharing files, but nobody on the team can remove a member, add or remove a guest, or decide whether it should be archived.

Ownerless Microsoft 365 groups and Teams pile up for four reasons:

1. The only owner's account is deleted, and there was never a second owner.
2. Microsoft's controls ask for an owner but don't assign one.
3. With expiration on, active groups renew automatically, so expiration never flags them.
4. Owners who've left but whose accounts are only disabled still count as owners.

Microsoft's three controls, the ownerless group policy, group expiration and the SharePoint site ownership policy, each cover part of this. Each one asks someone to take ownership, and none of them assigns an owner when nobody answers, so the reassignment comes back to IT. 

How Microsoft 365 groups and Teams become ownerless

A team in Microsoft Teams is a Microsoft 365 group underneath. When you create a team, a Microsoft 365 group is created to manage its membership, so the team’s owners are the group’s owners. Microsoft says a group or team can become ownerless if you delete an owner’s account. In practice, that happens when the only owner leaves the organization and their account is removed. 

Microsoft's definition also has a blind spot. A group counts as ownerless when it has no owner assigned, so an owner who has left the business but whose account is only disabled still appears as an owner.  Those teams don’t appear in the ownerless filters in the Microsoft 365 or Exchange admin centers, even though nobody is managing them. 

The cost is the same either way. Only owners remove members, manage guests, change team settings, and renew, archive or delete the team. Without one, every request becomes an admin ticket, and guests stay until someone notices.

Orchestry All Workspaces report with Ownerless and Inactive Guests insight flags on each workspace  

Orchestry flags ownerless workspaces as an insight in its workspace reports, so the backlog shows up next to each workspace's risk rating and activity.

The Microsoft 365 ownerless group policy: what it asks and when it stops

The ownerless group policy is Microsoft's most direct answer. An Exchange or Groups administrator turns it on in the Microsoft 365 admin center, and it emails the most active members of each ownerless group every week, asking whether they'll accept ownership. If the group has no activity, it asks random members instead, and up to two members can accept.

 Ownerless Microsoft 365 groups and Teams and the native controls that ask members to take ownership

It's a useful nudge, and its limits are documented:

• It stops when nobody says yes. After the notification period ends, Microsoft says the policy stops there, and tenant admins need to find and assign an owner for each group.
• It’s manual unless you script it. In the admin center you add specific groups one at a time, up to 50. Microsoft Graph now exposes the policy, so the list can be set by script, but either way the policy only asks; it never assigns an owner.
• It can be throttled. Notifications come from one mailbox, and Exchange Online limits a mailbox to 10,000 sent emails a day.
• It only covers Microsoft 365 groups. SharePoint sites without a group are never checked. Guests are never invited to become owners, and limiting who can be asked with a security group needs Entra ID P1 or P2.

The policy picks members by activity. The most active person in a project channel may be a contractor who joined last month and knows little about why the team exists. 

Why group expiration renewal doesn't fix an ownerless team

Many admins expect Entra group expiration to catch ownerless teams. With an expiration policy set, groups with user activity renew automatically, owners of inactive groups get renewal notices, and groups that aren't renewed are deleted, with 30 days to restore them. It keeps a group alive or deletes it, and it never assigns an owner. 

For a group with no owner, renewal notices go to an alternate email address you specify. Someone in IT renews or ignores the group, and either way it still has no owner. 

 Activity-based renewal adds a quieter problem. An ownerless team that people still use renews itself without sending any notice, so the busiest ownerless teams, the ones with the most content and guests, never surface through expiration at all. 

What the SharePoint site ownership policy adds and where it stops

The third control sits in SharePoint Advanced Management, which Microsoft includes for tenants with a Copilot license. The site ownership policy runs monthly against a minimum owner count you set, and it can notify current owners, the managers of previous owners, and the site's most active members from the last 180 days. Guests aren't asked. 

It goes further than the group policy because it can act. For a site with zero owners, it can set the site to read-only after three monthly notices and, if Microsoft 365 Archive is turned on for your tenant, archive it after a read-only period you choose. 

The gaps are in who it can reach:

• Managers hear about it only briefly. User details are deleted 30 days after someone leaves, so a policy that runs after that point can't find their manager.
• Teams SharePoint sites often miss the manager step. For a Teams site, the manager notice only works when the departed owner was added directly as a SharePoint site owner. Teams owners normally get site ownership through the Microsoft 365 group, and those owners don’t trigger it.
• Its fix is a lock. Read-only and archive stop the risk on a site nobody claims, and they also stop a team people may still need. For workspaces that really are finished, here's how to archive inactive Teams and SharePoint sites with Orchestry with an owner decision first. 

How to assign owners to ownerless Microsoft 365 groups at scale

All three native controls ask. What's missing is a process that keeps asking the right people until the workspace has an owner, and that starts before the owner leaves. Four steps close the gap:

1. Require two owners at creation. A second owner is the cheapest fix there is. If one leaves, the team never becomes ownerless.
2. Detect ownerless workspaces continuously. Check every workspace on a schedule, including the ones you haven't added to a policy.
3. Route the decision to people who know the workspace. Active members are a good start, but you also need named fallback owners, such as a department lead or a service account, for teams where nobody steps up.
4. Make ownership part of a recurring review. A check that repeats with every membership, sharing and lifecycle review catches teams that lose an owner later.

Orchestry workspace review policy that reassigns reviews for ownerless workspaces to active members or named users.

Orchestry builds each step into the workspace itself. Workspace templates can set the minimum number of owners and members needed to request a workspace, so teams requested through Orchestry start with two owners. The Ownerless Workspaces report keeps the list of workspaces with no assigned  current  owner. . Owners with disabled accounts still count there too, so add an ownership check to your offboarding process. 

For workspaces that have already lost their owner, Orchestry's workspace reviews handle reassignment. The policy sends the review to the workspace's most active members, or to specific users or service accounts you name, and the recipient accepts the owner role before completing the review. Guests aren't counted as active members. 

Because ownership sits inside the same recurring review as membership, sharing and archival, the next review catches a team that loses its owner later.  Orchestry customers clean up 75% of their unused Teams within their first 14 days, once archival and workspace review policies are turned on. 

If you're starting from a backlog and want the native click-paths for finding and fixing orphaned teams one at a time, see our guide on how to deal with orphaned Microsoft Teams and groups. 

Ownerless Microsoft 365 groups: frequently asked questions

What happens to a team without an owner?

Members can keep chatting and sharing files, and in a public team they can still add members. But nobody can remove members, add or remove guests, change team settings, or renew, archive or delete the team. Those requests go to tenant admins until someone is made an owner.

How do I find ownerless groups in Microsoft 365?

In the Microsoft 365 admin center, go to Teams & groups, select Active teams & groups, and filter on Ownerless groups. The Exchange admin center has the same filter under Groups. Both show groups with no owner assigned, not groups whose owner has left but is still listed.

Does the ownerless group policy assign an owner automatically?

No. It emails active members each week and asks them to accept ownership. If nobody accepts within the notification period, the policy stops and an admin has to assign an owner.

Does group expiration delete ownerless groups?

It can. Renewal notices for a group with no owner go to an alternate email address, and if nobody renews the group it's deleted, with 30 days to restore it. Groups with recent activity renew automatically, so active ownerless groups aren't deleted.

How many owners should a team have?

At least two. A second owner means the team keeps an owner when one person leaves, and it's the simplest way to prevent ownerless Microsoft 365 groups in the first place. 

If ownerless teams keep landing on your desk, see how Orchestry routes ownership to the people who know each workspace. Book a 30-minute walkthrough in your own tenant.