Creating a team in Microsoft Teams takes about a minute. Creating one that doesn’t turn into a mess six months later takes a little planning first. The button is easy to find; the decisions behind it — who owns it, how it’s structured, which channels are open and which are locked down — are what separate a team people actually use from another abandoned workspace nobody opens.
This guide covers the three ways to create a team, the difference between a team and a channel and a chat (people mix these up constantly), and how owners, members, and the three channel types fit together. By the end you’ll know not just how to click Create, but how to set the thing up so it still makes sense later.
Team vs channel vs chat — get this right first
These three things look similar in the app but serve different purposes, and choosing the wrong one is the most common Teams mistake.
A team is the top-level container. It has members, a set of channels, a SharePoint document library for files, and a Microsoft 365 group underneath it. Think of it as the workspace for an ongoing group — a department, a project, a committee.
A channel lives inside a team and splits the work by topic. Every team starts with a General channel you can’t delete, and you add more for specific threads of work: one for planning, one for releases, one for support. Files posted in a channel land in a matching folder in the team’s SharePoint library.
A chat is separate from teams entirely. It’s a direct or group conversation for quick back-and-forth — a question, a heads-up, a small ad-hoc group. Chats don’t have channels, don’t get a SharePoint site, and are hard to search months later. Use them for the conversational stuff, not for work you need to organize and find again.
Which one should you use?
| Ongoing group, shared files, multiple topics | Team |
|---|---|
| A topic or project thread inside an existing team | Channel |
| Quick question or small ad-hoc conversation | Chat |
| External people who need shared files long-term | Team with a shared channel |
The three ways to create a team
In the Teams app, click Teams on the left rail, then Join or create a team (or the + at the top, depending on your client version), and choose Create team. You’ll get three starting points.
From scratch
Pick this when you’re starting clean and the membership doesn’t already exist somewhere. You choose a privacy setting, name it, and add people. This is the most common path and the one you’ll use most.
When you create from scratch, you set the team’s privacy:
- Private — people need an owner’s approval or an invite to join. This is the right default for most teams.
- Public — anyone in your organization can find and join it without approval. Good for open, org-wide communities; bad for anything sensitive.
- Org-wide — automatically includes everyone in the tenant. Only global/Teams admins can create these, and they’re best kept to a small number (all-hands, company announcements).
From an existing group or team
If the people you want are already gathered — in a Microsoft 365 group, a distribution list, or another team — build from that instead of retyping the membership. Creating from an existing team also lets you copy its structure: channels, tabs, settings, apps, and optionally the members. That’s the fast way to clone a proven setup for a new project.
From a template
Teams ships with templates (and admins can publish custom ones) that pre-build channels and apps for a scenario — event management, onboarding, a retail store, and so on. Templates save setup time when your team fits a known pattern. If none of them match how you work, create from scratch and build your own channel layout.
Before you create a team
- You've decided team vs channel vs chat — a team is for an ongoing group
- You know the privacy setting: private (default), public, or org-wide
- You've picked a clear, searchable name that won't collide with existing teams
- You have a second person lined up as a co-owner
- You know whether to start from scratch, a group, or a template
Owners vs members — and why you need two owners
Every team has two main roles, plus guests (covered in the guest access guide).
Owners run the team. They add and remove people, create and delete channels, change settings, manage apps, and can delete the entire team. Members take part — they post, share files, and by default can create standard channels, though an owner can lock that down.
The one rule that saves real pain: give every team at least two owners. A team with a single owner becomes orphaned the moment that person leaves the organization or loses access — nobody can add members, fix settings, or manage it without admin intervention. Naming a co-owner at creation time avoids the whole problem.
To set roles, open the team’s … > Manage team > Members, then use the Role dropdown next to each person to switch between Owner and Member.
Channels: standard, private, and shared
Once the team exists, channels are how you organize the work inside it. There are three types, and they differ by who can see them.
A standard channel is open to every member of the team. Most channels are standard — General, plus whatever topic splits make sense. Everyone in the team sees them and their files.
A private channel is visible only to the specific team members you add to it. It has its own membership, permissions, and a separate SharePoint site for its files. Use private channels when a subset of the team needs a space others shouldn’t see — say, leads discussing budget inside a wider project team. Members of the parent team who aren’t added to the private channel don’t even see it exists.
A shared channel can include people from outside the team, and even from outside your organization, without adding them to the parent team. It’s built on Teams Connect and is the cleanest way to collaborate with a partner org or another internal team long-term, because those people get access to just that channel — not the whole team.
Channel types at a glance
| Standard | All team members |
|---|---|
| Private | A chosen subset of team members |
| Shared | Selected people, including external orgs |
To add one, use the team’s … > Add channel, type a name, and pick the channel type. Note that the type is set at creation — you can’t convert a standard channel into a private one later, so choose deliberately.
Naming teams so people can actually find them
Naming feels trivial until you have eighty teams and three of them are called “Marketing.” A little discipline here pays off across the whole tenant.
- Be specific and searchable. “Q3 Website Relaunch” beats “Project” or “Team 2.”
- Use a prefix or convention if your org has one — for example
SALES-orPROJ-— so related teams sort together. Admins can enforce this with a naming policy in Microsoft Entra. - Avoid duplicating names. Two teams with the same display name are a constant source of “which one did you mean?”
- Remember the email and URL are set once. The team name maps to a Microsoft 365 group email address and a SharePoint URL at creation. Renaming the team later changes the display name but not those underlying addresses, so get the initial name reasonable.
If your organization wants to limit who can spin up teams in the first place — to keep this sprawl in check — that’s controlled at the admin level rather than per team.
Wrapping up
Creating a team is the quick part: click Create, pick from scratch, a group, or a template, set it private, and name it clearly. The decisions that matter are the ones around it — using a team only when you genuinely need an ongoing workspace, naming a second owner so it never gets orphaned, and choosing standard, private, or shared channels to match who should see what.
Get those right at the start and the team stays useful. Next, decide how outsiders fit in with guest access in Teams, and if you’re building out Teams Phone, see how to set up call queues. For more, browse the Microsoft Teams guides.
