Power Platform Pipelines verses Pipelines in Azure DevOps

[westerdaled]

I am looking to recommend Power Platform Pipelines to a client, given it is easier for the makers to configure and run when compared to pipelines in Azure DevOps. Additonally, you can configure predeployment ( approvals) and postdepeployment actions via Power Automate, plus integration with Git via GitHub Actions.   All our tasks / src is managed in Azure DevOps.

Are there any compelling reasons to use Pipelines of Azure DevOps over Power Platform  Pipelines other than ditching the requirement for environments that participate the pipelines to be either Developer or Managed?

Can you Prepopulating environment variable values and connection Ids in Power Platform Pipelines?

From what I can see, the environment variable values and connections will need to set up manually when the pipeline deploys a solution in the target environment.  There is no provision for prepopulating connections ids and environment variable values in a  settings.json file as per pipelines in Azure DevOps .  So am I right in thinking, there is no way to automatically prepopulate connection ids and environment variable values in Power Platform Pipelines?

[AllanDeCastro]

Hello,

According to the documentation, It's not possible to populate it as we're doing using dedicated CI/CD through DevOps:
"If connection references or environment variables are present, you’re prompted to provide these (just as you would when manually importing solutions)."

The only thing I haven't tested is that if it's a one-shot action (or when you have a change), the next pass will go through without a hitch, without specifying anything.

Link: Run pipelines in Power Platform - Power Platform | Microsoft Learn