Power Platform Community Forum Thread Details

Currently I am the only one in our organization that creates PowerApps (and flows). As a habit, I have been sharing ownership of the apps/flows with a service account as I have read that if I leave the company, the ability to retain these apps/flows is severed when my account is deleted. Is this what others do? Is this best practice? Are their other options that you are using that is a better solution?

Also, how do I plan for the future when others begin to create apps/flows and even Forms for that matter, in order to ensure when the author's account is severed that we are not in dire straits?

Finally, is there an audit tool that I can use to search if there are any other apps/flows/forms created by users that are not "shared" or retainable?

Categories:

Governance & administering

1) Using a service account when creating apps is a best practice. Simply sharing them with a service account as co-owner doesn't really accomplish much. Adding a Service account as co-owner doesn't change the connection account, it will still default to your account. And Power Platform admins can always take ownership of apps after you leave the company. So there really is no particular benefit to adding a service account as a co-owner. Using the Service account to create the app however will create the connections using the service account credentials. This is a better scenario.

2) A Power Platform Admin can see all the Apps in an environment, including who the owner is, by going to the Resources menu in the Environment in the Power Platform Admin center.