SOLVED
Home

Distribution List and existing o365 Groups

%3CLINGO-SUB%20id%3D%22lingo-sub-276212%22%20slang%3D%22en-US%22%3EDistribution%20List%20and%20existing%20o365%20Groups%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-276212%22%20slang%3D%22en-US%22%3EHi%20all%2C%3CBR%20%2F%3E%3CBR%20%2F%3EHow%20would%20you%20approach%20the%20existing%20Distribution%20list%20and%20o365%20groups%20while%20rolling%20out%20Microsoft%20Teams%3F%20What%20are%20the%20challenges%20and%20considerations%20while%20we%20upgrade%20it%20as%20per%20below%20-%3CBR%20%2F%3E%3CBR%20%2F%3EDistribution%20List%20%E2%80%94%26gt%3B%20o365%20Groups%20%E2%80%94%26gt%3B%20Team%3CBR%20%2F%3EO365%20Groups%20%E2%80%94%26gt%3B%20Team%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-276212%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EMicrosoft%20Teams%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-276883%22%20slang%3D%22en-US%22%3ERe%3A%20Distribution%20List%20and%20existing%20o365%20Groups%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-276883%22%20slang%3D%22en-US%22%3EI%20agree%20however%20still%20need%20a%20method%20for%20the%20org%20to%20send%20email%20since%20they%20won%E2%80%99t%20be%20in%20your%20team%20and%20not%20everything%20is%20going%20to%20be%20open%20discussion%20to%20have%20an%20org%20wide%20team%20for%20those.%3CBR%20%2F%3E%3CBR%20%2F%3EOnly%20way%20you%20could%20get%20rid%20of%20email%20is%20if%20we%20ever%20get%20some%20way%20to%20send%20email%20to%20a%20group%20and%20it%20creates%20a%20group%20chat%20and%20replies%20go%20out%20via%20email%20or%20something.%3CBR%20%2F%3E%3CBR%20%2F%3EYou%20could%20tie%20that%20group%20email%20to%20a%20contact%20that%20is%20set%20to%20a%20channel%20in%20your%20team%20you%20could%20but%20then%20you%20can%E2%80%99t%20reply%20to%20it%20from%20inside%20teams.%3CBR%20%2F%3E%3CBR%20%2F%3EAnd%20last%20but%20not%20least%20using%20mailclark%20to%20handle%20back%20and%20forth%20email%20in%20a%20channel%20which%20would%20work%20best%20if%20you%20wanted%20to%20get%20out%20of%20email%20on%20your%20team.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-276871%22%20slang%3D%22en-US%22%3ERe%3A%20Distribution%20List%20and%20existing%20o365%20Groups%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-276871%22%20slang%3D%22en-US%22%3E%3CP%3EKeep%20in%20mind%20that%20emails%20sent%20to%20the%20DL%20will%20not%20be%20visible%20in%20Teams.%20I%20would%20recommend%20to%20get%20rid%20of%20the%20DL%20in%20order%20to%20drive%20communication%20to%20Teams.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-276481%22%20slang%3D%22en-US%22%3ERe%3A%20Distribution%20List%20and%20existing%20o365%20Groups%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-276481%22%20slang%3D%22en-US%22%3EIf%20you%20already%20have%20a%20DL%20with%20a%20name%20that%20someone%20created%20a%20Team%20for%2C%20what%20we%20did%20was%20just%20delete%20the%20DL%2C%20then%20you%20can%20go%20in%20with%20powershell%20and%20replace%20the%20e-mail%20address%20associated%20with%20the%20Office%20365%20group%20that's%20tied%20to%20the%20Team%20so%20that%20you%20have%20a%20single%20e-mail%20address%20%2F%20object%20you%20can%20use%20for%20the%20Group%20and%20Team.%20Just%20make%20sure%20that%20you%20go%20in%20and%20subscribe%20everyone%20to%20the%20365%20group%20notifications%20%3B).%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-276233%22%20slang%3D%22en-US%22%3ERe%3A%20Distribution%20List%20and%20existing%20o365%20Groups%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-276233%22%20slang%3D%22en-US%22%3EYou%20could%20upgrade%20a%20DL%20to%20a%20group%20and%20create%20a%20team%20from%20that%20also%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-276217%22%20slang%3D%22en-US%22%3ERe%3A%20Distribution%20List%20and%20existing%20o365%20Groups%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-276217%22%20slang%3D%22en-US%22%3E%3CP%3EA%20office365%20team%20is%20always%20based%20on%20a%20group.%20So%20it%20makes%20no%20difference%20as%20long%20as%20you%20make%20a%20group%20first%3C%2FP%3E%3C%2FLINGO-BODY%3E
Frequent Contributor
Hi all,

How would you approach the existing Distribution list and o365 groups while rolling out Microsoft Teams? What are the challenges and considerations while we upgrade it as per below -

Distribution List —> o365 Groups —> Team
O365 Groups —> Team
5 Replies

A office365 team is always based on a group. So it makes no difference as long as you make a group first

You could upgrade a DL to a group and create a team from that also
Solution
If you already have a DL with a name that someone created a Team for, what we did was just delete the DL, then you can go in with powershell and replace the e-mail address associated with the Office 365 group that's tied to the Team so that you have a single e-mail address / object you can use for the Group and Team. Just make sure that you go in and subscribe everyone to the 365 group notifications ;).

Keep in mind that emails sent to the DL will not be visible in Teams. I would recommend to get rid of the DL in order to drive communication to Teams.

I agree however still need a method for the org to send email since they won’t be in your team and not everything is going to be open discussion to have an org wide team for those.

Only way you could get rid of email is if we ever get some way to send email to a group and it creates a group chat and replies go out via email or something.

You could tie that group email to a contact that is set to a channel in your team you could but then you can’t reply to it from inside teams.

And last but not least using mailclark to handle back and forth email in a channel which would work best if you wanted to get out of email on your team.
Related Conversations
Tabs and Dark Mode
cjc2112 in Discussions on
22 Replies
flashing a white screen while open new tab
cntvertex in Discussions on
13 Replies
Stable version of Edge insider browser
HotCakeX in Discussions on
35 Replies
How to Prevent Teams from Auto-Launch
chenrylee in Microsoft Teams on
28 Replies
description for autoplay blocking in settings page
HotCakeX in Discussions on
8 Replies