365 groups VS distribution lists

Posted by BulletRisen@reddit | sysadmin | View on Reddit | 20 comments

What’s the downsides of converting my DLs to groups without enabling the teams feature ? Fresh service can’t add users to DLs so the only way around this is to convert them all to groups. Appreciate any advice

Reply to Post

20 Comments

[-]

emp1r@reddit

Also have in mind that when adding users to the 365 group it will send them a welcome message and if you are converting loads then that might be spam the users. You can use the below command line to disable that: Get-UnifiedGroup it_admins | Set-UnifiedGroup -UnifiedGroupWelcomeMessageEnabled:$false

[-]

EducationAlert5209@reddit

Also, the group owner is not receiving the group emails. Need to set it online to allow in group settings

[-]

_GuybrushThreepw00d@reddit

Is there a way to just disable welcome emails for all groups entirely , not just the existing ones?

[-]

admlshake@reddit

MS says there is if I recall correctly. I've ran the PS command a couple of times, and it seems like after a few months it will get turned back on.

[-]

SingleWordQuestions@reddit

Do a test one, find where it comes from/what the subject line looks like, and sink them with a transport rule

[-]

SenteonCISHardening@reddit

Converting DLs 365 Groups without enabling Teams isn't usually a problem. You'll get more features like a shared mailbox, calendar, and file storage even without the Teams functionality. Just be aware that if these groups are used in address policies or have any specific settings in your email routing, you may need to adjust those configurations. Other than that, it's mostly upsides, especially for management and collaboration purposes. Just give it a test run with one group to see how it goes before converting all.

[-]

realCptFaustas@reddit

You also get a full SharePoint site for that group.

[-]

SingleWordQuestions@reddit

Which will increase the storage required for backups (you do back up m365 right?)

[-]

godspeedfx@reddit

Creating a 365 group creates a lot of extra fluff that you may not want.

[-]

department_g33k@reddit

>a lot of extra fluff Calendar, Group entry in outlook, Teams (unless disabled), etc.

[-]

hardcorebiker@reddit

You will lose moderation options. If that's something you use. Any automation will need to be redone using graph. Those are the problems I can think of off hand.

[-]

ramman0325@reddit

Biggest drawback o found is no nested groups

[-]

Maurer97@reddit

You can get around this by utilizing dynamic groups and querying the GUID for membership. A neat way to get around the no nested groups allowed for m365 groups.

[-]

BulletRisen@reddit (OP)

Hmm can I nest the o365 group in another DL ?

[-]

rezzyk@reddit

Groups are more like shared mailboxes than distribution lists. So it depends what you are looking for. Also I absolutely hate the way the inbox works on groups.

[-]

PessimisticProphet@reddit

Make sure you set them up properly because last time i used a 365 group as a DG, no one got emails like it was a DG, it just went into the shared mailbox associated with the group.

[-]

thelizardking43@reddit

Correct, that's a setting that needs to be enabled. Its also worth noting that a group does not send the sender a copy of a sent message, whereas a DL does.

[-]

jM2me@reddit

The answer lies in Graph API. You can call graph api endpoint to add user to DL in Automator web request.

[-]

PessimisticProphet@reddit

Make sure you set them up properly because last time i used a 365 group as a DG, no one got emails like it was a DG, it just went into the shared mailbox associated with the group.

[-]

Just-a-waffle_@reddit

Can freshservice run powershell scripts? We use Adaxes for AD user automation, and it integrates with AAD/o365, manages the token auth itself, and I can have powershell scripts execute automatically to perform actions in the cloud based on all sorts of stuff