Microsoft 365 Group naming and expiration policies

Microsoft 365 Groups proliferate easily — every Team, every Outlook group, every Planner plan creates one — and without governance the directory fills with Team-3 (Copy) and ten-month-old project groups nobody owns. Naming policies and expiration policies are the two main mechanisms for keeping group sprawl manageable.

Naming policies

A group naming policy in Microsoft Entra ID applies to Microsoft 365 Groups (and the Teams, SharePoint sites, and Planner plans they back) at creation time. Two pieces:

• Prefix and suffix attributes — e.g., the group name gets the user's department appended, so Marketing becomes MKT-Marketing-Group. Drawn from Entra ID attributes (department, country, jobTitle) or static strings.
• Blocked words — names containing words on the blocked list are rejected. Used for inappropriate terms, internal-only keywords, or to prevent users from impersonating official groups.

The policy is enforced at every group-creation point — Outlook, Teams, SharePoint, Planner, the admin center, Graph API. Microsoft 365 admins (Global Administrator, User Administrator) can override the policy when creating groups via PowerShell.

Expiration policies

A group expiration policy sets a lifetime (180, 365, or custom days) on Microsoft 365 Groups. As a group nears expiration:

• The group owners receive renewal notifications via email and Teams.
• Owners can renew with a single click, extending the lifetime.
• If not renewed, the group is soft-deleted at expiration — recoverable for 30 days.
• After 30 days, hard delete — group and all backing content (SharePoint site, Planner plan, Teams team) are removed permanently.

Activity-driven renewal: if the group has been active (Teams chats, file edits, email) recently, the policy can auto-renew without owner action. This is the right default for most tenants — active groups stay alive automatically, inactive ones force a renewal decision.

Configuration

In the Entra admin center → Identity → Groups → All groups → Expiration:

• Set expiration duration.
• Enable for all Microsoft 365 Groups or a specific subset.
• Configure the owner notification email address for groups without owners.

Naming policies are configured in Groups → Naming policy.

What policies don't fix

• Old orphaned groups already in the directory — naming policies only apply at creation; existing groups need separate cleanup.
• Bad group taxonomies — policy enforces names, not whether the group should exist.
• External access creep — separate controls (sensitivity labels on groups, sharing policies) cover that.

For a tenant that's let groups sprawl, the initial cleanup is one-time work: identify orphaned and inactive groups via reports, validate with owners or escalate, and delete. After that, expiration policies keep things tidy automatically.

Operational considerations

• Make naming policies meaningful — [Department]-[GroupName] is useful; [OurCompany]-[GroupName] adds noise.
• Set the right expiration period — 180 days for fast-moving teams, 365 for slower-moving ones.
• Activity-driven renewal is almost always the right setting — let active groups live.
• Communicate the policy so owners aren't surprised by deletion notifications.
• Provide a self-service "extend" path alongside the renewal flow.

A tenant running naming and expiration policies feels measurably calmer than one without — fewer "what's this group?" questions, less directory noise, faster Teams creation.