Microsoft Teams Copying Name, Timestamp, and Message

check this out:

reddit post about this

and someone who's happy about it

Feature ID is MC878422.. just google it

Please Microsoft, let us choose!

I agree that sometimes copying was a mess and that might be the reason why some users complained. Sometimes copying was copying things like "has context menu" that didn't belong to the conversation. But to have a choice can't be bad! Make it default if you want but seriously Microsoft. We need this.

Yes, please, please, please, Microsoft: go back to the way it was OR GIVE USERS A CHOICE!! It is imperative to capture WHO said what (and when) not simply what was said.

Dear Inema,

Just about your assumption above regarding a change on Microsoft's backend, I add you in the following the official message about this issue. (I got this info in another thread from me but unfortunately in German, like the whole thread.) But after a short research, I found at least a website from another IT pro, obviously with admin rights to the Microsoft message center. There it was the following message under the same label MC878422.

Microsoft Teams – new message center posts:
Teams copy/paste of messages does not include timestamp and message author name MC878422
Published Aug 30, 2024
"Many users have voiced frustrations over copying messages in Teams, particularly the inclusion of metadata like names and timestamps. Customer feedback has been clear, signaling that this feature was adding more noise than value to user workflow. We are rolling out the change that copied messages are only showing the message content moving forward.

• Streamlined Experience: Most users simply want to copy and paste messages without the extra clutter. Removing names and timestamps from copied content helps maintain focus and reduces unnecessary noise.
• Better Alternatives for Specific Needs: For those who need to forward messages or extract conversations, we recommend using the Forward feature for message transfer between chats, and the Teams Export API for conversation extraction. These tools are more robust and prevent manipulation of message content.

General Availability (Worldwide): Available now and we apologize for not communicating prior to the rollout occurring."

I didn't agree that 'most users simply want to copy and paste message...' in red above. I think the group of Customers who need timestamps/users urgently is much bigger than the others which have a mess with timestamps/users.

I've seen in many other threads and discussion forums that I'm not alone with my meaning... Many other people which need timestamps/users for their daily business, working in support business. And most of them mentioned a ticket system based on simple copy-paste export from Customers requests (like me).

It can also be that such a request is lasting several months, with dozens of chat messages, exchanging lots of technical explanations and documents. In this case, the timestamps/users is urgently needed to avoid a complete mess.

So, I discussed with the involved MSFT in my thread a little bit. Finally, I proposed to add a feature in Microsoft Teams to have as Customer the choice to activate/deactivate time stamps/users in a copy-paste export.

He agreed to forward my proposal internally ('Microsoft Product Team') and come back in this thread if there are some news about that.

Unfortunately and up to now, I didn't hear something that Microsoft will 'move' somehow. Like going back to the previous version incl. timestamps/users or implement an option to activate/deactivate this info by Customers etc.

Thank you very much for your attention and support.

Best Regards,
MarkusR (EXT)

Thank you Beth. I'd say that a screenshot tool is way more practical in my use case. However, in my business, which is a corporate business with lot of quick decisions to take and people to manage, not having this feature is so basic and I am so infuriated with Microsoft any time I update Teams and hope they restored this feature, and realize that they didn't.

Isn't there any, more public and visible, way of communicating this angst to Microsoft?