12-18-2017 06:12 AM
12-18-2017 06:12 AM
Currently our chat history is not being stored in the user mailbox conversation history. Everything i can find states that this is where it should be according to the statement below here: https://goo.gl/ZQXmsU
"All Teams 1:1 or group chats are journaled through to the respective users’ mailboxes and all channel messages are journaled through to the group mailbox representing the Team"
Is there a setting or flag that i am missing to turn on retention? I have enabled skype for business retention polices so that they are saved in conversation history?
Is anyone else experiencing this?
02-02-2019 09:15 PM
thank you for the screen shoot, and mine is set that way,.... but.... again i was on a Flight and a message was sent. and NOPE it is NOT in my mail as a missed message nor any message at all. if i understand correly, it should be. so we many Channels and coversatiion, i am having to look at all of them, and this is not a good use of time,
09-26-2019 06:44 AM - edited 09-26-2019 06:51 AM
@Tom Gouldyou are assuming the user remembers that the conversation or information being sought occurred in Teams. That thinking defeats the pervasive search reach approach that is so useful. Microsoft's overall search usability is rapidly declining. Windows search attempted to unify, giving you results from email, OneNote, folders/documents. These have now devolved into islands that you have to search individually. At least with Skype, when you searched in Outlook, you would see email AND chat messages that contained the content you seek.
So there is one reason a user might want access to that folder. Just my $0.02.
12-18-2019 11:25 AM
@Gregg RevakI would say there are lots of reasons. One is that I have a guy who wants his entire conversation history with a particular person to use as documentation. It appears you cannot simply select all and copy in Teams or export it and before anyone starts bringing up Security and compliance content searching, first actually try to use that tool to find said history.
12-18-2019 11:46 AM
@Christopher King Advanced eDiscovery (Office 365 E5) presents all threads from a conversation in a reasonable manner. The problem is that end users can't get to it. But the technology exists to create such a transcript, so I suggest you use User Voice to express the need for Microsoft to deliver a version that's suitable for end users.
01-10-2020 01:17 PM
What is being missed here notwithstanding the get over it remark, is the fact that with Skype you can keep a dual conversation history in Outlook (one for the initiator and one inclusive of the participants that can be referenced back at another point in time or copied for other's awareness. This feature needs to be added to Teams since it's the technology replacing Skype. Software replacement shouldn't change the way people work.
01-10-2020 01:49 PM
@LaurenP Skype for Business and Teams are two very different applications. It's a mistake to say that everything in Skype should be in Teams because that's not the intention. If it was, Microsoft would have simply upgraded Skype for Business. But if you want to lobby for change, feel free to make a case at Teams User Voice https://microsoftteams.uservoice.com/.
The engineering team do review the ideas posted in User Voice and consider them when they make decisions about new functionality. Lobby and vote for change and it might just happen.
02-15-2020 02:12 PM
The fact is that people do not want to find data they generated inside their communication spread all over the place. The desktop app for Outlook is where workers spend most of their day so tracking chats into Outlook or OWA is elementary. Outlook should have a personal conversation history if it is about to replace SFB, channel conversation can also get tracked in Outlook but I will understand if they don't.
02-15-2020 04:32 PM
@Dude1970 I think you're missing the point.
People don't need to know, nor should they, that compliance data for Teams is stored in their EXO mailbox. The fact is that a ton of stuff is stored in EXO mailboxes that people don't know about and don't need to care about. These are just compliance records that really mean nothing to the average user.
05-15-2020 10:51 AM
A simple use case for Teams Chat surfacing in Outlook Conversation History the same way Skype did > someone sends me a Chat with a question that requires a lengthy answer, or action item. I don't have time at that moment to answer or solve it. Before switching from Skype to Teams, when I had this scenario and was ready to respond, I would go to the Conversation History folder, find the Chat, and reply from there. There are many reasons I may want to reply from Outlook v. Teams Chat, one of which is the ability to bcc someone on my response. Either way, the "why" shouldn't matter - users should have the flexibility to work the way that is most effective and efficient for them. I know the ultimate goal with Teams is to steer all of our work there and away from email, but the reality is not everyone is ready to work that way and one size doesn't fit all.