Create a personal pipeline using the platform host

Pipelines are available to all who navigate to the pipelines page for the first time. Create personal pipelines from your development environments to other target environments that you have import access to. Apply the benefits of pipelines such as no downloads or uploads required, deployment scheduling, inline target environment solution validation, upfront connection reference and environment variable value validation, and Copilot-generated deployment notes with an easy setup process.

Prerequisites for personal pipelines using the platform host

• Three environments can be associated to a personal pipeline created from the Pipelines page: one current development environment and two target environments. More information: Add a stage to a single-stage pipeline you own.

  Note

  Default environments, Teams environments, and environments without a Microsoft Dataverse store can't be used as target environments for personal pipelines.

• All environments used in pipelines must have a Dataverse database.
• All target environments used in a pipeline must be enabled as Managed Environments.

Current limitations with personal pipelines using the platform host

• Personal pipelines can't be extended.
• Only three environments, a source, and two subsequent targets, can be configured.
• Personal pipelines can't be shared with other users.

Setting up the platform host for the first time

If you're the first user in your tenant to navigate to the Pipelines page in an environment not already associated with a custom pipelines host, the platform host is provisioned for everyone in the tenant to use.

Create a pipeline in Power Apps

First, ensure that you are in the development environment where you want your pipeline to start.

Select Create pipeline on the command bar or from the Pipeline dropdown list.

A panel opens, where you enter:

• Pipeline name: A name for the pipeline.
• Description: An optional description to describe what the pipeline is used for.
• Target environment: The environment that solutions in the current development environment are deployed to.

Once you select Save, the current (source) environment and the selected target environment are associated with the platform host, and environment records for each are created in the platform host. Then, the newly created pipeline is autoselected and you're ready to run the pipeline.

Add a stage to a single-stage pipeline you own

Select Add stage on the command bar to append a stage to the current single-stage pipeline. As part of this step, you're prompted for a stage name, description, and a final target environment for your pipeline.

Delete a pipeline you own from Power Apps

Select Delete on the command bar to delete the currently selected pipeline in the dropdown list. A confirmation message appears regarding your intent and knowledge of the consequence.

This action doesn't remove the run history for the pipeline nor does it delete the associated environment records from the host.

Use your personal pipeline with other development environments

If you have the same pipeline process for an additional development environment, such as your user acceptance testing (UAT) and production environments are the same for another source environment, you can reuse the pipeline that you already created.

Choose the created pipeline from the dropdown menu. When you select Next in the first step of the deployment configuration process, the current environment is linked to the pipeline (and the host) as a development environment.

Accessing the Deployment Pipeline Configuration app from Power Apps

From the Pipelines page within any solution, the Manage pipelines button in the command bar navigates to the configuration app of the pipelines host that is associated with the current environment:

• If the current environment is associated with a custom pipelines host, the button links to the Deployment Pipeline Configuration app within the dedicated Host environment.
• If the current environment is associated with the platform host, the button links to an embedded Deployment Pipeline Configuration app within Power Apps.

The Deployment Pipeline Configuration app can be accessed by anyone with the Deployment Pipeline Administrator role if using a custom host, and any tenant administrator for the app associated with the Platform host.

Frequently asked questions

When I navigate to "Manage pipelines", why am I receiving a privilege error when I'm a system administrator or why is it loading the app indefinitely?

Sometimes, when another user authentication cookie is present in your browser, the embedded model-driven app experience can display an error message related to privileges to access the app. In this case, clear your web browser's cookies or open the app in an InPrivate window in your web browser to ensure that your authorization token is the only one considered.

Next steps

• Run pipelines in Power Platform