Every Microsoft 365 tenant I have audited has the same problem, sitting quietly in the Teams admin center: dozens of channels and workspaces that nobody uses, owned by people who have since moved on, backed by SharePoint sites that are still accumulating storage and still granting access to external guests the original team lead invited eighteen months ago. The Teams are not deleted. They are not archived. They are just there, unmanaged and forgotten.
This is not a user behavior problem. Users create Teams because Teams is easy to create and there is nothing stopping them. It becomes an IT problem the moment nobody sets up the guardrails that prevent the accumulation. The good news: this is a configuration problem, and configuration problems have solutions you set up once.
What Gets Created When Someone Clicks "Create Team"
Most people think of a Team as a chat workspace. What Microsoft actually provisions is four things simultaneously: an M365 Group (which owns the membership list and permissions), a SharePoint site (which stores every file uploaded to that Team's channels), a shared Exchange Online mailbox (rarely used directly but always there), and a Teams workspace layered on top of all of it.
When the project ends and the creator leaves the company, all four resources persist. The SharePoint site keeps accumulating storage. The M365 Group retains whatever external guest access was granted when the Team was live. If the original owner's account has been deprovisioned, the Team has zero owners: nobody receives renewal notices, nobody can archive or close it, and IT does not find out until something breaks.
The Audit: Finding What You Already Have
Start in the Teams admin center (admin.teams.microsoft.com). Go to Manage teams, sort by Last activity. Any Team with zero activity in the last 90 days belongs on a review list. That alone will surface more than you expect.
For a more precise picture, use PowerShell. This command returns every Team with fewer than two active owners:
Get-Team | ForEach-Object {
$owners = (Get-TeamMember -GroupId $_.GroupId -Role Owner).Count
if ($owners -lt 2) {
$_ | Select-Object DisplayName, GroupId,
@{Name="Owners"; Expression={$owners}}
}
}
Run that against your tenant and you will likely find a large number of single-owner Teams, and a smaller number with zero owners entirely. The zero-owner ones are your first priority: archive or assign an owner this week.
The Expiration Policy: The Setting Nobody Turns On
The most impactful governance control available is the M365 Group expiration policy, configured in the Entra admin center (entra.microsoft.com) under Groups, then Settings, then Expiration. Set a group lifetime (I use 365 days for most tenants, 180 days where data retention requirements are tighter). Once configured, every M365 Group and its associated Team gets a renewal deadline.
Owners receive automatic email reminders at 30, 15, and 1 day before expiration. Active teams get renewed with a single click. Teams whose owners ignore the reminders (or whose owners no longer exist) soft-delete after the deadline. The soft-deleted Group sits in a recoverable state for 30 days before permanent deletion, which gives you a safety net if something important was missed.
What this policy does over time: active teams self-renew silently. Dead teams expire and clean themselves up. You stop manually hunting orphaned content every quarter because the platform handles the lifecycle automatically. The setup takes about fifteen minutes.
Creation Controls and Naming Policy
By default, every Microsoft 365 user can create a new Team, which creates a new M365 Group, a new SharePoint site, and a new Exchange mailbox. For teams smaller than roughly 30 people, that is probably fine. For anything larger, unrestricted creation is how you end up with 400 Teams inside two years.
You can restrict Team creation to a specific security group using PowerShell to modify the EnableGroupCreation setting in Entra. Users outside that group who try to create a Team see a message directing them to submit a request through whatever process you define (usually a simple form or a helpdesk ticket). I have seen this single change reduce net-new Team creation by roughly half, simply because it adds a moment of intentionality to what had been a frictionless default.
Naming policy, in Entra under Groups and then Naming policy, lets you enforce prefixes on every new Team name. Standard patterns I use: PRJ- for project teams, DEPT- for department channels, TMP- for temporary working groups. This costs an Azure AD Premium P1 license per user, but it pays for itself quickly in reduced cleanup overhead.
The Two-Owner Rule
Single-owner Teams are the highest-risk configuration in most tenants. The moment that one person leaves, the Team becomes unmanaged. Nobody receives the expiration notices. Nobody can archive it through the Teams admin center (archiving requires owner access). IT does not find out until someone complains they cannot access a channel, often months later.
The fix is a monthly check with the PowerShell query above, followed by a simple remediation: add IT admin or a designated backup manager as a co-owner on any Team with fewer than two owners, then send the original owner an email asking them to designate a human backup. I run this as a Power Automate flow that queries the Teams Graph API, filters for single-owner groups, and sends a formatted email to IT once a week. The whole thing takes about an hour to build and runs unattended after that.
The rule itself does not need to be a mandate from management. Frame it as a service continuity measure: if something happens to the owner, someone else can still manage the workspace. Most people are fine with that framing.
Archive Before You Delete
When you identify a dead Team through the audit and the expiration policy has not yet fired, archive it rather than delete it. Archiving makes the Team read-only: the channels and content remain searchable and accessible to members, but nobody can post or upload. This matters because someone, somewhere, almost always needs to retrieve a file from an old project channel at the worst possible moment. Archiving buys you a clean 90-day window to confirm nothing important is being accessed before you move to deletion.
To archive in the admin center: Manage teams, three-dot menu next to the Team name, Archive. Via PowerShell: Set-TeamArchivedState -GroupId <id> -Archived $true. After 90 days with no access requests to the channel, delete the underlying M365 Group. The SharePoint site and Exchange mailbox go with it, and your tenant storage recovers the space.
The State of Your Tenant After You Do This
What changes once these policies are in place: new Teams get created with intention rather than impulse, carry meaningful names from the start, and expire automatically if nobody cares enough to renew them. Existing orphaned Teams surface through the audit and get archived or assigned a real owner. The monthly two-owner check catches anything that slips through. And the Teams admin center's activity view, which used to show 300 Teams of uncertain status, starts showing you the actual active workspaces your team uses.
The first time I ran a proper Teams audit at a client, we found more than 80 inactive Teams, eleven of them with active external guest accounts and no current owner. Getting to zero open guest access on dead channels took about two hours total. The governance setup that prevents the problem from recurring took another half hour.
None of this requires a third-party tool or a new license tier beyond what most M365 Business or Enterprise plans already include. It is a configuration problem. Configure the platform and let it do the work.
If you are doing this audit now and want a second set of eyes on what you find, drop me a note.
Comments