How do you copy Teams message without time and sender information?

Anonymous
2022-06-14T11:30:21+00:00

I want to triple-click a message, copy it to the clipboard, then paste it in whichever application, and I don't want to see the header (time and sender information).

Yes, it is possible to carefully select parts of a message, and make sure you don't snag the beginning or end of the message so you don't "grab" the header. This is not what I'm looking for. I want a one-click-solution.

I found this post dating from 2013, about Skype/Lync. I'm looking for the same thing in Teams.

https://support.microsoft.com/en-us/topic/update-enables-users-to-copy-instant-messages-without-author-name-and-time-stamp-in-skype-for-business-lync-2013-42c4ac43-9d14-d2be-ef38-107f15033bf7

Thank you

Microsoft Teams | Microsoft Teams for business | Chats | Other

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

64 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2023-06-09T06:21:20+00:00

    One thing that pisses me off the most is 85% of all the answers offered on this "official Microsoft Forum" don't solve the issue, don't address the issue or seem to be easy answers "to get rid of the bothersome consumer"

    There are a lot of UX issues that Microsoft just doesn't address. Some issues I've found that are 10 years old. Either they are incompetent fools that don't know how to get constructive feedback from their user base, or, they simply don't care. I have a hard time believing they are that incompetent.

    At home, OF COURSE I don't use Microsoft Office. Office makes me miserable (I'm not sure if VSC is part of Office. I will admit I was pretty impressed by VSC). There are so many unpolished and unstandatdized details throughout the whole Office suit... It's like trying to drive at 100k/h with square wheels.

    Where I DON'T have a choice to use Office is at work. MS Office is unfortunately one of the most widespread business standards in the world. And Microsoft knows this. If you can't conform to it's subpar experience and performance, you're condemned to suffering it day in and day out.

    You know... I imagine the Microsoft Office team thinking: "there's nothing wrong with Office". Which leads to the adage : "If it ain't broke, don't fix it"... But I hate this adage.

    Here's my version : "If it ain't broke, make it better."

    And most probably, this is going to end up being just another lost rant, from just another disgruntled user...

    Was this answer helpful?

    6 people found this answer helpful.
    0 comments
  2. Anonymous
    2024-08-16T15:08:03+00:00

    I depend upon the names and timestamps being included in copied messages. I include snippets and conversational history in documentation of work and conversations done.

    I noticed this morning that this has just "gone away". I can't find an option to turn it back on.

    Complainers and whiners are not the only users, and a documented option (or override available on the right-click menu) is the better solution to them, rather than the recent MS trend of just removing (or hiding?) some feature because someone(s) complained about it.

    Was this answer helpful?

    5 people found this answer helpful.
    0 comments
  3. Anonymous
    2023-08-18T13:28:07+00:00

    One way to copy text in Teams is to highlight it and press Ctrl + C, then paste it wherever you want. This is a simple and effective workaround. 😊

    More Microsoft lies.

    Was this answer helpful?

    5 people found this answer helpful.
    0 comments
  4. Anonymous
    2023-06-08T05:23:33+00:00

    It is 2023 now, why is it still not fixed?

    Was this answer helpful?

    5 people found this answer helpful.
    0 comments
  5. Anonymous
    2023-06-07T20:39:54+00:00

    double click the message > right-click > copy

    nope, did not work.

    Was this answer helpful?

    4 people found this answer helpful.
    0 comments