CLI Import Task keeps failing when including connection references in configuration file - Azure DevOps CI/CD

[PowerPlatform-P]

Hello community,

I have a Azure DevOps CI/CD pipeline built using YML. Whenever I try to include the configuration file that contains the connection references, my pipeline keep breaking.

I have checked many times that those connection references are the correct ones that I have shared with service principal and I cannot really know what else to check anymore. I deleted the entire solution and try to import as a brand new solution but it still keeps failing as long as I include the connection references in the configuration file. 

Any suggestions on what else I can check? Thank you in advance for your help!

[PowerPlatform-P]

I found the reason now. I had used the wrong service principal in DevOps lol.... so it is still service principal related. 

[v-xiaochen-msft]

Hi @PowerPlatform-P ,

Glad to see you solved the issue.

Please consider marking yourself reply as the solution.

Best Regards,

Wearsky

[PowerPlatform-P]

I realized I got the wrong SPN. However, upon changing the SPN, I still faced the same issue that as long as I included the Connection References in the configuration file, the import task failed... and I don't know where else to check when I am sure all connection references have been shared with the Service Principal. Any ideas for troubleshootings?

[PowerPlatform-P · Accepted solution]

I am able to find the root cause of it now. One of my connection references is a SharePoint connection reference. However, the SharePoint site and list that are used in the app and flows, the owner of those connection references (which the owner is a Service Account), do not have access to.

I did a manual import, and got an "warning error", which I would not be able to see through the auto-deployment. The warning was "Warning" You do not have access to the site value for this selected connection. However, this does not block other users in the target environment from using this site value if they have access." I just need to click the okay button to proceed with the manual import. Once that was all done, I ran an auto-deployment with configuration on and included all the connection references, then it was working. 

Lesson learn here, please ensure the Service Account also have access to the SharePoint sites or lists unless you do a manual deployment first to bypass the warning.