You’re offline. This is a read only version of the page.
445
Almost every day now, something is breaking in Power Automate that has previously been working for months or years. I am exhausted and frustrated with so much breaking at once. Our productivity and my workload are increasing exponentially at this point.
At the moment, I'm getting an error for the O365 action 'remove member from group'.
Cannot Update a mail-enabled security groups and or distribution list.
There is nothing indicating this connection is broken but it evidently is. This action was working as recently as six days ago. I'm also getting errors in other workflows in regard to expired tokens.
What do I need to do to build a workflow that will never break?
I mean, am I mistaken that we should be able to use Power Automate as a toolset to run a business? It seems more and more evident that we are putting a lot of eggs into a basket that is built to fail.
You'd probably have use MS Graph..
Or the "old school" way was to use PowerShell, store that as a Webbook( I think that was it as it was a couple years ago I did that) in azure, then pass value in Power Automate to the PowerShell to update the DL.
It appears this incident is in regard to a Distribution List.
The Object ID for this Distribution List is different than the Group ID obtained from O365 Group 'Get groups of a user (V2)'. Is it the case that this action is not able to remove a user from a Distribution List?
If connections are fine, then I'd say something else changed..
Based on this error- Cannot Update a mail-enabled security groups and or distribution list.
Have you checked to make sure the account that is connecting to the group/distribution list still has access to it?
You could also try adding a new action and or create a test flow to see if that works.
This is exactly what I'm doing as well. I have checked the Connections page and there are no issues to resolve.
I am the "Security Team". Where would I find the Token Refresh setting?
Whenever we build a Business Impactful Power Platform solution, we get a Service account created for that department. This is a Full account with a Mailbox and a M365 license.
We do that so that if the person who created the flow leaves the company, the flow continues to function as the service account never leaves.
You might want to go to Power Automate and click on "Connections" on the left side and review the status of your connections and click on "Fix Connection" for each broken connection
If it continues to happen then you will want to check with your security team to see if Token refresh is set for the account for that connection.
@ShaneMeisnerTH Could you elaborate on Service Accounts? Do you mean Service Principle? I'm currently using a dedicated "workflow" account for Power Automate. I don't have any expiring passwords nor have I changed anything. To my knowledge, Flows are breaking for no reason. Sometimes I can just open a flow and save it and it starts working again. In other instances, I'm still struggling to determine how to resolve a break that has no error.
We use Service Accounts to run our Business Impactful Flows, and worked with our Security team to not refresh tokens on these accounts when Passwords are changed.
Doing this allows our flows to continue to run when the Password changes, without breaking the connections.
#1
Michael E. Gernaey
566
Super User 2025 Season 1
#2
David_MA
516
Super User 2025 Season 1
#3
stampcoin
492
Share
Report
All responses (
Answers (
