cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
scottyb
New Member

Export a Bot Solution to another Tenant / Environment

Firstly, great application you have built - it really seems to have made it easier to build and deploy bots than use .NET and the Bot Framework to make simple bot solutions.

 

However I have a question in relation to exporting a bot to another tenant, as we may have a requirement where we build a Bot for a customer requirement in our tenant and then need to export it into their own tenant or environment- in a similar way in that Flow can export and then be imported.


I have checked the 'Deploy' area and see no ability to export / import the bot, so I wondered if this is possible and if so, are there any constraints to consider - such as having built Flow integrations within the bot etc.

 

Thanks!

16 REPLIES 16
JoeGill
Resolver I
Resolver I

You can provide your client with a copy of your solution containing the PVA bot. They can import the solution into their tenancy from the power platform maker portal.

Medkhalil
Helper I
Helper I

@JoeGill ,thank you for your feedback. No extra steps are required as we have Power Automate Flows used by the BOT?
By creating a new PVA connection reference, I think we will have a new BOT ID. 

JoeGill
Resolver I
Resolver I

I would expect your Flows to also be included in the solution (or another solution) as they need to be created in the client's tenancy.  

Indeed they are in the same solution with the PVA BOT. I was checking because the BOT is no longer working when we embed it into a website after deployment on the second tenant. The Microsoft support mentioned that there is no official documentation to move PVA BOT between tenants and that can be the main reason for getting a 3000 error code.

Medkhalil_0-1662728873489.png

 

JoeGill
Resolver I
Resolver I

Sorry for the delay. I may be misunderstanding your issue. I just created a bot with a simple flow and was able to import into a new tenancy without issue. Is this a user authentication issue? or you trying to access deployed bot in another tenancy?

I was trying to use the deployed bot on the new tenant from the client side using a custom webchat widget with Directline API. I got that error for the BOT from  the new tenant. The other BOT work as expected from the client side as below :

Medkhalil_0-1663231759448.png

 



JoeGill
Resolver I
Resolver I

Sorry for the delay.  I was able to generate a token in the tenancy where I imported my bot solution.

I was able to use this to connect using the webchat.directline without issue

 

If you want to send me a sample bot solution I can try it

 

Screenshot 2022-09-20 060925.png

Screenshot 2022-09-20 060925.png

Helpful resources

Announcements
Microsoft 365 Conference – December 6-8, 2022

Microsoft 365 Conference – December 6-8, 2022

Join us in Las Vegas to experience community, incredible learning opportunities, and connections that will help grow skills, know-how, and more.

Difinity Conference 2022

Difinity Conference 2022

Register today for two amazing days of learning, featuring intensive learning sessions across multiple tracks, led by engaging and dynamic experts.

European SharePoint Conference

European SharePoint Conference

The European SharePoint Conference returns live and in-person November 28-December 1 with 4 Microsoft Keynotes, 9 Tutorials, and 120 Sessions.

Power Virtual Agents Ideas

Changes to Ideas Coming

We are excited to announce a new way to share your ideas for Power Virtual Agents!

Top Solution Authors
Users online (3,021)