[CoE Starter Kit - Feature] Use co-owners for orphaned process

[manuelap-msft]

"Cleanup for orphaned resource" process checks if there is a co-owner? Today a customer was telling me that as the flows don't check for the "co-owner", it checks only if there is an owner or not, and that was the reason preventing them to use this process in CoE. What do you suggest?

AB#2156

[Papa-Cho]

+1 for this improvement 👍

[nvarsha23]

Hi,
When is a flow considered as Orphan? Is it when the primary maker/creator leaves the firm or when all the flow owners leave the firm? Can we know all the flow owner details (including co-owners) through CoE report?

[CoEStarterKitBot]

@manuelap-msft This has been fixed in the latest release. Please install the latest version of the toolkit following the instructions for installing updates. Note that if you do not remove the unmanaged layers as described there you will not receive updates from us.

[Jenefer-Monroe]

accidental close

[HenningStrand]

I take it that this was never fixed as it is reopened? I still see the behavior in 4.17 and have created my own temp flow and table for running through all the flows marked as orphaned in CoE to check if they have co-owners or are shared with SharePoint lists and storing this add'l info. I don't want to initiate cleanup processes for orphaned flows that are not really orphaned, so please reconsider what is the definition of what is an orphan.

Please update us on what the current definition is. Is it when the current maker's account is no longer active, or when the current main owner/derived owner account is no longer active? I can see flows with inactive owner and active co-owners that are marked as orphaned, but also flows with active current owner but where the original owner (now co-owner) is inactive. Not clear..