Answered

How to duplicate a Copilot?

(1) Share

Report

Posted on by andypejman

Is there a way to duplicate a Copilot? Let's say we want to make another Copilot, but we don't want to start from scratch, so we'd want to duplicate it as a starting point, is that possible with Copilot Studio?

Categories:

General topics

I have the same question (0)

All responses (6)

Answers (1)

adilei on at

Like (1)

Report

Cloning copilots is not currently supported. However, you can still “clone” topics across copilots by copying and pasting the topics’ YAML code. The number of topics in your original copilot will determine how much work this will be.

Was this reply helpful? Yes No
andypejman 11 on at

Like (0)

Report
Thank you, I had two questions:

Is there an ETA on when cloning copilots would be able to happen?
Is there an ETA on when the "Allowlist" feature will be available? (See screenshot attached).

Screenshot 2024-0...

Was this reply helpful? Yes No
Verified answer

adilei on at

Like (10)

Report
Well, it seems my information regarding cloning wasn't up to date 🙂

It is now possible to clone copilots using the Power Platform CLI.

If you haven't had a chance to use the Power Platform CLI so far, the most straight forward way to get started would be installing the CLI using the Power Platform Tools VS Code extension.

Here are the steps to add the extension and clone a copilot. Jump to step (3) if you already have the Power Platform CLI installed and working.

1. Install the Power Platform CLI by adding the Power Platform Tools extension to VS Code: Microsoft Power Platform CLI - Power Platform | Microsoft Learn

2. Create an auth profile for the environment(s) where you copilots are stored, by clicking on the Power Platform icon in the sidebar, and then "New Auth Profile"

3. Export your source copilot/bot by starting a new terminal in VS Code, and running the following command:

pac virtual-agent extract-template --bot SOURCE_BOT_ID --environment ENVIRONMENT_ID --templateFileName sourceBot

This will create a "template" - a local file with the YAML code for your exported copilot/bot.

4. Create a new copilot/bot from the template you have just exported, using the following command:

pac virtual-agent create --SchemaName prefix_destinationBotName --TemplateFileName sourceBot --displayName DESTINATION_BOT_NAME --solution SOLUTION_NAME --environment ENVIRONMENT_ID

Couple of things to note here:

SchemaName is used to create the copilot's Dataverse table, so it must include a prefix followed by an underscore
TemplateFileName refers to the file exported in step (3)
The "solution" parameter refers to a solution that already exists in the environment

Let me know in case you run into any challenges!

Was this reply helpful? Yes No
NicolasGeolives 14 on at

Like (0)

Report

Hi, I tried to use your method to duplicate my copilot but unfortunately it doesn't work. I tried with the pac copilot and pac virtual-agent commands but the result is the same. Here is the full description of my error: https://powerusers.microsoft.com/t5/General/Error-while-creating-a-copilot-based-on-a-template/m-p/2606848

Hoping you'll be able to help me

Was this reply helpful? Yes No
Mina Saad 2 on at

Like (0)

Report

Thanks @Adilei for your answer, it is really a life saver.

Just I'm having an issue if you have faced before, when I'm creating the new bot it gives me the following error message

Error: HTTP Status:BadRequest, ServiceRequestId: 608c907e-f17a-491d-ba99-a7f75ecda467 [0x80048408:InvalidStateCodeStatusCode] 2 is not a valid status code for state code botcomponentState.Active on botcomponent with Id 99ed7f5c-b5c9-48b1-a8dc-33b4b89e5c92.

The issue is that I can't find this botcomponent with that Id, do you have any clue?

Was this reply helpful? Yes No
Suggested answer

Sohom Ghorai 87 on at

Like (0)

Report

Hi @Mina,

I have faced the same issue as you

HTTP Status:BadRequest, ServiceRequestId: 2 is not a valid status code for state code botcomponentState.Active on botcomponent with Id

I have got an workaround for this .

Before exporting the template make sure no topics are disabled . After enabling all that issue got resolved

Was this reply helpful? Yes No