[CoE Starter Kit - BUG] Flows, apps and makers is set to orphaned

[larhem]

Does this bug already exist in our backlog?

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

Describe the issue

A low of flows and canvas apps has been marked as orphaned, probably because the maker is set to orphaned.
However the maker is not orphaned but the maker is a app registration used in Azure DevOps Pipelines - hence this user is set as maker when imported using pipelines. So those "makers" has been for some reason set to orphaned.

Expected Behavior

Flows and canvas apps not to be set as orphaned.

What solution are you experiencing the issue with?

Core

What solution version are you using?

4.50.7

What app or flow are you having the issue with?

not sure

What method are you using to get inventory and telemetry?

Cloud flows

Steps To Reproduce

Use the inbuilt views for "Orphaned flows" and "Orphaned canvas apps" in the Power Platform Admin View app.

Anything else?

No response

[harini-2-y]

Hi @larhem ,
Apologies for the delayed response, and thank you for the detailed information.

We have investigated this issue and confirmed that the orphaned status for flows and canvas apps created through Azure DevOps pipelines is caused by the current lookup logic in the CoE Core Components.
The flows are using the service principal’s Object ID (Id) to query Microsoft Graph, but for pipeline‑based makers this value does not return a match. As a result, these makers are incorrectly classified as orphaned.
We have identified the fix — the lookup needs to use the service principal’s App ID (appId) instead of the Object ID. This update is currently being worked on and will be included in an upcoming CoE Core Components release once the fix is finalized.