A retailer imports a Copilot Studio solution into test, and the connection references still point at production. What should happen before the next promote?
Select an answer to reveal the explanation.
Short Explanation
A fire drill that still rings the real alarm is not a drill. You rebind the retailer's connection references to the test connections before the next promote. Leaving them on production means the test run is a production run with a test label.
Full Explanation
A connection reference is the solution's placeholder for a connection, and each environment binds it to its own connection. This test deployment is still bound to production, so the test agent reads or writes production data while everyone believes they are in test. Rebind those references to the test connections and prove the agent there before the solution is promoted again. Leaving the references on production so the test agent exercises live retailer orders makes the test a production change, including any order the agent creates. Deleting the connection references and hard-coding production addresses inside the agent removes the placeholder the pipeline can retarget, and it locks production into every environment. Promoting on the existing schedule and retargeting only after production is updated ships the bad binding forward and fixes it on the live side, which is the opposite of a test. Exam caveat: the reference component travels in the solution, and the binding is environment-specific. Importing the solution does not choose the right connection for you. Operational check: open the test environment's connection bindings, confirm none of them are production connections, and run one order scenario that lands in test data.