Previously one could add members to mail-enabled security groups via Graph API. But turns out that was a bug, and it was fixed some weeks ago removing this functionality. Would it be possible to allow add-remove of members in mail-enabled security groups via Graph API?
47 Comments
Would be great to get this working with Power Automate! It would be good for ISMS.
I can't agree more
With everything moving to Graph, we need a consistent way of updating Groups, not if it is this type then do Graph, otherwise do some other way...
If automate is to be used to enhance the Microsoft 365 administration experience going forward then we definitely need DLs and Mail enabled Security Groups to be manageable through it too.
It is absurd that I can use an onboarding form and a flow to automate user creation, manage it's security groups and assign licenses but can't add to a simple DL, thus requiring a human intervention just the same.
What's the point of having only a semi-automated process? Should we petition to rename it to Power Semi-automate?
I view this as a necessary feature. Distribution Lists and Mail Enabled Security Groups are a still valid options within Exchange. I don’t see why management of these group types through Graph or Power Automate cannot be restored; this was evidently available in the past.
Not all groups need the collaborative aspects of Modern Groups, DLs and Mail-enabled SGs still serve a function, and should be manageable using the same options.This feature is very important for setting up a clear governance and facilitate the communication. Please bring this feature back.
Please bring this feature to mange distro/security groups back into the Graph API. I have tons of scripts that I am having to use really janky workarounds which are not idea. Thanks!
This feature will be very helpful for our Identity Management project. Thank you.
Hi all. I wonder if there is an progress on this from Microsoft? Or if there is any workaround? Thank you
Seems Microsoft is hesitant to allow the Graph API to action anything in the Exchange workload, as there are no meaningful Power Auto triggers or actions available for that service. You have to do everything using PS via Azure Automation actions. It's not terrible, but seems unnecessary.
Why can't we use PowerAuto to manage Exchange mailbox properties and mail enabled groups? I really cannot justify junking up the list of M365 Groups to include one for every mail+security group in the domain.
