Unable to remove member from Teams group chat

NarasimaPerumal Chandramohan

Accidently added few members to a Team's group chat, but I don't find option to remove the members. Whether the newly added members can see the old conversations? Is there any indirect way to remove members?

72 Replies
Is it that you can't see those members you added, or how to remove any members?
To remove members from the Team all you need to do is:
1. Click the ... to the right of the team name and select "View team". You will be presented with a members listing.
2. Hover over the names of the people you want to remove, on the right side an X will appear that you can press to remove them.

You could also try removing them from the Office 365 Group.



I meant in the group chat option, not the teams. In teams, i can do so.



It has been suggested to many in Uservoice. I hope it will be fixed soon too.



Has this been implemented?

@NarasimaPerumal Chandramohan wrote:



I meant in the group chat option, not the teams. In teams, i can do so.




In the Chat (NOT Teams/Channels) function of Teams, adding another person to the chat does not give them a historical view of what was said with the other participants before you added them. You are in essence creating a brand new chat space for that new increased group of people.


This means if you've added someone by mistake, just start a different chat with the original people you wanted to chat with. No need to remove anyone.


You can confirm this on this support page in the 'Messages' section: https://support.office.com/en-us/article/Frequently-asked-questions-f4644010-d5fa-4055-b42a-6a531731...

What if the original group with let us say 10 users chat has a long history and is still active? Those 10 users would probably not want to start over just because someone was added by mistake.


It seems like more user friendly to allow the initiator of group chat to remove users that were added by mistake, and also giving the one who was added the option of leaving.

As far as I know, they would not have to start over. You'll see when you start adding people to a new chat, that the screen starts displaying any historical conversation that has already happened among those people. So if you go back and start a new chat without the accidentally added person, all the history should just show up.


I think we're trying to apply the concept of a chat "room" to person to person chat, and that does not seem to be how the backend of the Chat functionality works. Teams/Channels works that way; you're in effect chatting with a Channel, and others have access to that Channel to see the persistent chat history that is stored there. Chat is chatting with people, so it feels to me like some sort of permissions is being stamped onto each chat message when it is sent saying who has access to see it.

Keeping the history is nice.

But it seems to me forcing restart a group chat and adding all participants again if someone was added by mistake or want to leave, is more of a workaround than a solution.

When Hovering over a member name I do get the member details, however without any option to delete/remove, nor X or similar.



--- Moshe


Maybe a feature request, but if I want to leave a chat can I?



To me it's a must have feature to be able to remove participants from a group and also allow participants to leave if they are no longer interested in the group. We shouldn't have to start a group just to remove someone. It's a big gap for companies like us who use group chats regularly. 

You should be using Teams and Channels for that use case, as it fits all of your needs you described. Chat is slightly different, and generally fits a more private communication use case.

I started a new conversation after someone accidentally added people to a private chat. The history did not move over. There really should be a way to "undo" an accidental addition to a private chat. 

I'm sorry but that is missing the point. Chat is an adhoc group that I and others can create as and when needed. I shouldn't have to create a Team and Channels for such adhoc discussions. But it doesn't mean that it shouldn't have the flexibility of adding and removing participants. I can do this on other chat apps!

Features have (or will be shortly) arriving to allow users to leave a chat on their own.


Removing someone from a chat implies some sort of ownership, and there is no concept of that in Chat in Teams currently. Everyone in a chat is equal. In the Teams/Channels side, there are Owners and Members which allows the capability you're looking for.


I would encourage you to submit your use case/scenario to UserVoice! https://microsoftteams.uservoice.com/forums/555103-public

Everyone is always free to leave the groupchat when they are added. But not in the Teams desktop app because the button is missing ;)

I agree that it would be nice that a member in the groupchat can be removed when you added a person by mistake. But then a whole new level of permissions needs to be created and managed, because probably only an owner of a groupchat can remove members and so on. Whole new challenge.

Right now it's easy and clear. If you are added to a groupchat, you as a member can leave whenever you want.  Including the person who started the chat can leave the conversation.

Let's see how the groupchat development continues. :)



You can do it from the desktop client as well now, but the functionality is a bit hidden.


  • Click the "Participants" link on top of group chat
  • Select "Leave"


Hi Johan, thanks for the screenshot. I did some extra digging why it didn't work... because I expected the Leave button also in the desktop client.

Solution = When you enable the developers preview the 'Leave' groupchat button is missing. Disabled the Developers Preview and the button is back.  :) 

For some background on why that is happening, it is because the Developer Preview is actually a completely different deployment ring and it seems to have not gotten the Leave functionality yet.

Thanks for your response! I see that a new feature has been implemented that allows members to leave Group chats. This is definitely an improvement. I would also like to see permission to allow provide Group owner to remove members from a group. When is this likely to be available?

Group owners can remove members from groups now, and always have been able to.
It can be done from Outlook: https://support.office.com/en-us/article/Add-and-remove-group-members-in-Outlook-3b650f4a-5c9b-4f94-...
Or via SharePoint as well.

Hi Loryan,
Thanks for your input but this conversation is about group chat in Teams and not about removing people from an Office 365 Group. ;)

From what was written earlier in this thread, it looks like granting group owners / creators the right to would need significant changes in how ownership rights works. Because of that it will not be implemented.

Yes I know, I was the first person to respond in the thread.
However the comment I was referred to was "I would also like to see permission to allow provide Group owner to remove members from a group" - the lack of the word "chat" changes the intent of the question/statement. :-)



I hope you are not serious when you say it looks like granting group owners/creators the right to would need significant changes in how ownership rights works. Because of that it will not be implemented.


You have this feature already available on Teams for Channels! Also, I don't understand how you could categorically decline a reasonable request from many users based on something requiring significant changes. Isn't that down to MS to figure out why this feature wasn't available to begin with when most other chat apps in the market provide it very easily?

Hi Alok,


I just summarised what I read on the subject so far. :-)


Not saying I agree with the decision,or that they might not change it in the future, but it looks like there are big enough changes to make it a lower priority for now. If I misunderstood this, anyone with better knowledge can feel free to correct me.



This is not a matter of equality or personal worth? LOL! I supervise some guys, and we have a Chat set up for just the guys I supervise. One has left my team, and I need to remove him from the CHAT, but can't. So, in this sense, I do "own" the chat, as it's a resource provided by my organization for communication, and the participants wouldn't be in this chat if they weren't in our employ. This needs a fix, and not a work around.

I appreciate what you all are saying here, but as the tool currently exists you are using it differently than intended and then asking for features that already exist for you if you used it as intended.


For your scenario specifically @Jason Bishop, you should create a Team for the group of people you supervise. That would make you the owner, and all the people you supervise members. This would let you control a ton of options, including membership, and give you far more extensibility options via Apps, let you have team meetings more easily, etc etc etc. It would also allow you to quickly and easily add any future members of this group and instantly give them access to everything that happened in the past among this group as well as all content owned by this group. This is a far better fit for your scenario than using Chat.


You all are trying to put the square peg in the round hole, when the square hole is literally right next to the round one. :)


Also not saying these sorts of things may never change in the future, which is why in this thread I continuously ask you all to get your ideas onto UserVoice so the engineering team can see and review them!

Lol! I have a team for the entire group I supervise. That being said, private conversations can not happen in the team part of the app. We’ve asked for private channels inside each team for a year now, and been told they are coming/not ever coming. So, to work around this app’s inability to have private channels inside a team, we were instructed BY TEAMS to use the chat function for that. So, here we are... by the way, the end user should be able to let developers know that what they have provided could be better if they make a specific change. That doesn’t seem to be the case with Teams.

An overwhelming amount of evidence disagrees with your conclusion. There are literally pages and pages of items here with hundreds and thousands of votes, that Microsoft has responded to and is actively updating as they work through their backlog.


Again, I implore you all, go put your ideas in. The team looks at every single submission.



I just lost data to this bug - is it a lost cause for this to be fixed?
We tried "Teams" for morning scrum meetings. Huge lag 20-30 seconds, no indication that a person is replying, and no alert to inform members that a new message was added. What works for our daily ongoing meeting is the "Chat" feature. Why not give the users (us) the option to remove people if we want to? Let us use the software how we want to, not how someone else thinks we should.
I totally agree. we create adhoc groups frequently...

No, you cannot remove anyone from an ad hoc group that you created. Please note that I'm not talking about a MS Team Group where I already know that you can add/remove team members


I've found that, in the Manage Team area, the 'x' to remove a member doesn't appear for users who are in the Owner role. If you are a team owner then you can change other owners to members first and then delete them by clicking the 'x' out to the right of the Role column.


To head off comments about this being obvious, it is not obvious when all team members are owners.


If assigning user rights/group ownership is a big challenge to come over with, why dont you add a feature as "vote to kick a chat group member" then? 

Having no private group option in Teams section and not being able to kick "resigned" or "added by mistake" users are frustrating. Having a max limit of 20 chat members is an another issue. 

Let me give you an example.
We have a Team for all of our guys in production, works like a charm. However we also have a group chat of 5 members (people on the team with different skillset) where we discuss certain topics that other members do not need to know/read about. Since channel permissions are not a thing, we made a group chat.
In there, we keep files, documents, links, processes, and lots of information.
Are you telling me that, if we need to remove someone for whatever reason, the only thing we can do is recreate the group? what happens to everything we already had?

Other platforms like Discord (who happens to be free) tackles most of these problems. Even Facebook Groups have this.

Either way, I found this on the uservoice page thingy:

We should vote so we can have this implemented soon hopefully.

this is untrue

"the tool currently exists you are using it differently than intended"

That's a disappointing narrow minded response.

What happened to caring about your customers?

If anyone is permitted to add a user to a group chat, anyone should be permitted to remove a user.

We now have a situation where a group chat has a user that has left the business and they show up as "unknown user" and every message results in "failed to send message to one recipient"

Just lazy. this is the "we know best" thinking that brought us windows seven. Get over yourselves.

Maybe should have slept on it before sending that one.

I feel some of the same pains. We have a huge chat going at work that could easily have been a channel or a group. However, a couple of things with UI design make chat more appealing.

The first item is conversation threading. In the desktop version, it's just too easy to start a new conversation when a response was intended. Aligning the behavior with the mobile app version would be helpful. Ability to merge conversations would be helpful.

The second is the extra screen real estate that comes with a new group, especially when it contains only one channel. Would be helpful to fold in channel into the group header when there's only one channel.

Good conversation here - 


It sounds like there are two asks:  

1.  Be able to remove a participant from a group chat.  If you have 4 people in a group chat and one of them was accidently added - there's currently no way for someone to remove them from the conversation, however, they may "leave conversation" on their own show in the screenshot above.  Good ask & I totally understand when this would be useful.  It would be good to know if you prefer to have this necessary for all in a conversation or for only the person who created the initial group chat - I can see value in both but for some, they might not want just anyone removing folks from a chat.  I urge you to include your thoughts here: User Voice Vote: Remove participant from a conversation


2.  Others are asking for the ability to remove "unknown users" from teams AND chat conversations including group chats.  The unknown user is the 'name' applied to someone who has left the organization.  There is work being done to improve this experience, today.  That said, there's a UserVoice item asking for clean up options around these users.  That can be found here: UserVoice Vote: clean up unknown users


There have been a couple of comments around the Teams team not looking at feedback and I want to be very clear that we take our customer feedback extremely serious and view all items.  Although it is impossible to make every change immediately, we absolutely take all feedback into consideration in our planning process and review all items in our community feedback meetings with all feature teams within MSTeams.  Thank you for taking the time to submit your ideas to UserVoice - it really does make a difference!

What a great comment. Thanks very much I will add my voice to both of these.

Hi There. I seriously think Microsoft should provide an option for "group chats" (defined as more than 2 users in a chat) enable the original creator of the chat, to boot someone out.


There are many use cases why this is so:

1. When team members leave a team and work in a different focus group

2. When employees transfer to another subsidary

3. When there is an abusive participant and needs to be booted


If Microsoft truly only wanted to limit the group admin functions to teams, then I would suggest you just Disable the group private chat function, and keep it 1-to-1.


As TEAMS transitions into a full fledged client having full features of Skype4Biz in Q4 2018/Q1 2019, imagine calling a conferencing by pressing the "call button" in the group chat. This then becomes that "Group conference" function, but lacks the full function of skype4biz where conference calls have a presenter, and a participant segregation. 


This chat function is not a simple after thought, and should not be treated as such.



Since Microsoft is serious about being on-par, and BETTER than #SLACK because of the full integration of Skype4Biz into the Teams client, then it should deliver as intended, and not limit the way Enterprise and organisations work, but be fluid and Evolve their application together.

Yes you can leave. Just hover your mouse over the list of names and you will see at the bottom the option to "Leave"

Dear @Aria Chelabian,


Thank you for that response. Leaving a group chat on your own has been widely discussed numerous times, and is not the query here. 


The key phrase is "SOMEONE ELSE".  How do you remove someone(other than yourself) from a group conversation chat (not a TEAM chat).


This issue is still open, and pending many requests for it.

I agree with this. We need more functionality over the Chat feature. The Conversations in the Channels do not update in real time, like they do in Chat. We need more functionality in Chat (Ability to add/delete users, no limitation to users in Chat, etc)

Why can we not remove a person from a chat?

@David Rosenthal wrote:

In the Chat (NOT Teams/Channels) function of Teams, adding another person to the chat does not give them a historical view of what was said with the other participants before you added them. You are in essence creating a brand new chat space for that new increased group of people.


This means if you've added someone by mistake, just start a different chat with the original people you wanted to chat with. No need to remove anyone.


You can confirm this on this support page in the 'Messages' section: https://support.office.com/en-us/article/Frequently-asked-questions-f4644010-d5fa-4055-b42a-6a531731...


Needs it doesn't fit:

1. Group chat with my supervisor and manager to get pto approved, notify of late arrival, etc. If my supervisor has changed (lateral movement to new team), I have to add the new sup and request the old sup to leave the group.

2. The case where my specific team of 4 people has a Team, but it's accessible by all other team leads as we're a testing and technical support group. Because of this, we don't have a private channel. One of our team members went from contract to regular employment, which means new employee number and sign in. That account is now essentially dead (but kept around for archiving purposes) and will always show as an offline member of the group.

It's not a huge deal, but it's annoying for my mild ocd tendencies.

Basically, they are saying that it will take some extra work to satisfy their users requests to improve the app. And they are not willing to do this. Even though the concept for the request makes complete sense and is done by many other platform as mentioned by Alok. I get there are other, more pressing priorities. But a good idea or request should not just be shut down or told that it is not practical or logical to do. All this does is infuriate users and even discourage them from wanting to use your product. "Think before you respond!"