What you need to know
- Microsoft Teams will have an option to delete a private chat thread in the future.
- Right now, you can delete individual messages or hide or archive private chat threads.
- The option has almost 20,000 upvotes on a UserVoice thread.
Microsoft has finally agreed to roll out a highly-requested feature to Microsoft Teams, the ability to delete private chat threads. At the moment, you can delete individual messages or hide or archive threads, but there's no option to completely delete a thread of private messages. That's going to change, according to a Microsoft engineer's response to a UserVoice post.
Alex from the Microsoft Teams engineering team responded to the request:
The ability to delete private chat threads has received a shocking amount of upvotes. At the time of publication, almost 20,000 people have expressed their desire to delete private chat threads.
Microsoft hasn't committed to any timeframe for the feature, so it could be some time before we see it roll out to Teams. People seem to be quite passionate about the feature, as many comments complain that it isn't already available and express doubt regarding Microsoft releasing it in a timely manner.
Several people in the UserVoice thread cite legal reasons as the driving factor behind wanting to delete messages.
Sean Endicott brings nearly a decade of experience covering Microsoft and Windows news to Windows Central. He joined our team in 2017 as an app reviewer and now heads up our day-to-day news coverage. If you have a news tip or an app to review, hit him up at email@example.com (opens in new tab).
This shows the state Teams is in....
Thank the lord, praise Jesus. How many times do you start a chat, add a person or two and really don't need that combo to hang around till Armageddon. Yes you can hide it, but it still hangs around, somewhere. Not like there is a good way to see what's hidden or archived. That would be nice too.
Thank you for signing up to Windows Central. You will receive a verification email shortly.
There was a problem. Please refresh the page and try again.