Connect with "Groups" conversation in Outlook
I was surprised that conversations within Teams doesn't show up inside the conversation thread in Outlook Groups. Please consider at least connecting the "General" channel with the Outlook Conversation.
Thanks for the feedback.
We are considering a number of ways to better integrate experiences across Teams, Outlook, and other apps. However, we don’t have any specifics to share on this request.
It is hard to actually create this, because you probably don't just want to copy everything in to a channel as an 'email post' (you still want to be able to reply in email, for example) but it would be good to have a place for this sort of thing to live - even a top tab app that's part of the team by default in the General channel would be good.
At the moment, there's a whole side of the Group (which is attached to the Team) that you just can't see within Teams.
When people in the organisation email the Groups as distribution lists, trying to get an email to all the members of the team, you have to get the 'subscribe members' settings just right. But if each team had a place for the emails to go, everyone could unsubscribe and just look in the Team. Most of our users don't use Groups the way they were designed, because Teams came along just afterwards and we hadn't really started using Groups like forum posts.
A tab that goes to the Group conversations in Outlook for Web could work, but it's clunky.
As it is now, I'll have to disable existing distribution lists in order to implement Teams. That is not kind to user who would prefer to stay with what they know.
No updates in almost a year on this issue.
Besides the new feature of automatically hiding the Group feature when creating a new Team.
Since part of the Group features is integrated with Teams (i.e. file shares in General), I was seriously dumbfound when I learned about Group messages IS NOT synced with Teams messages.
I mean, how are we to convince the Outlook die-hards to even consider Teams when they can't access the old conversations?
The only way would be to stop using Groups cold turkey and ignore the old conversations (or have some poor guy transcribe the content to a Teams channel by hand).
This is a big stumbling block trying to get a non technical team on board for using teams.... things like this hare huge blockers to adoption and make buy-in really difficult.
How are Teams group calendars added to Outlook 365
Gidi Hazan commented
i don't get notifications from the group to my email
Sophie Hannachi commented
Not really agree. I think conversations must take place in Teams ... and not in Outlook. What is the aim (except having conversations dispatched in different places....
Planner "buckets" and Teams "channels" should integrate so comments in a planner task nested in a bucket is a comment in the relevant Teams channel.
Mike baker commented
having a separate group conversation thread that doesn't appear as a channel in teams is starting to give us a lot of negative "we should go back to Slack"
Gary Bampton commented
This is a significant user adoption challenge. Having created Teams from existing Groups and adding in a tab for the Planner, any comments in Planner appear in the Groups in Outlook. Trying to get users to buy into Teams when the conversations appear in Outlook defeats the purpose. Teams has the potential to be a single pane of glass into core O365 apps but is shooting itself in the foot if Groups conversations force people back to Outlook for internal comms.
Julian Smith commented
I have seen that people want their Team's chat threads don't appear in the conversations in Outlook, and Vice Versa the Outlook Chat Threads need to appear in the Teams chat. I have found that if you are sharing a task from Planner with the Group and the Team - then the updated comments on the Task are replicated in both the Conversation in Outlook and in the Planner Task in Teams, and if you add to the comment in the Outlook Conversation Thread it also updates the Comment in the Task Update pane.
It also generates a rather annoying and unwanted email which I can only remove with an Outlook Rule to delete all emails sent to the entire Team.
I assumed that the two bidirectional sync would work, so this is a vital update required to make the experience seamless please
Mark Burland commented
Some of the comments here are absolutely spot on. Like verbatim what I am thinking. If complete strangers can look at and use a product and end up thinking the exact same things, why can't the dev teams at MS also?
Paula Wu commented
It is expected. Please keep the history.
It should be possible and it should be an easy task for MS professional support team.
Christian Schäfer commented
I fully agree. Having separated conversations in the Outlook Groups and in Teams makes no sense. We never used Groups before Teams was introduced and naturally I assumed that in my Outlook I could see Teams conversations and/or just forward mails to the team. Turns out this doesn't work!?
One major issue is that comments in MS Planner are sync'ed up with Outlook Conversations, but not the Team General Channel. If we are tracking projects with Planner, then Teams essentially becomes useless as a conversation repo.
This is pretty bad. Merging the two conversations would be one way to start, but I think given the ease of Teams, it might be good to remove the legacy Outlook Groups conversation altogether and to provide a more seamless experience between Outlook and Teams.
This is a must have!
David Conradie commented
I see I've duplicated this idea with one I posted a little while back - https://microsoftteams.uservoice.com/forums/555103-public/suggestions/31532350-surface-groups-email-conversations-as-teams-cha
@suphatra.... can these two ideas be merged?
The best lure to MS Teams is that it has integration with Outlook. Without this feature it is a hard/complicated sell.
[Deleted User] commented
extremely confusing choice to split conversations
the worst part of it is that users assume that it would connect, and that's where errors and miscommunication happen.
thank you for making us look bad/stupid/inefficient!
users automatically go back to slack with this kind of masterful decision, well done, this will end like groove and MS phone