mcs-deploy

To deploy a Copilot Studio agent to production, you can automate the process using PAC CLI for solution-level export and import or agent-level replication, ensuring ALM compliance across development and target environments.

Solution-level ALM deployment for Copilot Studio agents is the process of exporting solutions from a development environment and importing them to production using PAC CLI, ensuring application lifecycle management compliance and consistent configurations.

Yes, you can validate Copilot Studio agents before deploying to production by running pre-deploy validation checks to ensure the agent is published and meets required quality gates prior to environment replication.

Yes, Copilot Studio deployment supports post-deploy smoke testing to verify basic agent functionality in the production environment after the solution import or agent replication is complete.

Connection mappings identify and report the manual connection steps required in the target environment when moving agents between development and production, ensuring dependencies are correctly configured post-deployment.

Use agent-level replication for direct environment copying when ALM compliance is not required, and use solution-level deployment via PAC CLI when you need structured export and import for application lifecycle management.