Anonymized engagement summary: Microsoft Teams cleanup, creation policy and governance for an industrial manufacturer (2024)
Delivered — meeting record and work products on file (EPC-reported; documents private)First-pass editionAn industrial manufacturer (client not named) · 2024 · Project ID EPC-2024-ANON-MFG-TEAMSGOV
Last updated by Errin O'Connor, Founder & Chief AI Architect, EPC Group
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. Between October and November 2024 EPC Group and the client's IT lead 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.
Disclosure. This is an EPC-reported anonymized engagement summary. The client is not named. The supporting records — the countersigned statement of work, the dated project meeting record, the team inventory workbooks and the training deck — are retained privately and are not published in the Evidence Center, so this account is outside the Evidence Center's documented-engagement counts. Every engagement fact below is taken from those documents.
Verification class
Delivered — meeting record and work products on file (EPC-reported; documents private). The client's CIO countersigned the statement of work in September 2024. The meeting record is dated October to November 2024 and records each step below. No formal acceptance form or user-adoption measurement is claimed.
Buyer problem and scope
| Item | What the documents state |
|---|---|
| Buyer | An industrial manufacturer (client not named) |
| Situation | Teams 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 |
| Objective | Microsoft Teams as the organization-wide unified communication platform, with structure and policy to prevent future sprawl |
| Scope (statement of work) | Assessment 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 model | Short cycles that deliver working pieces ("quick wins"), with weekly status reporting; each deliverable reviewed and accepted, or rejected in writing within five business days |
Unknowns, not stated in the documents cited: 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. By November 20, 2024, 239 teams had been 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 (dated, held privately):
| Work product | Date |
|---|---|
| Countersigned statement of work | September 2024 |
| Project meeting record — cleanup, creation policy, archiving approach, security decisions | October–November 2024 |
| Team inventory reconciliation (owners, members and usage exports) | October 2024 |
| Phased cleanup and governance plan (cleanup and governance; standardization; security and compliance) | October 2024 |
| Teams best-practices training deck (11 slides) | Undated; on file by April 2025 |
| Team owners, members and status workbook; all-teams export | December 2024; May 2025 |
Results and limitations
| Claim | Basis | Status |
|---|---|---|
| Team creation restricted to a designated group, confirmed working | Meeting record, November 2024 | On file (EPC-reported) |
| 239 teams archived | Meeting record, November 20, 2024 | On file (EPC-reported) |
| Training on ownership, naming and channel use delivered | Training deck | On file (EPC-reported) |
| Adoption, sprawl or support volume measurably changed | No document cited | Not claimed |
Provenance
- Sources: the countersigned statement of work (September 2024), the project meeting record (October–November 2024), the team inventory workbooks and the training deck, held privately. Engagement ID: EPC-2024-ANON-MFG-TEAMSGOV, an alias unrelated to the client's name.
- Anonymization: industry only, under EPC Group's anonymized-case rule; team names, locations, staff names and commercial terms are not published.
- Not claimed: client endorsement, or any measured adoption or productivity result.
- Author: Errin O'Connor, Founder & Chief AI Architect, EPC Group, who signed the statement of work for EPC Group.
Revision history
- 2026-10-25: anonymized engagement summary published from the engagement's statement of work, meeting record and work products.
Related service
Microsoft Teams governance · Microsoft Teams consulting · Talk to a senior architect
Author: Errin O'Connor, Founder & Chief AI Architect, EPC Group · Published: 2026-10-25.