A team is standardizing ALM for agents in Copilot Studio.

Comprehensive and Detailed Explanation From Microsoft AB-620 Study Guide: The required first action is to create a custom solution from the Solutions area. A solution is the ALM carrier that groups the agent with its related components and enables controlled export, import, pipeline deployment, dependency management, and versioning across environments. Exporting an agent directly is not the supported replacement for solution-based ALM. A channel configuration determines where users can interact with a published agent; it is not a container for development assets. Exporting a managed solution and importing it into production is a later release step and cannot occur until the custom solution exists and contains the agent and its dependencies. After creation, the team should add the existing agent, associated flows, connection references, environment-variable definitions, prompts, and any other required components. Development normally occurs in an unmanaged solution, while a managed build is deployed to Test and Prod. This separation supports repeatable promotion, protects downstream environments from unmanaged edits, and provides a clearer rollback and support boundary. Study Guide alignment: Test and manage agents > Implement application lifecycle management for agents in Copilot Studio > Create a solution.

===============