A maker finishes testing a Copilot Studio agent in a development environment and needs to move it to production using Application Lifecycle Management. Which approach best preserves connections and environment-specific configuration?
Select an answer to reveal the explanation.
Short Explanation and Infographic
Here's the deal — treat the agent like any other Power Platform asset. Ship it in a solution with connection references and environment variables so production can bind its own connections without hard-coded dev secrets.
Full explanation below image
Full Explanation
The correct approach is solution-based ALM: export the agent with connection references and environment variables, then import into production and provide production-scoped values. That keeps secrets and endpoints environment-specific while preserving the agent definition. Copying raw browser payloads is unsupported and fragile. Emailing ZIP files outside solution pipelines bypasses governance and source control. Manual recreation wastes time and introduces drift. Administrators should also use pipelines or automated imports for repeatability and approval gates.