Domain 3 of 3 · Chapter 7 of 7

Implement and extend Microsoft Power Platform Pipelines

Unlock the complete study guide + 1,040 practice questions across 16 full exams.

Bundled into the existing Designing and Building Integrated AI Agent Solutions in Copilot Studio premium course — no separate purchase.

14-day money-back guarantee — no questions asked.

Included in this chapter:

  • Where the automated half of the release starts
  • The pipelines host, and the two ways to get one
  • Installing the application and declaring the environments
  • Linked development environments and ordered stages
  • Who may edit a pipeline and who may run one
  • Running a deployment from the development environment
  • One artifact, exported once and sealed in the host
  • Extending pipelines with gated steps
  • Delegated deployments and the identity that installs
  • What the host keeps, and the three ways back
  • Where pipelines stop

The three gated extensions

AxisPre-export Step RequiredIs Delegated DeploymentPre-deployment Step Required
Where the step is insertedWhen a deployment request is submitted, before the solution is exported from developmentAfter the request, as an approval the delegate must grant before the deployment proceedsAfter a deployment is approved, immediately before the deployment runs
What it is forCustom validation logic, such as automated agent tests; Microsoft says to enable it only for the first stageRunning the deployment as a service principal or the pipeline stage owner rather than the requesting makerA final custom step, such as a last manual sign-off, once approval already happened
Step started triggerOnDeploymentRequestedOnApprovalStartedOnPreDeploymentStarted
Step completed triggerNone published for this extensionOnDeploymentCompletedOnPreDeploymentCompleted
Unbound Dataverse actionUpdatePreExportStepStatusUpdateApprovalStatusUpdatePreDeploymentStepStatus
Identity that must call the actionAny identity with access to update the deployment stage run recordThe configured service principal or the pipeline stage owner, and no one elseAny identity with access to update the deployment stage run record

Decision tree

Which pipelines setup does the scenario need?Must anyone other than the makercontrol, approve or sharethis release?More than one developmentenvironment, or more thantwo target environments?Custom host requiredAn admin installs the appand shares by security rolePersonal pipelinein the platform hostcannot be extended or sharedWhat must the gate do?each option is one setting on the stageNo gate neededShared custom-hostpipeline, orderedstages onlyPre-export Step RequiredHold the export untila check passesOnDeploymentRequestedIs Delegated DeploymentDeploy as a serviceprincipal or stage ownerOnApprovalStartedPre-deployment StepRequiredAdd a final stepafter approvalnoyesnoyes
Cheat sheet

Cheat sheet

  • The pipelines host stores configuration and run history
  • Pipeline environments require Dataverse and managed targets
  • Install the Power Platform Pipelines application only in the host
  • A runnable pipeline links a development environment and at least one stage
  • Run pipelines from an unmanaged solution in development
  • Preflight validates dependencies and target settings
  • The same immutable artifact traverses stages in order

Unlock with Premium — includes all practice exams and the complete study guide.

References

  1. Overview of pipelines in Power Platform
  2. Configure pipelines using a custom host - Power Platform
  3. Create pipelines using the platform host - Power Platform
  4. Set up pipelines in Power Platform
  5. Create and manage custom solutions - Microsoft Copilot Studio
  6. Run pipelines in Power Platform
  7. Extend pipelines in Power Platform
  8. Automate testing and deployment of agents using pipelines in Power Platform - Microsoft Copilot Studio
  9. Deploy pipelines as a service principal or pipeline owner - Power Platform
  10. Redeploy past Microsoft Dataverse solution versions in Power Platform
  11. Import solutions from a pipelines host - Power Platform
  12. Microsoft Power Platform CLI pipeline command group