This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Just getting back to work after vacation and noticed the Conversation button in the top right-hand corner is no longer visible when documents and spreadsheets, both existing and new, are opened in Teams. We use the Conversation button to notify and tag the appropriate channel members that the document has been updated and to share information. This button is no longer available/visible to me; however, it's visible to my associate. See the attached screenshots of a document that was created and opened in Teams.
• Screenshot #1 is from my Teams application (MacBook Pro) showing that the Conversation button is missing.
• Screenshot #2 is from my associate's Teams application (MacBook Pro) with the Conversation button circled in red.
Here are the Teams applications version numbers for myself and our associate. I'm confident that this issue is directly related to the latest version of Teams that was updated yesterday; however, Microsoft Chat Support says that's not the case.
Me: You have Microsoft Teams Version 1.5.00.17261. It was last updated on 6/29/22.
Associate: You have Microsoft Teams Version 1.5.00.15861. It was last updated on 6/14/22.
I've also confirmed that a user outside of my organization running Version 1.5.00.17867 is also experiencing this issue as of this week.
Any assistance would be very helpful.
Additional team and channel-related features and issues within Microsoft Teams for business
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.
Hi AKTeel-
I'm actually running Teams on my MacBook Pro and experiencing the issue.
Thx.
I had my husband check the Teams desktop app on his MacBook, and the Conversation button appears exactly where it is supposed to for him. Does this mean this issue only applies to those of us running Window?
I agree that this is a critical feature that needs to be brought back immediately. The only workaround I have found is to copy a link to the file and then paste that into my post. However, this takes much longer and is terribly inefficient. How do we get Microsoft's attention to this issue?
I had actually opened a ticket with our IT team because I thought a change had been made with access rights to share content. I use the conversations button at least once per week if not multiple times per week and so do many others in the organization. When I built the business case for implementing Teams for collaboration this was one of the key features I presented. Commenting in documents creates a bunch of extra e-mail (if configured to notify) which is the exact opposite direction our organization wants to go. We are attempting to communicate internally using Teams instead of attempting to use e-mail as a collaboration tool. This is a very critical feature and needs to be brought back immediately!
I can’t understand the logic to remove the Conversation Button. We are on a “Asynchronous First” journey within our org and the conversation button is imperative when users link documents into the channel discussion, and continue those discussions whilst real-time collaborating on a document.
Yes I can open the file in the desktop version of the app, and continue the conversation in my Teams client but it really isn’t the same – the conversation button combined with the in-Teams editing ties the conversation and the document as one!
The conversation button in the Teams Files section has been missing for weeks for me as well in both the desktop and web versions. Will this be corrected soon with a future update?