Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Summary
This article helps you resolve a problem in Microsoft Copilot Studio in which an agent is missing components in a target environment. After you import an agent's solution into a target environment, new components that you add to the agent's source solution don't automatically appear in the imported version of the agent. Such new components could include topics, tools, actions, connectors, child agents, or Model Context Protocol (MCP) servers. This article describes how to add the missing components and how to avoid the problem.
Symptoms
After you import an agent's solution into a target environment, and then you add new components to the agent in the source solution, you experience one or more of the following problems:
- Topics are missing from the agent in the target environment.
- Knowledge sources are missing from the agent in the target environment.
- Environment variables are missing from the agent in the target environment.
- Components or tools that are linked to the agent in the source environment don't appear in the target environment.
Cause
When you import an agent's solution into a target environment, and you later modify the agent's source solution, the imported solution in the target environment doesn't automatically include any components that are added to the agent's source solution. The imported solution reflects the agent's state only at the time that you originally exported it.
Solution
To sync new components from the agent's source solution to the imported agent in the target environment:
- In Copilot Studio, go to Solutions, and then open the agent's source solution.
- In the Objects pane, locate your agent under Agents.
- Open the commands menu (⋮), select Advanced, and then select Add required objects.
- Export the source solution.
- Import the updated solution into your target environment.
For more information, see Export and import agents using solutions.
Note
If you add new components to the agent, repeat the previous steps to add required objects before you export the solution.
To prevent this problem, use one of the following approaches to keep agent changes in sync with the target environment's solution.
Create agents in the solution context
When you create an agent in a solution's context, Copilot Studio automatically adds new agent components to that solution. To create a new agent in your target environment's context, follow these steps:
- On the Home page of Copilot Studio, select the gear icon in the description box.
- In Agent settings, under Advanced settings, select the desired solution in your target environment.
If you already added the agent to your environment, open the agent from your target environment's solution (Solutions > Your Solution > Agent > Open), and then continue editing from that context.
Use a preferred solution in Copilot Studio
Copilot Studio supports solution-aware authoring through preferred solutions. When you set a preferred solution, new agents and component edits are created directly in that solution.
To set a preferred solution:
- On the sidebar, select the ellipsis (…).
- Select Solutions.
- On the top menu bar, select Set preferred solution.
- Choose the solution in your target environment that you want to create agents in by default.
For more information, see Solution management in Copilot Studio.
Verify the solution context of the agent
To verify that the agent is correctly mapped to your solution so that new components sync automatically:
- Open the agent.
- Select Settings > Agent details.
- Select View solution.
- Verify that the solution that's shown is your desired solution. If the agent isn't mapped to the correct solution, follow the steps in Create agents in the solution context or Use a preferred solution in Copilot Studio to update the mapping.