setup-pipeline

Creates Power Platform Pipelines in Dataverse for automated Power Pages solution deployments.

808|167|Updated Jan 21, 2026
One-click install
npx skills add https://github.com/microsoft/power-platform-skills --skill setup-pipeline
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: setup-pipeline
Source: https://github.com/microsoft/power-platform-skills/tree/main/plugins/power-pages/skills/setup-pipeline
Command: npx skills add https://github.com/microsoft/power-platform-skills --skill setup-pipeline

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Setting up CI/CD for Power Pages projects normally requires manual configuration of Power Platform Pipelines through the admin UI. This Skill automates the entire pipeline provisioning process by creating pipeline, environment, and stage records directly in Dataverse via the PP Pipelines OData API, with no external CI/CD infrastructure required.

Core Features & Use Cases

  • Automated Pipeline Provisioning: Creates deployment environments, pipelines, and stages in the Pipelines host environment using the OData API, including source environment association and multi-stage setups (Dev to Staging to Production).
  • Preflight Validation: Verifies PAC CLI and Azure CLI authentication, Pipelines package installation, solution existence, pipeline name conflicts, and blocked attachment settings before any Dataverse writes occur.
  • Host Resolution and Error Recovery: Detects the correct Pipelines host environment through a multi-signal resolution flow and handles edge cases like environments already linked to another host via the force-link recovery path.
  • Use Case: A developer finishes a Power Pages code site and wants automated deployments to staging and production. Running this Skill detects the project context, confirms the configuration, and provisions a complete Power Platform Pipeline ready for deployments.

Quick Start

Ask the assistant to set up a Power Platform Pipeline for automated deployments of the current Power Pages project.

Frequently Asked Questions about setup-pipeline

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up CI/CD for Power Pages deployments?

Use Power Platform Pipelines, Microsoft's native CI/CD tool built into the Power Platform. This Skill automates the setup by creating the pipeline configuration directly in Dataverse through the PP Pipelines OData API, with no external infrastructure or YAML files needed.

What prerequisites are needed to create a Power Platform Pipeline?

You need a powerpages.config.json file, a .solution-manifest.json created by the setup-solution step, Azure CLI logged in, PAC CLI authenticated with an environment selected, and a Power Platform environment with the Pipelines package installed as the host.

Does this support GitHub Actions or Azure DevOps pipelines?

GitHub Actions and Azure DevOps Pipeline options appear in the platform selection menu but are shown as coming soon. The current implementation creates Power Platform Pipelines only, which require no external CI/CD infrastructure.

Why does pipeline setup fail with 'already associated with another pipelines host'?

This error means the target environment is stamped to a different Pipelines host. The Skill detects this pattern and offers the force-link-environment flow to take over the association, which is destructive to the previous host and requires explicit user consent.

Can one pipeline deploy multiple solutions?

Yes. When the solution manifest uses schema version 2 with a multi-solution layout, a single pipeline ships all solutions through per-solution stage runs. Single-solution manifests create one pipeline through the standard flow.