Deprecating Conversion of Distribution Lists to Microsoft 365 Groups
Published Nov 03 2022 08:43 AM 31.6K Views

When Microsoft 365 Groups were launched as a collaboration tool, we introduced a feature in the Exchange admin center and PowerShell to migrate existing distribution lists (DLs) to Groups. This feature was designed to provide continuity for DL users and to enable continued collaboration without having to make new groups from scratch.

As Microsoft 365 Groups is now a mature feature, we are deprecating the feature for migrating DLs to Groups. The deprecation will happen on February 1, 2023.

Post the deprecation, you can use the following process, to convert eligible DL to a Group. In the Exchange admin center, create a new Group with the following properties:

Group Type: Microsoft 365

dltogroup01.png

Give it a temporary name, like for example tmpGroup and assign it a temporary email address like for example tmpgroup@contoso.com:

dltogroup02.png

As Group owners, assign the owners of the DL that you are trying to convert, and do not add and group members at this point (unless the original DL has just a handful of users).

Next up, use the Azure Active Directory (Azure AD) portal to export the members of the original DL to a CSV file.

dltogroup03.png

In the Azure AD portal, add members to the tmpGroup using the CSV file downloaded in step 2 (adjust the file format according to the sample provided).

dltogroup04.png

Once the bulk import has completed, use the Exchange admin center to delete the original DL and then update the name, email, and alias of the tmpGroup to replace the original DL.

If you’d like a refresher on Microsoft 365 Groups, please see Overview of Microsoft 365 Groups for administrators.

Microsoft 365 Groups team

28 Comments
Brass Contributor

WHY?

How can you read the process in this document and think... "that's better"?

Steel Contributor

I really don't understand the point of this deprecation. I thought we are all going into automation and optimisation. 

Copper Contributor

This is ridiculous change.  Granted, the conversion isn't great now but it is at least a somewhat automated process.  Why not provide tools to do the conversion?  I have been fighting with converting DL's over for a few months now and have come to realize that Groups are not a mature product.  There's a 50GB cap with email and it appears that the cleanup process with a retention policy also includes the data in other aspects of a Group like files and conversations. At this point I find that Groups are half baked at best.  Maybe that's the point of this, make it harder to convert to Groups so people won't do it.  

Copper Contributor

This has to be a joke...

Brass Contributor

Hey guys, April first is still several months away.

Copper Contributor

@SBirchfield Are you sure about the retention policy part? I have not used it yet for group mailboxes, but am exploring the Groups functionality and based on the documentation, you should be able to modify the retention policy created for the Group and change the Applications parameter to either 'Group:Exchange' or 'Group:SharePoint'. 

 

Configure Microsoft 365 retention settings to automatically retain or delete content - Microsoft Pur...

Copper Contributor

This is quite possibly the dumbest thing I have seen Microsoft do to date.  You want people to use M365 groups, yet you take away the tools they can use to upgrade DLs to do it.  That's smart.

:facepalm:

Bronze Contributor

@The_Exchange_Team you wrote:

"As Microsoft 365 Groups is now a mature feature, we are deprecating the feature for migrating DLs to Groups. . . "

Have you though that for making this decision you have had invalid data available? Before you are taking the converting tool away from users, don't you should preventing them to create more DLs to be needed to convert to groups later?

 

Also do you have some plan for the future of DLs?

Why would anyone at Microsoft think this is a wise idea?  What is the cost of keeping a simple feature around to help organizations convert groups in the future?  This will only stunt the conversion and adoption of Microsoft 365 groups.  Seems to be a trend at Microsoft, how do we take a good experience and make it bad for people who pay us money for good features?  I do hope this is a joke.  A bad joke.

Steel Contributor

@The_Exchange_Team wrote:

...

As Microsoft 365 Groups is now a mature feature, we are deprecating the feature for migrating DLs to Groups. The deprecation will happen on February 1, 2023.

...

I don't understand what one has to do with the other and I don't understand why something so simple, yet effective is deprecated. The maintenance cost of this can't be more then a handful of hours a year.

Iron Contributor

I would honestly love to understand the thought process behind this decision. 

Is this meant to encourage people to not create DLs anymore?

 

Do you have metrics that indicate established EXO customers are no longer creating DLs?

 

Will there not be a process for newly onboarding customers to migrate their on-prem DLs to M365 groups?

 

Has Microsoft and customers experienced a high frequency of failures with this tool?

 

Is the tool expensive to maintain and support?

 

Please reconsider.

Iron Contributor

you have got to love microsoft's new approach, remove something and don't engage with the customer. post a blog under a generic name so that no-one can possibly register any feedback or ask questions about it.

Copper Contributor

Does this affect hybrid environments?  Do we need to update our local DLs to email enabled security groups?  I'm also with everyone else on the confusion of why this change is going into effect, it doesn't seem necessary.

Copper Contributor

IT Admins: Hey look - a cool automated tool to convert legacy lists to modern lists in the cloud! What a time saver!

Microsoft: This makes too much sense. Hold my beer.

Microsoft: New Feature Announcement! We are taking away this feature. 

IT Admins: Wait, what? Why? April fools in February?

Microsoft: Deal with it. Chat GPT is coming for all of our jobs anyway. 

ALL YOUR BASE ARE BELONG TO US. 

Copper Contributor

I am just starting our company project to migrate DL to M365 Groups.  I've been prepping and planning for many weeks.  However, I go to migrate my first production group this week, and can't find the button I had done tests with for mnths.

Never saw this blog post until now,   Who ever thinks that REMOVING features is a good idea.

 

I would have started this project monnths ago, but the Broken Advisor for Teams rollout tool pushed that project back for so long... and only support will acknowledge it is broken.

 

Microsoft, get your act together...

Copper Contributor

What is the point of removing the functionality? This is a very lame excuse, come on Microsot, bring this back ASAP, there are still some of us migrating, you can remove it in 2039 if you like.

 

Copper Contributor

I'm confused now... So Microsoft is deprecating this feature for admins and removing it from the Exchange Admin Center, but it is introducing a new feature that allows admins to trigger the upgrade by the DG owners themselves (MC510333 - Allow End Users to Upgrade Distribution Lists to Microsoft 365 Groups - M365 Admin (handsontek.net))?! Is the admin-driving conversation also being removed from the Microsoft 365 Admin portal?

Copper Contributor

It looks like this functionality remains as part of the M365 Group creation. There is a parameter that allows you to define the DL that you want to migrate to M365 group. -DlIdentity

New-UnifiedGroup (ExchangePowerShell) | Microsoft Learn

Brass Contributor
Copper Contributor

I suspect that the information given here could be quite misleading.
There is no mention of a simple follow-up process, which IMHO will become common and here to stay forever.

See M365 Changelog: (Updated) Allow End Users to Upgrade Distribution Lists to Microsoft 365 Groups.

 

Copper Contributor

Dear Team,

I have a question for the expert.

Tell me, what will happen if I did not upgrade the DL to O365 and remove the on-prime exchange server completely? is there any impact on the existing DL mail flow or should I migrate to O365 before removing the on-prime exchange?

 

Please clear me.

 

Thanks and Regards,

Shahir

Copper Contributor

What on earth did Microsoft decide and remove this little cool feature?

Yesterday one of our service desk members created a DL on the request to create a group, which led me to this post and scratch my head now.

 

Copper Contributor

@rsaddey I've tested myself by following what the website talks about the group conversion.

This is the screenshot of me sending a request to the group owner:

VanVuite_1-1693265066065.png

This is how the requested email comes to the group owner:

VanVuite_2-1693265173941.png

"Something went wrong..... please contact your admin".

Now we are living in this world of "Something went wrong" that we do not know what would be the 'something' and where it 'went wrong'.

If someone knows how to fix this 'Something' and successfully converge DL into a 365 group, please help us!

 

Microsoft

@VanVuite, I would suggest capturing browser traffic trace (.har) and check the underlying error which should give an idea about it. Please refer to the article shared below to capture the logs. 

 

Capture a browser trace for troubleshooting - Azure portal | Microsoft Learn

Copper Contributor

@The_Exchange_Team 

Please make this process better. Not encouraging us to migrate here!!!!

This makes absolutely not sense at all. I would listen to your community here.

 

Copper Contributor

Hi Just looking for some feedback, I can see the thread is old, but wanted to understand.

 

We have our SharePoint / Teams sites.  What is the benefit of migrating Dynamic Distribution lists to M365 Groups?  yes I know that DDLs have fewer features, but they also don't create a heap of SharePoint stuff that won't ever get used. Why are you converting? What is the benefit? I am just trying to understand why not to continue with DDLs over M365 Groups?

 

Thanks

 

Peter

 

Copper Contributor

Date is 06MAR2023 and the distribution lists still stands . I don't think DLs are getting deprecated. 

 

 

 

 

Copper Contributor

4/24- tasked with upgrading basic Distribution groups.  The gui and powershell ways to upgrade DG's did not work.  I understand dynamic groups will automatically pickup users, Obviously the Dynamic group Import Bulk option is greyed out. So, I'm guessing the Bulk Export is just a reference guide to make sure all the users are picked up correctly.

 

My question is why all the documentation explaining how to do it if none of it works? In my understanding of how Dynamic 365 groups work, once they set, the rules can be changed but Users cannot be manually added. It would be easy if MIcrosoft would just explain this.

Co-Authors
Version history
Last update:
‎Nov 03 2022 08:42 AM
Updated by: