Skip to main content
Sprawlsight
Sign inFree self-assessment
Menu

Find ownerless and inactive Teams and SharePoint sites

By The Sprawlsight team · · 8 min read

teamssharepointlifecycle

In short

To find ownerless teams and groups, filter Active teams & groups by Ownerless groups in the Microsoft 365 admin center. For sites, use a site ownership policy. Find idle workspaces with inactive site policies and the Team usage report. Restore owners first, archive idle workspaces, and delete only after a Microsoft Purview retention policy covers them.

Self-service creation of teams, groups and sites is Microsoft's default, and it works. After a few years, though, it leaves a long tail of workspaces that nobody owns or uses. They keep old content and old access alive, and that matters once Microsoft 365 Copilot and agents start working across the tenant.

This guide works in lifecycle order with Microsoft's own tools: restore ownership, measure inactivity, then archive or delete with retention in place.

What is workspace sprawl?

Workspace sprawl is the buildup of teams, Microsoft 365 groups and SharePoint sites that have no owner, no recent activity or no retention coverage. A project ends and the team stays. An owner leaves, their account is deleted, and the group becomes ownerless. A site built for a one-off event keeps its members and sharing links for years.

It is one of six kinds of sprawl covered in our guide to Microsoft 365 sprawl, and a forgotten site often holds overshared files and inactive guests too.

Why do forgotten teams and sites matter for Copilot?

Copilot works within the permissions people already have, so any forgotten workspace a user can still open is content Copilot can draw on. Three problems follow.

  • Stale content grounds answers. An old price list or a replaced policy in an abandoned site can show up in a Copilot answer next to current material.
  • Old permissions persist. Members, guests and sharing links outlive the project. Our posts on SharePoint oversharing and inactive guests and accounts cover those layers.
  • Nobody reviews access. Groups and teams need an owner to manage members and settings. With no owner, those changes fall to admins, and nobody close to the work notices the wrong people are inside.

How do you find teams, groups and sites with no owner?

Use the Ownerless groups filter in the Microsoft 365 admin center for groups and teams, and a site ownership policy or the Active sites page for SharePoint sites. Start with Microsoft 365 groups, because every team and group-connected site takes its owners from its group.

Microsoft 365 groups and teams

In the Microsoft 365 admin center, go to Teams & groups > Active teams & groups, select Filter, and choose Ownerless groups.

To have members fix it for you, turn on the ownerless group policy. Go to Settings > Org settings > Services > Microsoft 365 Groups and select When there's no owner, email and ask active group members to become an owner. The policy emails the most active members each week, and up to two members per group can accept. Know its limits:

  • It covers Microsoft 365 groups only.
  • If nobody accepts, the policy stops and you assign owners yourself.
  • It needs an eligible plan, such as Microsoft 365 Business Premium or Microsoft 365 E3 or E5, or Microsoft Entra ID P1 or P2.

The filter lists only groups with zero owners. Deleting the last owner's account makes a group ownerless, but disabling it doesn't, so a departed owner whose account is only disabled still counts as an owner.

PowerShell: groups with fewer than two owners

Microsoft recommends at least two owners per group. This read-only Microsoft Graph PowerShell sketch lists Microsoft 365 groups below that bar.

Connect-MgGraph -Scopes "GroupMember.Read.All"
$groups = Get-MgGroup -Filter "groupTypes/any(c:c eq 'Unified')" -All
foreach ($g in $groups) {
  $owners = @(Get-MgGroupOwner -GroupId $g.Id -All)
  if ($owners.Count -lt 2) {
    [pscustomobject]@{ Group = $g.DisplayName; Owners = $owners.Count }
  }
}

Check the owners it does find against sign-in activity, so a departed owner doesn't count as cover.

SharePoint sites

Communication sites and classic sites have their own site owners and admins, so group checks miss them. With SharePoint Advanced Management, create a site ownership policy under Policies > Site lifecycle management in the SharePoint admin center. SharePoint Advanced Management needs a qualifying plan, such as Office 365 or Microsoft 365 E3 or E5, plus at least one Microsoft 365 Copilot license in the tenant or the Plan 1 add-on. Check the prerequisites for your plan.

Set a minimum of two owners or admins. The policy can notify current owners, site admins, managers of previous owners and recently active members. Run it in simulation mode first for a one-time report, then switch to active mode, which runs monthly and sends notifications. Read-only and archive enforcement apply only to sites with no owner at all.

Without SharePoint Advanced Management, use the Active sites page. The Primary admin column and each site's Membership tab show who is accountable.

How do you find inactive sites and teams?

Use an inactive site policy in SharePoint Advanced Management, or the Team usage report, Groups activity report and Active sites page that come with Microsoft 365. Each shows a workspace's last activity date. Fix ownership first: an owner can confirm or close an idle site, while an ownerless one just collects notices.

Inactive site policies

Inactive site policies in SharePoint Advanced Management track activity across SharePoint and connected workloads. That includes Teams channel messages and meetings, email to the group mailbox, and Viva Engage. Activity from apps that sign in as themselves, with an app-only token rather than on behalf of a user, doesn't count. A backup or governance tool that reads a site this way won't keep it active.

  1. In the SharePoint admin center, go to Policies > Site lifecycle management and open Inactive site policies.
  2. Set the scope, the inactivity period and who to notify: site owners, site admins or both.
  3. Choose what happens after three monthly notifications with no response: do nothing, make the site read-only, or archive it. Archiving follows a read-only period of 3, 6, 9 or 12 months and uses Microsoft 365 Archive, which must be turned on first.
  4. Save the policy in simulation mode and review the report.
  5. Switch to active mode once owners know what is coming.

Owners keep a site by selecting Certify site in the email, and the policy then skips that site for a year. Microsoft's site lifecycle management overview shows how ownership, inactivity and site attestation policies (which ask owners on a schedule to confirm a site is still needed) work together.

Teams and group activity reports

  • Team usage: in the Microsoft 365 admin center, go to Reports > Usage > Microsoft Teams > Team usage. The table lists each team's last activity date and exports to CSV.
  • Groups activity: under Reports > Usage > Microsoft 365 apps, the Groups activity tab shows each group's last activity across email, Viva Engage and the site.
  • Active sites: the SharePoint admin center has a built-in Least active sites view and a Last activity column.

Usage reports hide group and site names by default. A Global Administrator can show them under Settings > Org settings > Services > Reports.

Should you archive or delete an inactive team?

Archive first when anyone might need the content again, and delete only after retention protects what you must keep.

  • Archive the team. All activity in the team stops, but members can still view channels, files and chats. A team owner or admin can also make the team's SharePoint site read-only for members, and can restore the team later. See Archive or delete a team.
  • Archive the site. Microsoft 365 Archive moves a site to a colder storage tier. Content in the archive tier is no longer directly accessible to anyone until an admin reactivates it, and permissions and metadata are kept. It uses pay-as-you-go billing, and sites for teams with private or shared channels are only partly supported.
  • Delete. Deleting a team removes its channels, files and chats. The underlying Microsoft 365 group can be restored for 30 days, then it is gone unless retention holds the content.

Before you delete anything, put retention in place. A Microsoft Purview retention policy that uses the Microsoft 365 Group mailboxes & sites location covers a group's mailbox, site and files. Teams channel messages need their own policy with the Teams channel messages location. Communication sites, classic sites and the sites for private and shared channels aren't connected to a group, so cover them with the SharePoint classic and communication sites location. A deleted team's site under retention isn't deleted until the retention period ends.

A simple order for each idle workspace:

  1. Confirm it has an owner, or assign one from IT for now.
  2. Ask the owner to confirm it is needed or agree to close it.
  3. Check that a retention policy covers it.
  4. Archive it and set a review date.
  5. Delete it at the review date if nobody asked for it back.

What keeps new workspaces from becoming orphans?

Two owners per workspace, a group expiration policy, limits on who creates groups, and scheduled ownership checks keep new workspaces from becoming orphans.

  • At least two owners. Make it a creation rule, and back it with a site ownership policy in active mode.
  • Group expiration policy. In the Microsoft Entra admin center, open Groups > All groups > Expiration and set a group lifetime. Groups with user activity renew automatically. Owners of idle groups get notices before expiry, and you name an email address for groups with no owner. A group that nobody renews is deleted one day after it expires and can be restored for 30 days. Put a retention policy in place first, and start with a longer lifetime, such as 180 or 365 days. See Set expiration for Microsoft 365 groups. It requires Microsoft Entra ID P1 or P2 for members of the groups in scope.
  • Creation and naming controls. You can limit Microsoft 365 group creation to members of one group, which also limits who creates teams and group-connected sites. That needs Microsoft Entra ID P1 or P2 for the admin who sets it up and for the people allowed to create groups. A naming policy adds prefixes or suffixes and blocks chosen words, and needs P1 for every member of a Microsoft 365 group.
  • Ownership notifications. Keep the ownerless group policy on, and run site ownership and site attestation policies on a schedule.

Native tools at a glance

Problem Native tool Licensing note Sprawlsight snapshot test
Group or team with no owner Ownerless groups filter and ownerless group policy Policy needs an eligible plan (such as Business Premium or Microsoft 365 E3 or E5) or Entra ID P1 or P2 SPR-005
Site with no owner, or too few owners Site ownership policy SharePoint Advanced Management SPR-009 (sites with no owner)
Inactive SharePoint site Inactive site policy; Active sites page Policy needs SharePoint Advanced Management; Active sites is included SPR-006
Inactive team Team usage report; archive in the Teams admin center Included with Microsoft 365 SPR-007
Idle groups that never expire Microsoft 365 group expiration policy Entra ID P1 or P2 for members of groups in scope Not in the snapshot
Content lost when a workspace is deleted Microsoft Purview retention policy Depends on your plan Not in the snapshot

Which Sprawlsight checks cover this?

The free snapshot checks SPR-005 through SPR-009: group, team and site owners, inactive sites and teams, and nested groups. The Workspace Sprawl field guide has the full cleanup playbook and a checklist.

Frequently asked questions

What is an ownerless Microsoft 365 group?

It is a Microsoft 365 group or team with no owner, usually because the only owner's account was deleted. Without an owner, only admins can add or remove members or change the group's settings, so day-to-day access decisions stop. In the Microsoft 365 admin center, filter Active teams & groups by Ownerless groups to see them.

Does archiving a team make it read-only?

Yes. Archiving stops all activity in the team, while members can still view its channels, files and chats. A team owner or admin can also make the team's SharePoint site read-only for members, and can restore the team later.

Will a group expiration policy delete teams that people still use?

No. Groups with user activity, such as a Teams channel visit or a file edit, renew automatically. Owners of idle groups get notices 30, 15 and 1 day before expiry. A group that nobody renews is deleted, and it can be restored within 30 days.

Do I need SharePoint Advanced Management to find inactive sites?

You need it for site ownership and inactive site policies. On a qualifying plan, such as Office 365 or Microsoft 365 E3 or E5, it is included when at least one user has a Microsoft 365 Copilot license, and it is also sold as the SharePoint Advanced Management Plan 1 add-on. Without it, you can still use the Active sites page, the usage reports, the ownerless group policy and PowerShell.

Should I archive or delete an inactive SharePoint site?

Archive first when anyone might need the content again. Delete only after a retention policy covers what you must keep, and after the owner, or a temporary owner from IT, has agreed.

Related reading

· 8 min read

Fix SharePoint oversharing before Microsoft 365 Copilot

Find and fix SharePoint and OneDrive oversharing before Microsoft 365 Copilot surfaces it: sharing defaults, Anyone links, org-wide access and site reviews.

sharepointonedriveoversharingcopilot

· 9 min read

Clean up inactive guests and accounts in Entra ID

A safe, repeatable way to clean up inactive guest accounts, stale users, idle admins and unused app registrations in Microsoft Entra ID: disable before delete.

identityentraguests