Unanswered

Preventing flows from orphaning

(0) Share

Report

Posted on by Krash

Hello all.

I'm building a flow for an organisation, but I'm doing this as a temporary contractor and will leave eventually. My question is how to ensure that the flows I create will be functional even after I leave the organisation and have my account disabled? I could in theory move the ownership to another employee, but that just moves the risk to another individual. Ideally, the ownership would be tied to the Teams/SharePoint site that it is dependant on. Is that possible, or can someone provide a solution / suggestion to secure its robustness?

Thanks in advance!

Categories:

General topics

I have the same question (0)

All responses (2)

Answers (1)

Verified answer

ScottShearer 25,270 Most Valuable Professional on at

Like (1)

Report

@Krash

Upon your departure, a Power Platform admin can remove you and add someone else as the owner of the Flow.

By default, your credentials will be user for all connections within a Flow. You may want to have a service account created and use the service accounts credentials for all connections. When you leave and your account is disabled, all of your Flows will fail to run even if a new owner is assigned because the credentials used for all actions are tied to your credentials unless you have specified otherwise in your Flow. The new owner can change the connection info but that may prove time consuming.

Was this reply helpful? Yes No
Krash 9 on at

Like (0)

Report

Thanks for the reply. Its not an ideal solution as a service account would take up a license slot, and be a security risk (as it would be a shared account), but I just have to accept the situation as it is 🙃

Was this reply helpful? Yes No