Summary

Completed

You now have a repeatable way to release an agent that keeps changing, from the development environment where you make each change to the production environment where people use the agent. Every update, from a new tool to a bug fix, moves through test as one managed package, so production receives the same version that testers validated.

What you learned

In this module, you learned how to:

• Match an environment type, managed status, and security group to each lifecycle stage, and plan a separate pipeline host.
• Build a custom solution that carries an agent and its required objects, and deploy it as managed outside development.
• Store environment-specific settings in environment variables of the right data type and in connection references, and supply values at deployment.
• Promote one managed artifact through pipeline stages, run deployments as a service principal, and control them with approvals and gated extensions.

Learn more

Use these resources to go deeper into each part of an agent's lifecycle:

• Establish an application lifecycle management strategy
• Power Platform environments overview
• Export and import agents using solutions
• Environment variables for Power Platform overview
• Use a connection reference in a solution with Microsoft Dataverse
• Overview of pipelines in Power Platform
• Deploy pipelines as a service principal or pipeline owner