HomeCase StudiesTeams sprawl governance
Professional services firm · 300 people

From 280 orphaned teams to a tenant that cleans itself.

Three years of unrestricted creation left this 300-person professional services firm with 280+ teams — duplicates, teams with no owners, guests with standing access and five naming conventions. Nobody could tell which team was the real one for a client, and nobody was accountable for cleaning any of it up.

280→96active teams
100%teams with owners
0unmanaged guests
The problem

Anyone could create a team. Everyone did.

When the firm rolled out Microsoft Teams, creation was left wide open — any employee could spin up a new team, and for three years they did. Every client kickoff, internal initiative and side conversation produced another one. By the time leadership looked, the tenant held 280+ teams, and no one could explain what most of them were for.

The sprawl had a daily cost. With five naming conventions in circulation, searching for a client surfaced several plausible candidates, so people posted updates in one team while colleagues worked from another — and files for the same engagement drifted apart across duplicates. Teams with no owner had no one who could approve a membership change, tidy the channels or make the call to archive.

The quieter risk was access. Guests invited during long-finished engagements still had standing access to whatever their teams contained, and with no owners there was no one to review them. When leadership asked the simple question — who can see what? — the honest answer was that nobody knew.

What we did

Audit, archive, standardize — then make it self-maintaining.

A full sprawl audit, archiving of the dead weight, client and project templates with naming standards, owners on every team, and expiration policies so inactive teams archive themselves. Here's how that unfolded.

1
Full sprawl audit

We inventoried every team in the tenant — activity, membership, owners, guest access and which client or project it actually belonged to — so every later decision was made from evidence, not memory.

2
Archived the dead weight

Duplicates and inactive teams were archived, not deleted: conversations and files stay searchable and recoverable, but the clutter disappeared from everyone's Teams list.

3
Client & project templates

New teams now start from a standard template with the right channel structure and settings baked in, so the correct home for an engagement is obvious from day one.

4
One naming standard

Five competing conventions became one. A team's name now tells you the client, the engagement and its status — and search finally returns the one right answer.

5
Owners on every team

Every surviving team got an accountable owner responsible for membership, guest access and the archive decision. Guests without a current reason to be there lost their standing access.

6
Expiration policies

Inactive teams now prompt their owner to renew — and archive themselves if nobody objects. Governance keeps running without a person having to drive it.

Results

A tenant the firm can trust again.

Every remaining team is real, named consistently, owned by someone accountable — and the tenant now keeps itself that way.

280→96

active teams

100%

teams with owners

0

unmanaged guests

Microsoft Teams Microsoft 365 Groups Microsoft Entra ID Teams Admin Center Microsoft Graph PowerShell SharePoint Online

Your Microsoft 365 is already paid for. Start using it.

Book a free 30-minute audit — we'll look at how your Teams tenant is really being used and show you exactly where your team is losing time.