Microsoft Teams templates

A team template in Microsoft Teams is a pre-defined blueprint for creating new teams. It bundles a set of channels, pre-installed apps and tabs, and starter settings, so users don't start from a blank slate every time.

Templates enforce the structure decisions in Teams channels explained and Groups vs Teams vs SharePoint; combine them with naming and expiration policies and sensitivity labels for a governed creation process.

Why templates exist

Without templates, every team grows organically — different channel naming, different apps, different conventions — and quickly becomes hard to govern. A template makes the first version of a team consistent with how you want similar teams to look.

Templates are most valuable for repeatable patterns:

• Project teams with consistent kickoff, planning, retro channels.
• Incident response teams with predefined apps for paging, status, and post-mortems.
• Department teams (HR, Finance) with standard channels for typical workstreams.
• Crisis management with the right ServiceNow / PagerDuty / Approval apps already pinned.

Built-in templates

Microsoft ships a small set of built-in templates: Manage a Project, Manage an Event, Crisis Response, Patient Care, Bank Branch, Retail, and so on. They're a useful starting point even if you don't use them as-is.

Custom templates

In the Teams admin center under Teams → Team templates, you can:

• Create a template from scratch.
• Create one from an existing team (recommended — clone a known-good team).
• Create one from an existing template and customise.

A custom template defines: the team's default settings, the channel list (standard channels only — private and shared channels aren't in templates), and tabs/apps pinned to each channel. It doesn't include channel content, files, or membership.

Assignment

Admins decide which templates show up in the "Create a team" flow via Team templates policies. A policy can hide all built-in templates and surface only the templates your governance approves. Pair this with naming and expiration policies for Microsoft 365 Groups for full control over team sprawl.

Limits

Templates are creation-time blueprints; changing the template later does not update teams that already used it. If you add a new app to a template, only teams created from that point on get it. Treat templates as defaults, not living standards.

For organisations creating many teams a week, a few well-maintained custom templates pay back the setup time many times over.

Templates don't replace governance policy

A template standardises the starting shape of a team, but it doesn't enforce anything about the team's ongoing lifecycle — naming conventions, expiration, guest access rules, and sensitivity labelling are all governed separately, by Microsoft 365 Groups policies and Conditional Access, and apply regardless of which template (if any) a team was created from. A well-designed template combined with weak group governance still ends up with consistently-structured teams that nonetheless sprawl indefinitely with no owner ever reviewing whether they're still needed; the template solves the "what does day one look like" problem, not the "does this team still need to exist in year three" problem.

Frequently asked questions

Can a template pre-assign specific people as owners or members? No — templates define channels, apps, and settings, but membership is set at creation time by whoever creates the team; a template can't pre-populate a roster, since the whole point is that the same template is reused across many different teams with different people each time.

What happens to a team's template reference after creation? Nothing persists — once a team is created from a template, it becomes an entirely independent team with no ongoing link back to the template it was built from. Updating the template afterward has zero effect on teams already created from it, which is why templates should be thought of as one-time blueprints rather than a source of truth to keep teams in sync with.

Is it better to build a custom template from scratch or clone an existing team? Cloning a known-good, already-in-use team is usually the faster and more reliable path — it captures the actual apps, tabs, and channel structure that a real working team settled on, rather than an admin's best guess at what a good starting point looks like in the abstract, and it's easy to trim down afterward if the source team had anything too specific to itself.