[CoE Starter Kit - BUG] admin_applastlaunchedon table has no new data since Feb 19, 2023

[idea01]

Does this bug already exist in our backlog?

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

Describe the issue

admin_applastlaunchedon table has no new data since Feb 19, 2023.

We have had many apps opened this year, so we expect to see a lot of data here. We see createdon, modifiedon, publishedon dates, just not the last launched on date.

We've verified the Auditing is on in the Compliance Center.

In the Audit Log table, we see the admin_operation for last lauched date up until Feb 19, 2023 and nothing after that.

We are testing the July version right now.

Any Ideas?

Expected Behavior

No response

What solution are you experiencing the issue with?

Core

What solution version are you using?

4.11

What app or flow are you having the issue with?

Audit Log

What method are you using to get inventory and telemetry?

Cloud flows

Steps To Reproduce

No response

Anything else?

No response

[Jenefer-Monroe]

Hello. Connections to custom connectors get broken on solution upgrade. Please see issue 1424 for how to resolve
If that does not resolve, then you likely ended up with a bad connection, perhaps due to the wrong identity provider being selected as in issue 4808

If that occurs please try the steps outlined in issue 4961

[Jenefer-Monroe]

It is for this and a few other reasons that we have actually deprecated the custom connector solution for audit logs and so we recommend you switch over to the new Http methodology by following this write up: How to convert audit logs from custom connector to http format

[idea01]

Hi Jenefer, We updated to use the HTTP method, and then we had several folks go and launch some apps in a couple different environments. waited 30 minutes and ran the Admin | Audit Logs | Sync Audit Logs (V2) and we are still not seeing any new data in the admin_applastlaunchedon table.

[Jenefer-Monroe]

Please go to the details page on this flow. Are the flows running and passing?

If so, open one of the runs and look for a filter event that has a "LaunchPowerApp" event

Find that iteration in the loop and see where it falls here.

[idea01]

Hi Jenefer, In the steps above, we were not getting "LaunchPowerApp" data in Filtered results. We did however, have a break through on this issue. My customer is on a GCC Tenant. We did make sure to have the environment variables set for the Audit Logs - Audience as described on https://learn.microsoft.com/en-us/power-platform/guidance/coe/setup-auditlog-http

However, upon examining the Admin | Audit Logs | Sync Audit Logs (V2) flow, there are two HTTP actions that have a hard coded URI pointing to "https://manage.office.com" In the GCC tenants, that should be "https://manage-gcc.office.com"

We added an unmanaged layer to this flow and changed the URI in those two HTTP actions and we started getting "LaunchPowerApp" data.

[Jenefer-Monroe]

Thank you for debugging, this was posted by another user and is local fixed for August, yeah!
#6075

[idea01]

Another oddity... We updated to the GCC paths and had one test succeed, on the following auto-runs of the flow it is failing, stating the Get_Azure_Secret failed because it cannot be null:

[CoEStarterKitBot]

@idea01 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.