Blog Post

Exchange Team Blog
2 MIN READ

Deprecating Conversion of Distribution Lists to Microsoft 365 Groups

The_Exchange_Team's avatar
The_Exchange_Team
Platinum Contributor
Nov 03, 2022

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

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

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.

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).

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

Updated Nov 03, 2022
Version 1.0

28 Comments

  • Petri-X's avatar
    Petri-X
    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?

  • brodiemac's avatar
    brodiemac
    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:

  • amariak203's avatar
    amariak203
    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'. 

     

    https://learn.microsoft.com/en-us/microsoft-365/compliance/retention-settings?view=o365-worldwide#configuration-information-for-microsoft-365-groups

  • SBirchfield's avatar
    SBirchfield
    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.  

  • Kris_Deb_e2e's avatar
    Kris_Deb_e2e
    Iron Contributor

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

  • KEV1L's avatar
    KEV1L
    Brass Contributor

    WHY?

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