[CoE Starter Kit - BUG] Data not updating after host name change

[Dom-Hen]

Does this bug already exist in our backlog?

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

Describe the issue

CoE was configured by a colleague that has left. After picking this up I noticed that there are no cloud flows (apps and others as well) created recently (by any user in any environment). Chasing the issue found that some CoE flows are failing with the error finding the host (name was changed after the CoE was deployed). The connection references in solution look fine (at least it seems it works some times) but have not tried creating new ones due to the issue with unmanaged layers on the solution. I have turned off and on the flow as the guide says but still no joy.

Expected Behavior

Created a flow on a monitored environment but is not coming/showing in the CoE.

What solution are you experiencing the issue with?

Core

What solution version are you using?

4.29

What app or flow are you having the issue with?

Admin | Sync Template v4 (Flows)

What method are you using to get inventory and telemetry?

Cloud flows

Steps To Reproduce

No response

Anything else?

No response

AB#3816

[Jenefer-Monroe]

Unmanaged layers will make it difficult to debug as it means you are not in the same state as we shipped with. But we can give it a try.

First of all, you'll likely want to upgrade soon. There was a product change that caused us to have to upgrade the creator kit version and the apps to use it. So you'll want to upgrade to at least Creator Kit Core 1.0.20240529.1 and to at least the June release of Core (4.32.2) (I'll post more below)

And please be sure that each time you upgrade you boot the setup wizard as it will make sure that all new flows and env vars are filled. (I'll post more below)

Upgrade will also reset all the flows in the kit (unless there are unmanaged layers). And typically things like cached host names are cleared from flows with upgrade.

Lastly, you'll also want to note that issues connecting with other environments may be due to a product change around the way the product treats escalated roles (PPAdmin Role). There is a workaround thats needed. (I'll post more below)

So in short, my suggestion is:

1. Try to understand the unmanaged layers created so that they can be removed or re-applied
2. Upgrade Creator Kit Core
3. Upgrade Core (and gov/nurture if you use them)
4. Run the setup wizard
5. Implement the workaround for the escalated roles change (see below)
6. See what state you are in

[Jenefer-Monroe]

New PIM Feature and the Kit

Hello likely you have been impacted by new product behavior that shipped recently around the way the product treats privileged roles (ex Power Platform Admin role, Global Admin role)

While there is a workaround we can put into the kit to fix this directly, we cannot ship it with the kit until the workaround is available in all regions. Hopefully for the July release.

The product change

Here is information about the product feature: Manage admin roles with Microsoft Entra Privileged Identity Management

How to check if this is the case

1. Validate the user running the flow has direct and permanent assignment to the Power Platform Admin role.
2. Take one of the target environments in your repro, one of the environments which is failing, and make sure the user running the flow has System Admin security role in that target environment.

How to address and More information

Please see https://github.com/microsoft/coe-starter-kit/issues/8119 for a write up on this change. Included also is a workaround you can do until we can have it natively in the kit.

[Jenefer-Monroe]

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]

Buttons and Panels Broken - AKA Creator kit broken by product change

All dialogs and panels were broken in the kit due to a product change that broke the creator kit components that we use. This has been resolved with the latest version of the creator kit: https://aka.ms/creatorkitdownload

• Creator Kit Core 1.0.20240529.1

Then this new version of creator kit has been adopted and used to fix in the June 2024 release of the kit: https://aka.ms/coestarterkitdownload

You will need to install the new creator kit and then at least June release of the kit which is the versions below to see this fix across the kit.

• Core 4.32.2
• Gov 3.24
• Nurture 3.18

[Dom-Hen]

Hello Jenefer! Thank you for the quick reply. I will try your approach as I thought about a fresh start for it but if the upgrade works, it will be better!

[Jenefer-Monroe]

We are here to help so please do let me know how I can assist in your ramp up!

[Dom-Hen]

Hi Jenefer! quick question: i did push the new solution in and all went well but when going through the wizard, on step "Run inventory flows" it complained that various flows are off. And they cannot be turned "on" due to the connection reference being invalid. I assumed the upgrade would refresh these connection? in order to "move on" I could reconnect each individually but it would create a solution layer on each of the flows that were not able to turn on.

For reference, before the upgrade all any/all solutions layers existing on the flows was removed.

[Jenefer-Monroe]

Connections are usually fixed on upgrade but you may have hit some issue. Here are the three main things people have to do when connections are broken. Can you please see if you can repair them?

Broken Connections

Please log in as the user who’s identity installs and runs the kit and do the following:

Fix connections.

Browse to the connections in the envt. If there are any broken connections please repair them

Fix HTTP with Microsoft Entra ID (preauthorized)

Make sure all the HTTP with Microsoft Entra ID (preauthorized) connections are pointing to your graph URL

Fix Connection References

Lastly go to the Default Solution > Connection References Make sure they are all pointed to the correct identity which is intended to run the flows by doing the below for all connection references.

[Dom-Hen]

All seems to be back and connected, although I had some issues with the "admin_CoECoreTeams" as it was not connected at all and i was not sure of the details. Will try the same on our production environment

[Jenefer-Monroe]

closing out as no further action for starter kit team