In January, Teams was a program with a pilot board and a coexistence spreadsheet. In April 2020 it is the company hallway, conference room, and sometimes the phone system — adopted in days because the alternative was silence. This post is governance when adoption happens overnight: sprawl control, external access, meeting hygiene, and what we deliberately deferred so the firm could work.
What “wartime scale” looked like
- Meeting creation rates multiples of February baselines
- Guest access requests from every partner and school district at once
- Teams created per project, per panic, per “just us five”
- Recording defaults nobody set on purpose
- Helpdesk scripts rewritten daily
Skype for Business Online retirement in 2021 still matters. It is no longer the only clock — operational chaos is.
Minimum viable governance (ship this week)
We pushed a short control set before multi-month frameworks:
- Who can create teams — limit to a role or require naming prefix + expiry owner
- External access / guest defaults — decide allow/block domains; document exceptions
- Meeting lobby and presenter defaults — stop anonymous presenters by accident
- Recording and transcription policy — legal and HR aligned in one paragraph
- Channel naming and “private channel” guidance — light, not a novel
Perfect information architecture lost to “can we have a team by noon.”
What we deferred on purpose
- Full lifecycle automation and elaborate provisioning bots
- Perfect enterprise org-wide teams hierarchy
- Migrating every Skype habit before enabling meetings
- Custom compliance holds design beyond emergency legal needs
Write the deferrals down. Otherwise they become permanent amnesia.
Sprawl will happen — plan the cleanup
Expect thousands of abandoned teams by autumn if creation is wide open. Options:
- Expiration policies where licensed and understood
- Quarterly owner attestation for high-member teams
- Archive patterns for project teams after end dates
Do not shame users for sprawl you invited by enabling the world without an off-ramp.
Network and quality
Governance is useless if media is unusable. Split-tunnel / optimized Office 365 paths, DNS, and proxy bypass for Teams remain infrastructure work. Pair EUC governance with network changes; siloed ownership failed in March and fails still.
Security objections we answered
“Guests are dangerous” — yes; so is shadow Zoom on personal tenants. Prefer governed guest access in your tenant over unknown SaaS. Monitor, do not fantasize about zero collaboration.
“Record everything” — storage, privacy, and eDiscovery costs; default-on recording is a legal decision, not an IT preference.
Metrics for steering
- Teams created per week vs archived
- Guest users active
- Meeting join failures / quality tickets
- Percent of meetings with external participants
- Helpdesk volume by Teams category
Extended practice notes (2020)
The remaining gap between a short checklist and a usable field note is usually scenario detail. In practice, the same engagement type described above still requires explicit answers to: what is in scope this quarter, what is deferred with a date, who can halt a wave, and how success is measured in production — not in a lab.
We document those answers before the first production change. When stakeholders disagree, the disagreement is resolved in writing, not on the bridge at cutover. That habit is independent of whether the workload is mail, identity, virtualization, desktop delivery, or security hardening.
Repeatable detail also includes communication: who tells users what changes, when the freeze starts, where status is posted, and how exceptions are requested. Technical excellence without communication still produces an outage from the user's point of view.
If you're facing this
If Teams went company-wide without a governance one-pager, write the minimum viable controls this week and schedule cleanup. We help Office 365 tenants put guardrails on Teams without shutting down the business — bring your external collaboration requirements and legal constraints.