[CoE Starter Kit - BUG] COE keeps asking us to republish apps

[Service-WebDevPowerP]

Does this bug already exist in our backlog?

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

Describe the issue

We recevie emails saying "Keep your app updated to stay compliant.
You own an app that's currently shared or used broadly but which has not been published recently"

I have republished each app every week for at least a month now and we still receive the email each week saying it needs to be republished. Is this expected behaviour? I thought this was only meant to trigger every 90 days?

we have some flows that have turned off since August update, could that be the cause?

I am not sure which solution contains this flow so I am not sure which version it is, but we currently have Septembers update installed

Expected Behavior

No response

What solution are you experiencing the issue with?

Audit Log

What solution version are you using?

September

What app or flow are you having the issue with?

Unknown

What method are you using to get inventory and telemetry?

None

Steps To Reproduce

No response

Anything else?

No response

[Jenefer-Monroe]

Your inventory generally will not run correctly without these 3 flows turned on. As you can see the driver flow is off so you have not gathered inventory since August 20th.

[Jenefer-Monroe]

Please do boot the setup wizard and walk through initial setup it will ensure the first two are turned on and running.
Then manually turn on Admin | Audit Logs | Update Data (V2)

Use the setup wizard

Its highly recommended that you use the Setup Wizard to walk you through setup and upgrades. It will ensure all the new flows are turned on in the correct order, trigger things like population of the bookmarks screen and do other cleanup steps needed.
You should do this both for upgrades and clean installs.
To use it, first perform the import of the solution install or upgrade manually, then boot the app and walk through the screens.

[Jenefer-Monroe]

For the publish warning, this is in the following flow: Admin | Compliance detail request v3
And is driven by the environment variable below. Its possible that the inventory not running is what happened, because if the app has never been published it will also go through the process.

[Service-WebDevPowerP]

Hi Jenefer

Thank you for your reply. I've always done the upgrades through the Set up and Upgrade wizard. Any idea why it didn't turn that flow on? Our Test environement has done the same thing. The flow Admin | Sync Template v4 (Driver) is currently not turning on, it gives an error of:

Admin data policy 'CoE' restricts the use of /providers/Microsoft.PowerApps/apis/shared_commondataserviceforapps with /providers/Microsoft.PowerApps/apis/shared_powerplatformadminv2.

The Admin | Audit Logs | Update Data (V2) has turned on fine though

[Jenefer-Monroe]

Yes it looks like you may not have updated the DLP policy with the new connector

Please add the DLP Policy - Power Platform Admin V2 connector to your DLP. Then once it has had time to sync up (which can take a while unfortunately) turn on the following flows in the order shown:

• HELPER - Driver Escalation Check
• Admin | Sync Template v4 (Driver)

[Service-WebDevPowerP]

Thank you Jenefer, I will let you know how that goes

[Service-WebDevPowerP]

HELPER - Driver Escalation Check doesnt appear to be in any of the solutions. Where is it?

[Jenefer-Monroe]

Are you a sovereign cloud user?
Can you please share a screenshot like this so we can see what solutions you have installed in this environment? Be sure to show all records (all rows) and expand the indicated columns so that we can see full names

[Service-WebDevPowerP]

Hope this helps, no not a sovereign cloud user

[Jenefer-Monroe]

Ok that flow is in the core solution then. It appears there may be something wrong going on.
Please go to the solution itself, outside of the command center, run the following flow:

Then see if you can find the escalation helper in the list an turn it on

[Service-WebDevPowerP]

Thank you I have now found them both and turned them on. Anything else I need to do?

[Jenefer-Monroe]

You will need to make sure all the flows in inventory are turned on.

Please go to the Admin Command Center > CoE Flows > Inventory. Validate that all flows are turned on and that there are no unmanaged layers as shown here.

[Service-WebDevPowerP]

We had 2 flows that were off they are now on. Strangely the Admin command center was out of sync with the state of the flows. Saying some were off when they were on, it has since refreshed though. Anything else I need to do?

[Jenefer-Monroe]

I presume that since inventory has been off for about 5 weeks, we need to do something more to get you back up to date.
I suggest updating the InventoryFilter_DaysToLookBack environment variable to go backwards further, 45 days should do it (see notes below)
Then when that is complete see if your publish date is correct.

Change how far inventory does lookback

In order to avoid using unnecessary API calls the kit only looks back 7 days (by default) to look for updated flows.
In the event something happened and your inventory was off for a longer period of time than that, we do allow you do change this and look back further. Here is how to do that.

1. Update the env variable to go back to when your inventory stopped working: InventoryFilter_DaysToLookBack
   
2. Restart all the flows that use this env variable to ensure the flows do not cache the old value
   
   
3. Kick off your driver flow: Admin | Sync Template v4 (Driver) and wait for it to complete
4. Reset the environment variable back to 7 to avoid needlessly consuming these API calls
5. Restart all those flows again.

[Jenefer-Monroe]

closing out as no further action for starter kit team