Allow addition of members to mail-enabled security groups via Graph API

Yes, please add the feature! Onboarding solution is almost uniform with graph, except for mail enabled sec groups and distro lists. What even!? Now I have to resort to some roundabout ways to implement it (azure fn-s?). Maintenance will have me nailed to the cross when they find out eventually.

@Darrel Miller Yes, would like to see it added back to the Graph. It is stupid that you can GET a list of members in a mail enabled security group, but you can't add or remove. 

I also agree with @lboonekamp . It should be part of the Graph API. 

DarrelMiller It sure would be nice if somebody at Microsoft would make a final decision on whether or not Graph is going to be the unified API framework. It's complete crap to have Microsoft telling developers that X, Y and Z are going away, and we should use Graph, but--wait for it--what you are doing right now in X, Y and Z isn't supported in Graph.

Hi, I agree to lboonekamp . It should be part of the Graph API because nearly all other groups , rights and user manipulations can be done there in an automated way.
So manipulation of all these instances in Graph is the only way that makes sense. 
Regards, JJ

feelie75 We are actively working with many teams to bring admin scenarios such as SharePoint settings, Service Announcements, Edge management to Graph.  It would be disappointing if customers end up having to a different API and get a different token for certain M365 admin operations.  Having said that, I understand that you just want the capability to be made available.

lboonekamp It is not really a case of someone thinking it should not be on Graph.  It is more a case of the effort to bring it to Graph could be spent working on other customer requests.   Yes, if it was a different API then it would require a different token.

Thank you both for your feedback.

DarrelMiller thanks for your input. I'm struggling to understand the reasons why there are people who believe it shouldn't be part of Graph? It's a standard operation, whether that's against a standard group or a mail-enabled security group shouldn't come into it.
To move this operation outside of Graph wouldn't make much sense, as you'd have almost all other operations being performed here and then for this operation you'd need to go over there. Also, what does that entail in terms of authentication; will we now need to authenticate against the new API and get a different token first or will our Graph token cover the new API?

Thanks for the feedback Darrel Miller! Personally, I don't care if it's part of the MS Graph API or just a ny API. Any 'ol HTTP API call to remove and add. personally, my code only deals with employee Terminations, so I just remove people from O365 groups.

The Graph API seems like it was a good idea, but then it kinda died; or at least issues like this make it seem like it died and got left behind, half-implemented.

But yeah, if there's ANOTHER way to add or remove people from an O365/Azure mail-enabled security group (or distribution list), that would be great so it doesn't have to be done manually!

AUTOMATE All the things! 🙂 Thanks!

Yes we are listening. I have been trying to make the case for this for longer than this thread has been around.  The conversation is happening once again, right now, but there remain some people that are not convinced that bringing the API functionality to Microsoft Graph is the right approach.

It would be useful feedback to understand whether you care if the API in on Microsoft Graph, and so would be part of the Graph docs and Graph SDKs, bound by Graph breaking change policies.  Or, if you don't care as long as there is an HTTP API you can call.

This thread has been open for one month shy of two years and not even a peep from Microsoft.

Are you even listening Microsoft?  Is this on a roadmap somewhere?