[CoE Starter Kit - BUG] Power Platform Admin View - Orphaned Solutions not being flagged

[RandomDepartmentofThings]

Does this bug already exist in our backlog?

• I have checked and confirm this is a new bug.

Describe the issue

When checking Solutions in the Power platform admin view and opening the relevant Solution in Dynamics 365. The 'Orphaned' property always shows as 'No'

In my example, the Solutions were automatically created via SharePoint Lists using the (Work Tracker Template).
During this process, a Flow is created, which in turn creates the Solution in the Default Environment.

When the List is deleted in SharePoint, there doesn't seem to be any automated cleanup of the Flow / Solution.
The Flow eventually fails as it can no longer find the list. After the List was deleted, I waited 24 hours. And the Solution still showed Orphaned as 'No'

Manual deletion of the Flow and waiting another 24 hours, also had the Solution still showing 'No' for Orphaned.

There are other external Microsoft triggers that create Dynamics Teams, Apps, Flows and Solutions, such as Apps in the Teams client so the above origin point is just an example.

I will also log this as a job to Microsoft Support if the issue is with Dynamics itself, however logging here for clarification on what changes the Orphaned Status on a Solution

Thank you

Expected Behavior

Solution should show as Orphaned when a Flow / List is manually deleted
Preferably a deleted SharePoint list (or whatever originating Microsoft source) should perform clean-up actions to any underlying Power Platform items it was the source of creation for.

What solution are you experiencing the issue with?

Core

What solution version are you using?

4.50.6

What app or flow are you having the issue with?

Power Platform Admin View

What method are you using to get inventory and telemetry?

Cloud flows

Steps To Reproduce

1. Create a New List on a SharePoint site
2. Select the Work Tracker template and complete the wizard
3. Solution is created in the default Environment
4. Delete the List in SharePoint and the Flow in Power Automate
5. Open Power Platform Admin View and go to Solutions

6. Open the solution and note the Orphaned status shows as 'No'

Anything else?

As mentioned, this may not be COE specific, just covering all my bases to determine where the disconnect occurs.

[mohamrizwa]

Hi @RandomDepartmentofThings,
Apologies for delayed response.
"Orphaned" classification only applies to makers / owners, not Solutions
Microsoft’s "orphaned" cleanup logic (CoE governance flows) focuses on:

• orphaned apps
• orphaned flows
• orphaned custom connectors
• orphaned PVA bots
• Solutions are not part of the orphaned-object detection pipeline.
• Solutions don’t automatically evaluate their child components for "orphaned state".
• The CoE doesn’t maintain the Solution orphaned flag—it only tracks orphaned apps/flows/power pages.