[CoE Starter Kit - BUG] Error in CLEANUP HELPER - Power Apps User Shared With - Step "List Group Members" when App shared with a group that is deleted

[robertobudelo-armacell]

Does this bug already exist in our backlog?

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

Describe the issue

The flow fails when an App has been shared with Tenant "Everyone in Organisation" as the flow searches for the corresponding Group which doesn´t exist in this case.

Expected Behavior

No response

What solution are you experiencing the issue with?

Core

What solution version are you using?

4.8

What app or flow are you having the issue with?

CLEANUP HELPER - Power Apps User Shared With

What method are you using to get inventory and telemetry?

Cloud flows

Steps To Reproduce

Recurrent floe

Anything else?

No response

[Jenefer-Monroe]

Can you please share a screenshot of where you are seeing this behavior?

[Jenefer-Monroe]

In 4.11 what I see is this, it does not go down that path. Please do let me know what you see.

[robertobudelo-armacell]

You're right. I'm experiencing a bizarre behaviour. Could it be that App assignments are not deleted when a group is deleted?

When I look at Shared With of the App I see only three entries:

Get App Role Assignment however returns 4 entries with the yellow marked group id not available in my tenant:

Whilst the model-driven app specifies it somehow as tenant:

And the flow fails due to:

code
:
"Request_ResourceNotFound"
message
:
"Resource 'XXXXXXXX-XXXX-XXXX-XXXX-a3d5ac9617d6' does not exist or one of its queried reference-property objects are not present."

[Jenefer-Monroe]

Looks like there are two issues at play

Shared with tenant

It looks like the app is shared with the tenant as shown here:

The fact that its showing twice, I think they changed something in the return that made the "Type" change. I think once we get the flow to pass for this app it will clean up the old one and only show tenant once. So lets see if that happens.

[Jenefer-Monroe]

The other issue:

Product returning deleted group in connector

It does appear there is a delay in the recognition of the group being deleted across the services. I was able to repro.

I added a catch so that the flow will no longer fail, but did not add work to try and figure out if the services are mismatch.

If the connector continues to return the deleted object you will need to raise to the product team via support, it will just mean they have some caching bug to address.

Thanks for posting!

[Jenefer-Monroe]

This failure is now local fixed for August.

[CoEStarterKitBot]

@robertobudelo-armacell 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.