Teams Chat - copy/paste

Anonymous
2024-08-28T07:54:37+00:00

When in Chats in Teams we used to copy conversations and paste them into other docs. This brought across name/date and chat text.

Now when we do this it only brings across the text; name/date are missing. This causes issues for us as we cannot keep accurate records.

Has this facility been changed/withdrawn in an update? Is there a workaround?

Microsoft 365 and Office | SharePoint | For business | Windows

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 No comments

83 answers

Sort by: Oldest
  1. Anonymous
    2025-03-31T08:18:45+00:00

    MS this is absolutely ludicrous - throwing my vote in here too

    "Noise" you say, the precise reason for wanting to copy chats out is to get the Name/date time stamp

    the workaround doesn't even work any more.. good on you MS, once again coming up with a solution for something that was never an issue in the first place.

    Was this answer helpful?

    4 people found this answer helpful.
    0 comments No comments
  2. Anonymous
    2025-04-03T21:17:56+00:00

    I see I'm in good company looking for a solution for this issue. This is a poor design choice which could have simply been made optional via a configuration setting rather than removing it entirely.

    There are many, many valid reasons for letting users copy the entire chat stream with details in place. Not the least that the function existed already and people were clearly using it.

    I work in the accessibility area and meeting participants will often provide very useful commentary via chat - some because of their own accessibility requirements. Other users need to copy the chat out to an external document to be able to access it in the way they normally work because of their disability. Removing the names and timestamps creates even more barriers for people with disability and removes important contextual information.

    Giant thumbs down on accessibility and equity Microsoft!
    Perhaps Microsoft could think about the collective time and money spent by MS clients trying to resolve this simple issue?

    The suggested workaround does not work and is not a solution.

    The "noise" has been replaced by "garbage" that requires even more time to reformat, amend and fix to be useful.

    Please look at this seriously Microsoft and provide a solution that is effective.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments
  3. Anonymous
    2025-04-03T21:32:11+00:00

    Yes, it is punishing! I had to download a full page screen shot add-in for google chrome to snippet conversations. (But it's not good because now i'm saving images of conversations, not the text to copy/paste) I run a construction company and we do tenders, a lot of tenders, largish 1-10 million range, and we have a tender chat for each tender. It's critical to be able to show a supervisor taking on a big job, what we considered during the tender phase, so they can quickly get up to speed around tricky detail and allowances. I do wonder if it's deliberate, not allowing a copy paste of entire chats due to some kind of privacy clause. Any who, looking forward to an update here!

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments
  4. Anonymous
    2025-04-04T12:52:51+00:00

    +1 on this issue also - was a useful feature!

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  5. Anonymous
    2025-04-10T15:57:06+00:00

    I too want to comment that this removal of an existing functionality/feature should have been defined as configurable to those supposed users that didn't want the clutter. I want the name and date/timestamps back when I copy chat threads for documentation purposes into Jira. I would have preferred to have just removed the likes and reactions when copying and pasting but once again that should have been configurable option in my opinion. Please get this to appropriate resources to address.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments