Power Platform ADO Tools Connections with Service Principal or HTTP

[byrnep]

Will the Service Principal assigned to a Dataverse connection carry over when using the ADO pipelines, or will it need to be manually configured afterwards in the Target environment?

I believe that only connections that can be configured with the pre-population file will be mapped on the Target environment.

[ANB]

Hi @byrnep ,

The Dataverse connection need to be created first in target environment. The Deployment setting file in ADO CI/CD pipeline will have the information of connection reference which will mapped properly when the deployment is completed.

However, before running ADO CI/CD pipeline you need to shared/assign Dataverse connection to Service Principal (Application user) manually and then run the ADO CI/CD pipeline to do the deployment.

If you do not share/assign Dataverse connection to Service Principal (Application user), then ADO CI/CD pipeline will fail.

I hope I understand your issue and answered it accordingly. If not then please elaborate little more on this.

------------------------------------------------------------------------------------------------------------------------------

I hope this helps.

Please click Accept as solution if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider giving it Thumbs up.

Thanks,

ANB

[byrnep]

Thank you. I was referring specifically to the connector (e.g. Dataverse) in the flow being configured to use an SP, and when moved via pipeline from dev to test, would the connector SP information still be configured in test after the pipeline imports to test? Or would I have to go into Test and reconfigure the SP for the Dataverse connection after the pipeline import?

[ANB]

Hi @byrnep , Please correct me If I am wrong. Are you referring to Dataverse action in Flow which can be configure using Service Principle as below?

If yes, then you must be knowing that to configure, you require Client ID and Client Secret.

As per my knowledge the Client Secret cannot be exported through CI/CD pipeline because for oblivious reason and I have tried this for one of our custom connector and as an alternative I have to use environment variable of secret type and then move to target environment. 

But I am sure that you cannot use environment variable while configuring the Dataverse action in flow through SP. And eventually once you deploy your components to target environment, your flow will fail and you have to re-configure the Dataverse action in flow through SP, if you have deployed your components to test environment as unmanaged solution. If you have deployed your components to test environment as managed solution, then it is going to be nightmare! 

So, to answer your question, you have to reconfigure all flows in test environment with SP if you have deployed your components to test environment as unmanaged solution.

Please check this https://powerusers.microsoft.com/t5/Power-Automate-Community-Blog/Using-Service-Principal-in-Power-A...

I would suggest you to create a ticket with MS to get more clarity on this. Also try posting your query on Power Automate forum: https://powerusers.microsoft.com/t5/Microsoft-Power-Automate/ct-p/MPACommunity

------------------------------------------------------------------------------------------------------------------------------

I hope this helps.

Please click Accept as solution if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider giving it Thumbs up.

Thanks,

ANB

[ANB]

Hi @byrnep , I was wondering if my response answer your query.

Thanks,

ANB