Showing results for 
Search instead for 
Did you mean: 

Enable Your Bot Framework Skills to Support Multi-Tenant Power Virtual Agents

Ever since Power Virtual Agents (PVA) have gone GA in December 2019, we’ve seen significant updates to this total No-Code visual authoring canvas. As an avid Conversational AI enthusiast, I have been following and implementing all of these updates either in my solutions or the demos at work. Out of several other improvement areas, Bot Framework Skills have been phenomenal both from the Framework perspective and also from the PVA support endpoint.


Few month back, I wrote about the extensibility of Power Virtual with Bot Framework Skills and how can you improve your customer experience without switching to any other conversational apps/channels. After observing the interests of people on forums, meetups and other platforms about this topic, I conducted a Skills Webinar this month with my dear friend, Mr. Charles Sterling from the Power Platform team.

In this post, it’s assumed that you are already aware of the basics of Bot Framework Skills i.e. publishing process on Azure and calling them from Power Virtual Agents. If you think you do not know about this then you may read this for the reference.

The tenant I used for Webinar’s demo was about to get expired and in that tenant, I opted for a lot of services which include Dynamics 365, AI Builder, Power Virtual Agents, Power Automate, Office 365 (for email!) and Azure 


I knew at the end of the month (or two), I had to bid farewell to this but the thoughts of setting up the skills (esp. the Azure trial) in the new environment were scaring me. Why? Because, to add a skill to PVA, the user signed into PVA can only add a skill that is deployed on her/his tenant.

So! I sat back. Thought of something and then decided to do simple stuff. Nothing complex at all.

All my work (except for the test data – which I did not want for now) was packaged under solution. Even the PVA, yes!


I downloaded the above solution (or package) while I was setting up my another trial. What I did not sign up for this time was Azure. Why? Because you get most of the stuff for FREE for a year and it’s super cool. But how could I run my Skill from this tenant to the other (new) one? That’s the motive of this post!

If you want to work with Azure and you’re just stuck because you do not have a credit card or anyway to sign up for FREE then please let me know – we at Azure Sydney User Group can help you with some free credit vouchers. All you have to do is just to tell me why do you need it for!

After setting up my new trial, I did opt for all other services again such as Dynamics 365, AI Builder, Power Virtual Agents and the Office 365 (this time it’s more important!). Then I delightfully decided to import my solution into it and it did not fail but… it did not bring my Bot’s assets.

Then I figured out you must have Power Virtual Agents solutions installed.

To achieve this in an easy way, just create a sample bot, for e.g. an AMA Demo Bot and then you will notice similar to the below image. You can then re-import your solution and you’ll have everything listed successfully!

Then I went to my PVA Portal and I could see that it brought everything successfully. I just had to re-connect my other Flows as they were not triggered (I do not know the reason why as it needs some more investigation).

Great work by the Product Team for this seamless import / export process. You can always follow this blog post for better understanding of import / export process!

The imported skill was pointing to my Azure tenant (which I secured for old trial) but as I sent a request to that, I got an error which was expected because Skill does not know my current PVA. One more thing to note is that this import process does not bring the Skill (as in Bot Framework Skill that’s hosted on Azure) itself, rather it brings the Skills configuration which you see under the Skills section / topic’s actions. Do give post-import docs a read here.

For that, you need to go to Skills sections, select Provide ID for Allow List and then add the same ID to your AllowedCaller’s list in your Skill’s appsettings.json file.


Once you’re done with this. Then you go to your active Azure portal (in my case, it was the one with my previous trial), add the new tenant’s user in your Azure AD.


Then go to your Subscriptions -> Access Control and add this user as Owner and in Active Directory as Group Administrator.


That’s all what I did! Now if you try to call your skill from the PVA, you should get the expected response similar to mine.


Thanks for reading!