Question

A pro-dev team of five is building a complex Copilot Studio agent used across the company. Multiple developers frequently modify the same topics and custom actions in parallel, leading to lost changes when someone publishes over another's work. The ALM lead wants a repeatable process that captures every change, enables code review before promotion, and supports rolling back individual changes. Which approach best addresses these ALM requirements?

Accepted Answer

Add the agent's unmanaged solution to a Git repository via Power Platform source control integration, using feature branches and pull requests, then deploy managed solutions through a pipeline to test and production.

Answer

Have all developers work directly in the shared production environment and rely on Copilot Studio's built-in version history to revert mistakes.

Answer

Store the agent in a managed solution and use Power Platform Pipelines to promote it manually between environments after each publish.

Answer

Export the agent as a package after each session and email the zip file to the ALM lead for consolidation.