An insurer is connecting a new claim system. The existing Copilot Studio agent already holds the topics adjusters use. A proposal would create a second agent and copy those topics into it so the new system has a home. What should the architect do?
Select an answer to reveal the explanation.
Short Explanation
You do not photocopy the whole office because a new filing cabinet arrived. You add the new claim system as an action on the agent that already holds the topics. A second agent with a copied topic list becomes two offices that disagree the first time a topic changes.
Full Explanation
Extensibility means the existing agent gains a way to call the new system. The topics adjusters already rely on stay in that one agent, and the new claim system is an action those topics can invoke. A second agent that holds a copy of the same topics creates a twin that must be edited whenever a topic changes, so the two agents drift and adjusters get different answers depending on which copy they open. Pasting the new system's field names into every topic buries connection details in wording and still does not give the agent one action to call, so each topic becomes its own unofficial integration. Retiring the existing agent and asking adjusters to paste claim numbers drops the topics the team already built and puts the lookup back on the person. Exam caveat: a new system of record is a reason to add an action and its connection, not a reason to fork the agent. Operational check: from the existing agent in a test environment, complete one claim action against the new system and confirm no second agent was published with a copy of the topics.