Gathered from customer feedback some improvements to consider for orphan process:
as part of compliance process, ask maker to specify a secondary owner (could be auto-suggested based on who is a co-owner)
true productivity apps (e.g. not shared with anyone, just the maker has access) should not be considered for orphan process, they don't need to remain active if the owner is left (could be a separate clean up process but not priority)
if the owner leaves, make the secondary owner the new owner both in product as well as in CoE kit - run this automatically and notify the new owner of their new responsibilities. they can use dev compliance center to re-assign ownership as well but let them know the reason they got ownership is because the previous owner picked them.
then, only apps with no secondary owner specified run into the orphan process that involves the manager/admin
could consider: if orphan > sent teams card to all co-owners to let one of them pick ownership, but runs the risk of no-one claiming it
What solution are you experiencing the issue with?
What is your question?
Gathered from customer feedback some improvements to consider for orphan process:
What solution are you experiencing the issue with?
Governance
What solution version are you using?
No response
What app or flow are you having the issue with?
No response