ALM Foundation for Copilot Studio Agents
Diesen Beitrag auf Deutsch lesen
Use environments, solutions, publishers, pipelines, configuration and evaluations to move Copilot Studio agents safely from development to production.
TL;DR
Copilot Studio agents should move from Development to Test to Production through managed solutions and Power Platform Pipelines. Create a custom publisher first, keep all assets in a preferred solution, store environment-specific values in environment variables, protect secrets with Azure Key Vault, block unmanaged customizations downstream, and run evaluations before and after deployment.
Original by James Papadimitriou, on Microsoft Copilot Studio CAT. Read the original
This is our own summary, not a republication or full translation.
Governance takeaway
- Makers: Create the custom publisher and preferred solution before authoring agent assets, so components receive a deliberate prefix and remain deployable.
- Admins/CoE: Separate Development, Test, and Production, configure Power Platform Pipelines, and block unmanaged customizations in Test and Production to protect live agents.
- Security/Compliance: Keep credentials in Azure Key Vault through secret environment variables, because pipelines map references without storing secret values.
- Leadership/Business: Require evaluations before export and after import, so promotion confirms both deployment integrity and agent behavior.
Frequently asked questions
How should Copilot Studio agents move between Development, Test, and Production?
Use managed solutions and a Power Platform Pipeline to promote the same artifact from Development through Test to Production.
What does the block unmanaged customizations setting do in Power Platform environments?
It helps prevent local edits to managed components in Test and Production, reducing changes that deployments could silently overwrite.
Where should Copilot Studio agent API keys and tokens be stored?
Store secrets in Azure Key Vault and reference them through secret environment variables, allowing key rotation without redeployment.