Do Connection References stay enabled when Owner is deleted from environment?

(0) Share

Report

Posted on by TimFe

Hi all,

I am currently in the process of takeing over a big project from the company that built the Soutions.

They used connection references for all the flows. While I can change the connection underlying the reference I can not seem to change the owner of the connection reference which is being used inside the flows. So I am wondering if the connection references stay operational after the owning users have been deleted or deatkivated from the environment or if the connection references need to be replaced in all 180 Flows.

Does anyone have experience with this matter?

Thank you very much

Tim

Categories:

Building flows

I have the same question (0)

All responses (3)

Answers (0)

Sort by

MarconettiMarco 3,812 Super User 2024 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Hello @TimFe ,
please refer to the following article:

https://community.dynamics.com/365/customerservice/b/ecellors-crm-blog/posts/orphan-flows-in-power-automate

If I have answered your question, please mark my post as Solved.
If you like my response, please give it a Thumbs Up.
BR,
Marco

Was this reply helpful? Yes No
TimFe 16 on at

Like (0)

Report
Copy link

Link copied!

Hello Marco,

thank you for your quick reply however this is not exactly what I am looking for.

I have just tried to replicate the situation in a Demo ENV. It seems that the Connection Reference itself is not depending on the user how owns it. That means that once the connection underlying it has been changed to a valid connection without a to be deleted user it will continue to work.

Was this reply helpful? Yes No
Shujaath_Khan 1,111 Super User 2024 Season 1 on at

Like (1)

Report
Copy link

Link copied!

Hi @TimFe
@MarconettiMarco has shared the point here.
in orphan flow the connection references also run in identity and use is no more active flows shall fail soon. so whoever has taken must change the connection to new connection to resume henceforth.
excerpts from blog
A flow turns into an orphaned flow when it doesn't have a valid owner anymore. It often happens when the creator or owner of the flow has left the organization and there's no co-owner. If the flow uses connections that require authentication, then it may start failing because the user identity isn't valid anymore.

reg. count you can check on using cmdlets
and more here : https://docs.microsoft.com/en-US/troubleshoot/power-platform/power-automate/manage-orphan-flow-when-owner-leaves-org

Thanks
Please click Accept as Solution on this reply if it helped to solve your issue, and thumbs-up if you feel this is useful or important in other ways as a boost.
https://www.youtube.com/channel/UCgQWIrxj5KrZ2nlx3CDYhEg/playlists

Was this reply helpful? Yes No