Forum Discussion
Adding Conversations inside MD Teams; using Outlook Vs using the MS Team desktop application
Confusing isn't it john john ?
Conversations inside Teams is a channel conversation
Conversations as visible inside the SharePoint site is a shared mailbox in Exchange so email to the office 365 group address will land here.
They are in no way related. I tend to remove the Conversations link in the SharePoint site if not used - to avoid this confusion amongst users.
Ian Moran wrote:Confusing isn't it john john ?
Conversations inside Teams is a channel conversation
Conversations as visible inside the SharePoint site is a shared mailbox in Exchange so email to the office 365 group address will land here.
They are in no way related. I tend to remove the Conversations link in the SharePoint site if not used - to avoid this confusion amongst users.
Ian Moran thanks for the reply.. but all the UI and the way they are presented makes users think that the 2 conversations are the same .... this is really confusing .
now in my case i want to have a conversation (chatting) features inside my sharepoint site (similar to conversation inside MS Teams desktop app), but we want to do the conversations from the sharepoint site itself using a web browser rather than using desktop app, so can we benefit from the conversation we got ?
Think of it this way. First of all we had Office 365 Groups, with an associated group SMTP address. Email to the group landed here. This was great for support related groups - eg support@company.com. Everyone in the group could see the email and respond.
Then along came Teams. This is layered if you will on top of the Office 365 Group. Each channel in the Team has an associated SMTP address. The Team itself does not have an SMTP address - the underlying Office 365 group does.
How can this be used ? Well, you could still have email coming into the Office 365 group - visible as Conversations in the SharePoint site. You could then have internal discussions around this email inside a channel by forwarding that email into the appropriate channel (right click channel name to grab the address)
Ian Moran wrote:Think of it this way. First of all we had Office 365 Groups, with an associated group SMTP address. Email to the group landed here. This was great for support related groups - eg support@company.com. Everyone in the group could see the email and respond.
Then along came Teams. This is layered if you will on top of the Office 365 Group. Each channel in the Team has an associated SMTP address. The Team itself does not have an SMTP address - the underlying Office 365 group does.
How can this be used ? Well, you could still have email coming into the Office 365 group - visible as Conversations in the SharePoint site. You could then have internal discussions around this email inside a channel by forwarding that email into the appropriate channel (right click channel name to grab the address)
Ian Moran But the chat i am thinking of is something similar to modern team sites chat or yammer chats ,, as we are working on building our intranet community site, where this site is an free area to start conversations and share photos, i thought the conversations tab inside modern team site will do this job for us, but it is not intended to be a real chatting in the way we want. so i am left with 2 options; using the commenting capabilities inside modern page, so when a user want to start a new chat he will create a new modern page, but the issue is that comments inside modern pages can not be backup-ed using any tool (as they are stored outside the site collection, in a onedrive as i read before), also any user can delete others comments and the deleted comments will not be stored inside the site collection recycle bin!!!!. i have not used yammer before, but not sure if it will provide a more professional chatting capabilities. and if users can start a new yammer chat from sharepoint..
- SharePoint itself doesnt offer this chat capability, and probably never Will! What it does offer is the capability to add web parts to it, for example Yammer, which is the tool to use for org wide communication!
