Execute the End‑to‑End lifecycle pipeline

Task 04: Execute the End‑to‑End lifecycle pipeline

Execute the full promotion flow from Dev to Test to Prod to validate the complete ALM lifecycle using your configured pipelines and controls.

01: Promote the Copilot agent through the Dev → Test → Prod pipeline to execute the full lifecycle flow.

Let’s validate whether the ZavaRetailsSolution solution is already present in the Zava Retail Store - UAT environment.

In the browser tab bar, go to the Power Apps - Solutions tab.
From the upper right side of the page, select the Zava Retail Store - Dev environment, then from the dropdown list, pick Zava Retail Store - UAT.
On the left side, select Solutions, select All to display all solutions, and notice ZavaRetailsSolution solution is not present.
Return to the browser tab with the deployment pipeline interface open Deployment Pipeline Active.
Select Deploy here to deploy ZavaRetailsSolution solution to Zava Retail Store - UAT environment.

Notice that you can run the pipeline now or later. Choosing Later allows you to schedule the deployment, while selecting Now executes it immediately.

Because we defined multiple stages in our pipeline, Power Platform automatically enforces the correct deployment flow. That’s why we’re seeing the Dev → UAT deployment rule selected here.
Leave the Deployment schedule set to Now, select Next.

Notice that Copilot automatically adds comments to the Deployment notes for you. How great is that, thanks to modern GenAI!
Select Deploy, and wait until the ZavaRetailsSolution solution is deployed to Zava Retail Store - UAT environment.
Return to the Power Apps - Solutions tab. Notice that the ZavaRetailsSolution solution is now present.
From the upper right side of the page, select the Zava Retail Store - UAT environment, then from the dropdown list, pick Zava Retail Store - PRD.
Return to the browser tab with the deployment pipeline **Power Apps Pipelines**, and repeat the same steps.
From the UAT → PRD Deployment Rules, select Deploy here.
Leave the Deployment schedule set to Now, select Next and then Deploy.

===

02: Verify each stage completes successfully by checking deployment status, solution version updates, and agent behavior in every environment.

Review deployment pipeline execution logs

From the top action menu, select View deployments to access the deployment history and review the details of each pipeline execution.
Scroll down to the History card; notice our deployment executions with a status of succeeded.
Select the most recent one and explore the execution log details.

Access the Deployment Pipelines Dashboard: View a centralized overview of pipeline activity to monitor deployment progress, validate execution status, and maintain lifecycle visibility across all stages.

In the browser tab bar, go to the Power Apps - Solutions tab.
From the upper right side of the page, select the Zava Retail Store - PRD environment, then from the dropdown list, pick Zava Retail Store - Dev.
From the left side menu, select Apps, then select Deployment Pipeline Configuration.

Notice here you can find how many times each pipeline has run.
Select the ellipses (…) next to Dev → UAT → PRD.

Notice that you can export, share, delete, modify, or even deactivate the pipeline, along with several additional options.
In the left side menu, under Pipeline Setup, select Environments to access all the environments involved in this deployment pipeline.
In the left side menu, under Deployments, select Solution artifacts to view the active deployment artifacts, including the solution version and the timestamp for when it was generated.
Select ZavaRetailsSolution to view its deployment artifact details, including the version, generated files, owner, and deployment metadata.

You can reassign the owner, rename the artifact, and also download or delete the managed and unmanaged artifact files from this page.
From the command bar, select the Related tab and choose Deployment Stage Runs to review all executions associated with this artifact and verify the success of each stage in the pipeline.

From the left side menu, select Advanced Settings, and notice that you can configure cross-geo deployments, define a custom pipelines host, or enable importing from the pipelines host.

Option	Purpose	When to Use It	Data Residency Consideration
Deployment Pipeline Administrator	Configure pipelines, manage stages, and enforce ALM governance.	Assign to central admins who manage Dev → Test → Prod promotion flows.	Must operate in the same geographic region as the pipelines host unless cross-geo deployment is enabled.
Deployment Pipeline User	Run deployments and promote solutions through the pipeline.	Assign to makers or developers responsible for executing deployments.	Deployments are restricted to the host’s region unless cross-geo deployment is turned on.
Maker / Environment Contributor	Build and update solutions in the development environment.	Assign to solution builders who do not need pipeline configuration rights.	Makers must work in environments located in the same geo as the host to avoid region-based filtering.
System Administrator (Environment)	Full administrative control over a specific environment.	Assign when full access to Dev, UAT, or Prod is required.	Ensure the environment’s region aligns with your organization’s data residency or sovereignty requirements.

Congratulations!

You have completed this exercise and the workshop!