Question

A Copilot Studio agent in a manufacturing company uses a custom connector to call an on-premises MES system. During ALM promotion from the development environment to test and production, the agent's connector action fails in each target environment because it points to the developer's personal credential and the dev-only endpoint URL. The architect must redesign the ALM approach so the same managed solution can be deployed across all environments without editing the agent after each import. Which approach should the architect adopt?

Accepted Answer

Use a connection reference in the solution and bind it to an environment-specific connection during (or after) import, along with an environment variable for the endpoint URL.

Answer

Hard-code the production endpoint and shared service-account credential directly into the connector definition before exporting the managed solution.

Answer

Export the solution as unmanaged to each environment so developers can manually update the connection and URL in place after every import.

Answer

Create a separate custom connector and agent copy in each environment and maintain them independently without a shared solution.