Forum Discussion

boehamian's avatar
boehamian
Copper Contributor
Jul 04, 2026

Power Automate

Good afternoon all, 

I am working with a non for-profit organization. I am slowly trying to implement processes to manage 365 for them as most of them are not tech savy. 

I have been playing around with power automate (not too familiar with it myself) in order to create a user and add it to certain teams' groups and mail distribution groups. 

 

So far I have managed to get it to create the account and add the user to the teams group. However, in doing my research I have found Microsoft has removed the functionality to add users to a mail distribution group. 

Is there a way around this that I can implement? 

I came across this article but am not sure from here https://damobird365.com/add-members-to-a-distribution-list/

 

Thanks all for your help. 

Account Management

3 Replies

  • Allen's avatar
    Allen
    Icon for Community Manager rankCommunity Manager
    Jul 16, 2026

    Thank you for your post and thank you Jamony​  for your reply.

    please be aware that the Microsoft Tech Community is not an official Support forum for Microsoft and we do not have any Power Automate focused community on MTC. You can always post any follow up questions in the Power Automate Community forum here: Microsoft Power Platform Community Forum Thread

     

    Hope this helps

  • Jamony's avatar
    Jamony
    MCT
    Jul 08, 2026

    Hi, you are on the right track, but distribution groups are where this gets awkward.

     

    Power Automate has good coverage for some Microsoft 365 group and Teams tasks, but classic Exchange distribution group membership is still usually managed through Exchange Online PowerShell. The clean workaround is to have the flow call something controlled, like an Azure Automation runbook or Logic App, that runs `Add-DistributionGroupMember` with the right permissions.

     

    For a non-profit, I would keep the design simple: Power Automate collects the request and creates the user, then a secured automation step handles Exchange distribution group membership. Use a dedicated service account or managed identity where supported, keep permissions narrow, and log every change. If you can replace distribution lists with Microsoft 365 groups in some areas, those are usually easier to automate long term.

    • boehamian's avatar
      boehamian
      Copper Contributor
      Jul 11, 2026

      thanks mate for the reply, much appreciated. I have seen this as a solution in a few places to use a run book. Does using the azure automation runbook or logic app tjat runs the add-distributiongroupmember with the right permission require any specific license? Would you happen to have a link or a guide on how to use this command? Sorry a bit fresh to power automate.