Copy Link is not an option

[EventHorizon]

I wish to share a link to a specific message in Teams chat ... however only options are

Save this message

Mark as unread

Share to Outlook

Translate

the ability to copy a link to a chat message is extremely handy ... its available on say Slack why not on Teams ?   or perhaps its a config setting disabled at my work ?

[#2 · Accepted solution]

It's available for Teams channel messages, but not for chat messages. And it kind of makes sense, as the latter are private by design and the link can only be used by direct participants in the chat (1:1 or group).

[#3]

Slack allows to copy any messages of any channel or chat, private or public. The person that click the link of the message will be able to read the message or not based on the account permission.

Is there any chance to see this implemented in Teams?

Imho is very convenient to be able to refer to any messages, knowing that only the right account will be able to read the message after opening the link.

[#4]

@Vasil Michev 

That would be nice.

But - now one year later - I've got the same problem even within a channel. But the problem does not exist in all channels. In some channels I've got the "copy link" ("Link kopieren" in german) and at least in one, I only have the share via Outlook option /"Mit Outlook teilen").

Does anyone know why?

[#5]

This really needs to be added as one or more persons you chat with directly could be in multiple chart groups (ie user1 & user2 in one group, user 1 user 2 & user3 in another) within the CHAT section and not within a TEAM and when you want to let a user know to check in X chat section for something you left them they have to first figure out which of the many chat groups you and they are in to find the text because there is no direct link. If there was only 1 Chat group for each combination of users that would be fine but that's not how TEMAS works so this really needs to be a thing. Access to read what the link references should be based on who is using the link and that would prevent private chart between user1 & uiser2 from being read by user3.

[#6]

@Vasil Michev 

I think that You can copy link to a massage in standard channel, but it's unfortunatelly not possible for private chanell.

[#7]

Thanks to the comments below I also realized I was unable to "Copy Link" from a private channel.

This in fact strikes me as even a worse potential violation of privacy, facilitating the copy of private conversations into e-mail for distributions. Copying a link is the most private mechanism, if a user is not in the channel they will be unable to read.

This is one of several significant functional gaps I have encountered transitioning from Slack to Teams, I hope Microsoft will continue to improve Chat functionality. Another huge gap is allowing threaded Chats, not just conversations in Team channels.

[#8]

This MS teams feature is broken (as others have stated bellow).

Not having "copy link" prevents me from giving the reference to previous chats. Even if the user was part of the private conversation. All I can say to them is try searching for xyz....

I have over 100 chat channels or conversations to deal with. So giving me a simple way to reference them all should be a given. If it's private just pop an access request screen !

[#9]

I am inviting three people to a Teams meeting. I want those three people to see the message I sent them in Teams chat (the same three people are in that chat), so I wanted to copy a link to that message to paste into the meeting invite. I get the privacy concern in the answer above, but that's solvable. Only people with access to that chat and that message should be able to successfully open the link. This is not the first time I've hit this, and clearly other users except this functionality too. MS, please consider.

[#10]

Exactly, this sums it up perfectly thanks !

[#11]

We have the exact same need. We often take a chat, rename it and make it a standing conversation, and need to send the link out to someone.  I am pretty shocked to hear that we can't do this

MS should get on this simple addition!