Inactive and orphaned objects

(0) Share

Report

Posted on by Paul T

In our scenario there are apps and flows that are orphaned AND inactive, so as the admin we're getting notifications from CoE saying "OWNER DOES NOT EXIST. APPROVAL SENT TO ADMIN".

Usually even as admin we don't have access to the object to view/edit it for investigation or even back it up.

I assume I've got two broad choices to silence the notifications (for now):

excuse the object from the inactivity process
take ownership to investigate and eventually:
- re-assign ownership to someone we think should own it, or
- republish the object
- back it up and allow it to be deleted (then wait for someone to scream)

#2 is troubling because there are dozens and dozens of objects. I'm not convinced I should take the time to research each individually.

How are you, dear community, handling things in this situation.

Categories:

Management

All responses (1)

Answers (1)

Verified answer

AlbertoCastro 1,184 Most Valuable Professional on at

Like (0)

Report

Re: Inactive and orphaned objects

Hi,
It depends on how clean you want your tenant to be 🙂
If you have a lot of inactives/orphaned, yes, it will take a big initial effort but you will have a good tenant and cleaned.
The inactives, backup and delete. It supposed that nobody were using them, the you will have a good defense excuse.
The orphaned: review the shared users and ask them what sould be the new owner.

If you are the power platform admin, you have to enforce your criteria about your governance plan. 💪
-------------------------------------------------------------------------
If I have answered your question, please mark your post as Solved.
If you like my response, please give it a Thumbs Up.
Regards
Alberto