Make a copy of a agent in same environment without disturbing the original agent

2026-07-28T10:16:55.2266667+00:00

Is it possible to make copy of a agent in same environment without disturbing the original agent. The import/export method via Solution doesn't seems to work well and it disturbs the original agent.

Microsoft Copilot | Microsoft 365 Copilot | Development
0 comments No comments

1 answer

Sort by: Oldest
  1. AI answer

    2026-07-28T10:17:13.46+00:00

    Yes. For a Microsoft 365 Copilot agent, the supported way to create a copy without changing the original is Copy to Copilot Studio.

    What happens when copied:

    • The original agent in Microsoft 365 Copilot remains available.
    • Copilot Studio creates a snapshot of the agent.
    • Updates to the original agent don’t affect the copied version.
    • Each copy operation creates a new agent in Copilot Studio.

    What is copied:

    • Name
    • Description
    • Instructions
    • Suggested prompts
    • Agent icon
    • SharePoint files, folders, and sites added as knowledge
    • Websites added as knowledge

    What is not copied and must be handled separately:

    • Enterprise knowledge (Copilot connectors): set up connectors after copying
    • Scoped Copilot connectors: not currently supported in Copilot Studio
    • Embedded files: upload again in Copilot Studio
    • Teams chats and meetings as knowledge: add the Power Platform connector for Teams
    • Emails as knowledge: add the Power Platform connector for Outlook
    • Create documents, charts, and code: add code interpreter in Copilot Studio
    • Create images from prompts: not currently supported in Copilot Studio

    How to do it:

    1. Open the agent in Microsoft 365 Copilot.
    2. Select More options (…).
    3. Select Copy to Copilot Studio.
    4. Save the copied agent in Copilot Studio.
    5. Test the copied agent before publishing it.

    If the goal is specifically to duplicate an agent by using solutions in the same environment, the documented solution flow is for moving agents across environments, and not all agent components and properties are included. Also, removing or changing agent components directly in a solution can cause export and import to fail. That makes solution-based duplication a poor fit for creating a safe same-environment copy.


    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.