How to copy teams chat with Timestamp?

Anonymous
2024-08-19T13:13:28+00:00

Ever since this month and while using the new team application, I can no longer copy teams chat message with the timestamp. I need the timestamp to reference conversations and it would be a pain to add the time and date stamps for every message I need to copy. Also I found that you can copy messages with a partial timestamp by highlighting the chat messages and press control c while holding the right click button on my mouse. This also doesn't help as I get a preview message with double names. It would be a pain to remove part of a line per chat message I am copying. Is there a way to restore the old copying with the timestamp and an option for those who don't want the timestamp. I know skype had this functionality.

Microsoft Teams | Microsoft Teams for business | Chats | Group chats

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

69 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2025-04-10T14:07:53+00:00

    I have found that the workaround is not a very good solution. First it takes multiple tries to get it to copy the timestamp. Then when you finally get it to work the below is what is provided. It is not easy to read and must be corrected before placing in a ticket.

    Has context menu

    Good morning Rick, by Bufford, Yolanda 8:41 AM Bufford, Yolanda Good morning Rick,

    This is Yolanda from L3 SharePoint.  by Bufford, Yolanda 8:41 AM Bufford, Yolanda This is Yolanda from L3 SharePoint.

    We recieved a request from you for an eShar... by Bufford, Yolanda 8:42 AM Bufford, Yolanda

    We recieved a request from you for an eShare Site. I have sent you multiple messages to set up a meeting with Steve and myself. Do you still need the site to be created?

    That is absolutely ridiculous. Please return the function or at the least give us an option to toggle between the two. The date time stamp is essential to business operations.

    Also, there multiple questions on this topic, which separates the hundreds of thousands (maybe even millions) replies as a ploy to do what Microsoft does best ignore the end users by acting as this is not affecting enough people to correct. I and everyone that had to research how to fix this issue would beg the differ. This has been going on for years and it's getting worse by the day. At least before the workaround actually worked as intended without needing to be done multiple times and correcting the final pasted text.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  2. Anonymous
    2025-03-07T22:33:12+00:00

    Any update on this?

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  3. Anonymous
    2025-03-03T21:22:02+00:00

    That does seem to work. But in addition to requiring more work it also seems to capture only one message at a time.

    Good to know, but still not a viable solution.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  4. Anonymous
    2025-03-03T15:46:46+00:00

    Short of using screenshot selections, you can copy&paste the message and the timestamp separately, just not in one grab.

    Annoying, but an option.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  5. Anonymous
    2025-02-27T10:53:20+00:00

    Until we get some answers, when transferring 1 message only and inside Teams, the following function may be :
    On the message's context menu click on "Forward" ("transférer" in french), you need to enter the recipient's name. He will receive the transferred message with timestamp and sender's name.
    Once sended, you may copy the forwarded message with timestamp to paste it into a different app...
    (Beware, keyboard and mouse may age faster)

    edited 5th Mar 2025

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments