Supporting technical capability

Decide which Microsoft Teams to keep, merge or archive.

Review the agreed Teams, their usage and their owners. You receive keep, merge or archive recommendations, rules for new Teams and a quote for the cleanup.

Engagement context

Where this capability applies.

  • You have far more Teams than employees, with duplicates and abandoned projects.
  • Nobody knows where actual collaboration is supposed to happen.
  • New Teams get created with no rules, so the clutter keeps growing.

The agreed outputs

What the engagement provides.

Teams Governance & Clean-Up Ledger

Every Team scored by activity with a keep, merge, or archive decision.

Lifecycle and provisioning rules

How new Teams get created, named, and retired, so sprawl does not return.

A fixed clean-up quote

The scoped, fixed price to archive, merge, and apply the rules. The ledger is yours either way, so you can hand it to your own team or another vendor.

Worked example

Teams Governance & Clean-Up Ledger

An illustration of the record an engagement can produce. Names and figures are constructed for this example.

Illustrative content. The engagement record is developed from the client’s own environment and agreed scope.

Commercial & delivery basis

The scope and conditions of the work.

Delivery window

3-5 days

How engagements are scoped
Included scope
  • Teams inventory and activity scoring
  • Keep, merge, archive ledger
  • Rules for creating, naming, and retiring Teams
  • A fixed-fee clean-up quote
Scope assumptions
  • Usage and activity reporting available
Exclusions
  • Executing the clean-up and content migration (a separate fixed quote from this assessment)
  • Custom development to automate how new Teams get created
Required access
  • Read-only access to Teams and the SharePoint sites behind them
  • A 30-minute kickoff with a collaboration owner

Acceptance

The agreed completion standard.

The engagement is complete when the governance ledger, lifecycle rules, and the fixed clean-up quote are delivered and walked through.

Discuss the work

Tell us what you need to change.

Share the systems involved, why the change is needed and your deadline. We clarify the work, responsibilities and information needed for a proposal.

Request an Architecture Briefing