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...
Account Management
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.