Skip to main content

Anonymized engagement summary: Microsoft Teams cleanup, creation policy and governance for an industrial manufacturer (2024)

Anonymized engagement summaryIndustrial manufacturer · 2024

Opening answer. In 2024 an industrial manufacturer engaged EPC Group to make Microsoft Teams its organization-wide communication platform and to bring a sprawling tenant under control. The assessment counted about 980 teams, most created per project. EPC Group and the client's IT lead then restricted who can create teams, agreed an archive-instead-of-delete approach, and archived 239 teams. EPC Group also delivered a Teams best-practices training session covering ownership, naming and when to create a channel instead of a team.

This is an anonymized engagement summary published under EPC Group's anonymized-engagement rule: the client is not named, no commercial terms are published, and every statement is EPC-reported. Named, documented engagements are in the Evidence Center.

Problem and scope

ItemScope
OrganizationAn industrial manufacturer
SituationTeams in use without governance: teams created per project, redundant and inactive teams, no limit on who could create a team, guest access on, no data loss prevention or retention policies
ObjectiveMicrosoft Teams as the organization-wide unified communication platform, with structure and policy to prevent future sprawl
ScopeAssessment and planning; Teams cleanup and restructuring (redundant teams and channels, alignment to the organization's structure, consistent naming); policy implementation (roles and permissions, assignment of users to teams by role, a limit on who can create teams, protocols for external sharing); a SharePoint Online permissions review; user training; a block of post-deployment support
Delivery modelShort cycles that deliver working pieces ("quick wins"), with weekly status reporting; each deliverable reviewed and accepted, or rejected in writing within five business days

Not reported: the number of users, the final team count after cleanup, and any change in adoption or support volume.

Approach and artifacts

Inventory first. The assessment listed about 980 teams. The working plan started with the 19 inactive teams, then moved on to duplicate and overlapping teams. Each team was reconciled against the owners-and-members export and the usage report, so teams missing from one list were found before anything was archived.

Stop the sprawl at the source. Team creation was limited to a designated group. A later meeting confirmed that only that group could create teams, and the redundant creation policies were deleted.

Archive, don't delete. Teams that might still hold useful files are archived: hidden from daily use, with their SharePoint sites set to read-only, so content stays available without being maintained. For teams being retired, the plan moves each team site one-to-one into a consolidated master site, with a select group of users holding access. During the engagement, 239 teams were archived.

Decisions recorded with the client. The meeting record shows each security recommendation and the client's decision on it. Guest access stayed on. The existing eleven conditional access policies were kept unchanged. A data loss prevention policy was offered and declined, and retention policies for the master sites went to the client for internal decision with options supplied.

Teach the owners. The training session set the rules the cleanup depends on:

  • only authorized roles create teams
  • every team has at least two owners, who review it quarterly
  • a channel, not a new team, when the topic and members already fit an existing team
  • names that start with region and function codes
  • team size guidelines, a standard channel structure and the platform's limits

Work products delivered (EPC-reported):

  • Project meeting record — cleanup, creation policy, archiving approach, security decisions
  • Team inventory reconciliation (owners, members and usage exports)
  • Phased cleanup and governance plan (cleanup and governance; standardization; security and compliance)
  • Teams best-practices training deck (11 slides)
  • Team owners, members and status workbook; all-teams export

What EPC Group delivered and what is not claimed

ClaimBasisStatus
Team creation restricted to a designated group, confirmed workingEPC delivery recordOn file (EPC-reported)
239 teams archivedEPC delivery recordOn file (EPC-reported)
Training on ownership, naming and channel use deliveredTraining deckOn file (EPC-reported)
Adoption, sprawl or support volume measurably changedNot reportedNot claimed

Related services

Microsoft Teams consulting · Data governance · All case studies · Talk to a senior architect

Last updated by Errin O'Connor, Founder & Chief AI Architect, EPC Group

Related service: Microsoft Teams Governance: Lifecycle and Retention

Author: Errin O'Connor, Founder & Chief AI Architect, EPC Group · Published October 25, 2026 · Project alias EPC-2024-ANON-MFG-TEAMSGOV · Published under the anonymized-engagement rule.

AI assistant — not a human