Best practices for Power Automate with service account

Matthew Carter 

We used one generic account called mailto:email address removed for privacy reasons for all "Power" related stuff, which initially only included PowerApps and PowerAutomate.

We later discovered that some flows with a conditional trigger do not run IF said item was updated using a PowerApp. The problem was that the owner (mailto:email address removed for privacy reasons) of the PowerApp was also the owner of the flow, and so when a staff member updated an item using the PowerApp, the flow would cease to run based on this conditional trigger, which is required (unlike how it worked in the past with SharePoint designer, where a flow can update fields and not trigger the flow again) to prevent all kind of chaos and infinite loops.

I'm sure there is a better way to scratch this cat, but for the time being, we've created another generic account called mailto:email address removed for privacy reasons. and have transferred ownership of all PowerApps to this account in order to avoid the scenario above.