Best Practices - When a DL is not eligible to be converted to a O365 group

[Tanya Arora]

In our company, there are very few DL's that are eligible for conversion to O365 group. As we are starting to use Teams more and more, we end up creating a lot of duplicates. There are legacy DL's and now there are DL's created with creation of the new Team/group. People are often confused where to send emails; to a new group DL or the legacy DL. Are there any best practices around how to retire legacy DL's?

[#2]

Simply assign the email address(es) to the newly created Group/Team? Any user that is subscribed to the Group will still receive the messages in their inbox, and a copy will be stored centrally, so you should have any issues with them.

That's assuming we are talking about "plain" DLs used to only distribute mail, if those are mail-enabled security groups (used to delegate permissions too), best leave them be.

[#3]

Thanks for the suggestion!
If we look at the admin center there are very few DL's that are eligible for conversion. I guess we will have to check each DL to confirm if they are security groups and then take necessary action. Seems like too much manual work. Wondering if MS is coming up with some direction. 

[#4]

There can be many possible reasons why a DG is not eligible, check the FAQ here: https://support.office.com/en-us/article/upgrade-distribution-lists-to-office-365-groups-in-outlook-...

[#5]

Yep.. I went through this list. Thanks