Microsoft Teams Group Chats: Create, Name and Manage Them Safely

A Microsoft Teams group chat is a private, continuous conversation for a defined set of people. It is useful for a small working group, a quick decision or a short-lived coordination thread.

It is not a mini team. It has no channel structure, team-owned SharePoint library or threaded topics, and removing someone does not erase the history they already saw.

Use this guide to create the chat correctly—and to decide when you should create a team or channel instead.

Group chat or channel?

Microsoft's current Teams navigation guidance draws a useful boundary:

Group chat	Team channel
Private to the people added	Visible according to team/channel membership
One continuous, unthreaded conversation	Multiple threaded conversations
Up to 250 people	Designed for a much larger, durable team audience
New participant history is chosen when they are added	Team/channel history follows membership
Files shared in chat are stored in a sharer's OneDrive	Channel files are stored in the team's SharePoint site

Choose a group chat when the people and purpose are narrow and the conversation can remain informal.

Choose a channel when the work needs durable ownership, discoverability, more than one topic, a stable membership boundary or files that should belong to the team rather than an individual.

Meeting chat is a third thing. Its access can depend on the meeting invitation, organiser settings, attendee type and whether it is a channel meeting. Do not use ordinary group-chat instructions as a policy statement for meeting chat.

Create and name a group chat on desktop or web

Microsoft's current Chat with others in Teams procedure is:

1. Select New message at the top of the list of chats and channels.
2. Select the arrow at the right of the To field to reveal Group name.
3. Enter a short, useful name.
4. Add the people in the To field.
5. Write and send the first message.

The first message matters. Until it is sent, you may only have a draft composer rather than a conversation the recipients can return to.

If your Teams layout says New chat instead of New message, use that equivalent compose action. Microsoft changes navigation labels and offers combined or separate chat/channel layouts, so teach the intent as well as the current label.

Use a name that will still make sense later

Good names identify the work and boundary:

• Website launch — decision group;
• Supplier onboarding — August 2026; or
• Payroll issue — case 1842 (only if the name itself is appropriate to reveal).

Avoid Project, Quick chat or a string of participant names. Also avoid putting sensitive personal or case information in a chat title, because titles are visible in lists and notifications.

The opening message should state:

• why the chat exists;
• the expected outcome;
• who makes the final decision;
• where durable files or decisions will be recorded; and
• when the group should stop using the chat.

Create and name a group chat on mobile

On iOS or Android:

1. Open Chat.
2. Tap New message.
3. Add the people in To.
4. Write and send the first message.
5. Open the participant names at the top of the chat.
6. Select Group chat name, enter the name and save it.

The order differs from desktop: Microsoft's current mobile procedure names the chat after the first message.

Add people without leaking the wrong history

In an existing group chat, select View and add participants > Add people, choose the people, then select how much history to include.

Pause before confirming. The history choice is a disclosure decision.

• Include full history only when the new person is authorised and needs the full context.
• Use a limited history option when earlier messages are irrelevant or sensitive.
• Start a fresh group chat when the purpose, audience or confidentiality boundary has changed.

You cannot inject another person into a 1:1 chat while preserving it as the same private conversation. Adding someone creates a new group conversation; the old 1:1 history does not transfer. That protects the original private thread.

Teams supports up to 250 people in a group chat. Treat that as a product ceiling, not a design target. At large membership and high message volume, a channel usually gives better structure, ownership and discoverability.

Manage notifications without muting the work

Group chat is a single message stream. There is no channel-level notification menu inside it.

Practical controls include:

• mute a noisy chat when you do not need immediate alerts;
• mark a chat unread when you need to return;
• add important chats to Favorites or pin where the client offers that layout;
• use an @mention sparingly when a specific person must act; and
• pin one genuinely important message for everyone when that feature is available.

Muting changes notifications, not membership or access. It does not stop messages arriving and it does not hide the chat from other participants.

Do not @mention every participant as a substitute for a clear request. Put the decision or action at the start of the message, name the owner and give a date.

Share files with the storage model in mind

Microsoft's Microsoft 365 storage guidance says files shared in a private or group chat are uploaded to the OneDrive for work or school account of the person who shares them. Channel files live in the team's SharePoint site.

That distinction affects ownership and continuity.

For a working attachment or quick review, chat sharing may be fine. For a final policy, project deliverable or record that must survive staff changes, put the file in the governed SharePoint/Teams library and share a link into the chat.

When a chat member cannot open a file, check the file's OneDrive sharing permissions—not only whether the person appears in the chat. Chat membership and file access are related user experiences, not one permission object.

For more detail, see our companion guide to managing attachments in Teams chats.

Leave or remove someone

A member can leave a group chat. They stop receiving new messages and can rejoin only when someone invites them again.

Microsoft's leave and remove guidance says participant removal depends on an administrator enabling the setting. In a chat of three or more people, an allowed member can open the participant list and remove someone.

The removed person:

• keeps access to previous messages they could already see;
• cannot send or react;
• cannot see future conversation; and
• cannot see new files shared after removal.

Their existing messages remain in the group history.

Therefore, removal is not retroactive erasure. If a person should never have seen earlier content, the failure happened when they were added or when too much history was shared.

For an employee departure or security incident, do not rely only on the chat menu. Follow the organisation's identity, device, data-access, retention and incident-response procedures.

External participants need a deliberate decision

Organisations can configure external and guest collaboration differently. A user may appear as an external chat participant, a guest in your tenant, or not be reachable at all.

If a person cannot be found or added:

1. confirm the exact address and tenant;
2. check whether the intended model is external access or guest access;
3. ask an administrator to review Teams and Entra policies;
4. test file/Loop capability separately from plain chat; and
5. avoid moving confidential work into an unmanaged consumer channel as a workaround.

The ability to exchange a message does not prove that file sharing, meeting chat, Loop or retention behaves identically across tenant boundaries.

A simple group-chat operating rule

For any group chat that lasts more than a few days, assign one person to keep the durable record elsewhere.

At the end of a decision:

1. write a short outcome message;
2. store the final document in the team-owned location;
3. link the decision or file from the chat;
4. identify any owner and due date; and
5. close or stop using the chat when its purpose is complete.

This prevents a private message stream from becoming the only place an important decision exists.

If you only need the basic 1:1 procedure, use our shorter guide: How to start a new chat in Microsoft Teams.

For practical Teams and SharePoint administration patterns, join the SharePoint & Teams Admins Space.

Frequently asked questions

How many people can be in a Microsoft Teams group chat?

Microsoft currently documents up to 250 people. That is a limit, not a recommendation; use a channel when a large or durable audience needs structured topics, stable membership and team-owned files.

Can a new member see old Teams group-chat messages?

When adding someone to an existing group chat, Teams lets you choose how much history to include. Treat that choice as a data-disclosure decision and start a new chat if the audience or purpose has changed.

Can I add someone to a 1:1 chat without sharing its history?

Adding another person creates a new group chat. The original 1:1 history does not transfer into that new conversation.

Does removing someone delete the old chat for them?

No. Microsoft says a removed person can still see past messages they had access to, while losing the ability to send, react or see future messages and files. Removal is not retroactive erasure.

Where are files shared in a Teams group chat stored?

They are stored in the sharer's OneDrive for work or school. Channel files are stored in the team's SharePoint site, which is usually the better home for durable team records.