How should we govern Microsoft Teams creation, naming and expiration?

Key facts

• Every team is backed by a Microsoft 365 group, so most Teams governance is really group governance in Entra ID.
• Group naming policies, expiration policies and creation restrictions require Entra ID P1 licensing for the users they apply to.
• A group expiration policy asks owners to renew; active groups can renew automatically, and expired groups can be restored for a limited period.
• Sensitivity labels applied to teams can control privacy, guest access and external sharing for the connected SharePoint site.
• Two owners per team is the simplest rule that prevents most orphaned teams.

Start with why teams sprawl

By default any licensed user can create a team. That is good for adoption and bad for findability. After a year or two most tenants have duplicate teams, test teams, teams with one owner who has left, and teams with guests nobody remembers inviting. Each team also creates a SharePoint site, a group mailbox and a Planner location, so the sprawl spreads.

Governance is about keeping the benefits of self-service while making teams findable, owned and safe to share. The goal is a short set of rules people can follow without filing tickets for everything.

Decide who can create teams

There are three common models. Open creation lets anyone create a team, with naming and expiration policies cleaning up after the fact. Restricted creation limits group creation to members of a security group, set through the Entra ID group settings, so only trained staff or IT can create. Request-based creation routes requests through a form, often built with Microsoft Forms or Power Apps and Power Automate, which then creates the team from a template.

Small and mid-size organizations usually do best with restricted or request-based creation for teams that will hold sensitive data or external guests, and open creation is acceptable only when naming, labels and expiration are already in place. Whatever you choose, document it and tell people how to get a team.

Set a naming policy

A Microsoft 365 group naming policy adds a prefix or suffix to group and team names and can block words such as CEO, Payroll or Test. Prefixes can use fixed strings or user attributes like department or office. Keep it short: a type prefix such as PRJ, DEPT or EXT is usually more useful than a long attribute string that clutters the Teams client.

The naming policy applies when users create groups from Outlook, Teams and other workloads. Admins can bypass it, so build the same convention into any templates or creation flows IT uses.

• Prefix by purpose: department, project, external collaboration.
• Block words that imply authority or that commonly mean throwaway.
• Publish the convention in the intranet or a pinned Teams post.
• Rename the worst legacy teams during the rollout rather than all of them.

Use expiration and renewal

A group expiration policy sets a lifetime for Microsoft 365 groups. Before a group expires, owners get renewal notices by email and in Teams. Groups with recent activity can renew automatically, so active teams are not disrupted. If nobody renews, the group is soft-deleted and can be restored by an admin or owner within the restore window.

Pick a lifetime that matches how work runs, often one year for most teams. Apply it to all groups or a selected set, and make sure every group has an owner, because ownerless groups need a fallback contact for notices. Pair expiration with archiving: a finished project team can be archived to read-only in the Teams admin center so its content stays searchable.

Control privacy and guests with sensitivity labels

Sensitivity labels from Microsoft Purview can be applied to teams, groups and sites. A label can set the team to private, allow or block guest members, and set the external sharing level of the connected SharePoint site. That turns a privacy decision into a choice from a short list, such as Internal, Confidential and External Collaboration.

Combine labels with a retention policy for Teams messages and files, and with periodic guest reviews. Entra ID access reviews can ask owners to confirm guest membership, where your licensing includes them; otherwise a scripted report sent to owners each quarter does a similar job.

Keep ownership and reviews simple

Require at least two owners for every team. Use the Microsoft 365 ownerless group policy to ask active members to step up when an owner leaves, and add owner reassignment to the user offboarding checklist. Each quarter, review a short report of teams with no owner, one owner, guests, or no activity, and act on the top items.

Most governance fails because the rules were written once and never checked. A short recurring review keeps the policies honest and gives you data for the next change.

How Accred Consulting approaches it

Accred Consulting sets up Teams governance as part of a scoped SharePoint and Microsoft 365 engagement. Discovery reports on existing teams, owners, guests and activity, and the proposal sets scope, fixed price and timeline. The US-based specialists assigned to your engagement configure creation rules, naming and expiration policies, sensitivity labels for teams, and a request and template process where it fits. In one intranet engagement for about 240 users, about 1.8 TB was assessed and organized into 11 governed sites in 9 weeks. Handover includes documentation, owner guidance and knowledge transfer, with optional support retainers.

Track record: 475+ client projects, 2,000+ migration workstreams and 210,000+ users migrated by a US-based team. Company facts · Case studies

Related questions