[ALM Accelerator - QUESTION] ShareConnectionWithServicePrincipal is not triggered about coe-starter-kit

[v-bjaiswal]

Hi @tobiasneunercs ,Yes you are right the "ShareConnectionWithServicePrincipal" flow triggered based on the checkbox value(checked only) and on "save and close" button of deployment setting screen.

but without checking the error it would be hard for us to help here. you need to share the failed run history of the "ShareConnectionWithServicePrincipal" power automate flow present on "Center of Excellence - ALM Accelerator" solution.

[tobiasneunercs]

Hi @v-bjaiswal ,

thanks for your reply. The issue is, that the flow is just not triggered at all. Or at least it is not triggered when I'm saving the deployment settings. I tested it with a colleague of mine, and if he saves the deployment settings, the connection is getting shared as expected.
Any ideas what might be the reason for this behavior?

[tobiasneunercs]

Hi @v-bjaiswal ,

we are still facing this problem, that the flow "ShareServiceConnectionWithPrincipal" is not getting triggered. There is no failed run, there are just no runs at all.

After clicking save & close nothing is happening:

In the end this of course leads to an error during deployment as the service principal does not have the permission to access the connection in the new environment. Any help on how to solve this, would be very much appreciated.

PS: Other flows seem to work and start as expected.

[RajeevPentyala]

@tobiasneunercs Can you try placing a Notify function in following formula and troubleshoot the issue?

[mikefactorial]

@v-bjaiswal it could be that the flow is not shared with your user since your colleague is seeing a different behavior or it could be a connection issue. Have you tried running the flow manually? You could just plug in some random parameters and see if you get an error other than the parameters being incorrect that might help understand the issue. If the issue is with flow sharing it's possible that you don't have the correct role assigned to your user. Make sure your user has the ALM Accelerator App role which should give you permissions to execute the flow. If none of those. @RajeevPentyala's suggestion would be a good way to further troubleshoot.

[tobiasneunercs]

Thanks for reminding me about debugging with unmanaged layer. We were able to find the issue this way. Somehow the permission on the service connection in DevOps was not working correctly. We were able to fix it, now everything is working as it should be.

Thank you very much for your support. Very much appreciated.