SOLVED

Power Virtual Agents for Microsoft Teams & Power Automate connectors

%3CLINGO-SUB%20id%3D%22lingo-sub-2833353%22%20slang%3D%22en-US%22%3EPower%20Virtual%20Agents%20for%20Microsoft%20Teams%20%26amp%3B%20Power%20Automate%20connectors%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2833353%22%20slang%3D%22en-US%22%3E%3CP%3EHello%2C%20Teams%20developer%20friends.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20have%20discovered%20how%20simple%20and%20powerful%26nbsp%3BPower%20Virtual%20Agents%20for%20Teams%20is%20and%20currently%20exploring%20how%20we%20can%20integrate%20with%20other%20systems.%20We%20plan%20to%20use%26nbsp%3BPower%20Automate%20connectors%3B%20however%2C%20we%20have%20noticed%20that%20all%20premium%20connectors%20fail%20to%20execute%20with%20a%20generic%20error.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20believe%20that%20an%20additional%20license%2Fsubscription%20is%20required%20to%20use%26nbsp%3BPower%20Virtual%20Agents%20for%20Teams%20in%20conjunction%20with%20premium%20connectors.%20The%20plan%20is%20named%20%22Standalone%20Power%20Virtual%20Agents%20subscription%22%3B%20however%2C%20it%20introduces%20a%26nbsp%3B%3CSPAN%3E%241%2C000%20monthly%20fee%20(not%20consumption-based).%20This%20is%20a%20lot%20of%20money%20when%20building%20a%20small%20system%20for%20our%20internal%20department%20and%20therefore%20wondering%20if%20there%20are%20any%20other%20options.%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESo%20far%2C%20we%20are%20thinking%20of%20the%20following%3CBR%20%2F%3E-%20Stop%20using%26nbsp%3Bthe%20Power%20Virtual%20Agents%20and%20create%20a%20custom%20teams%20bot.%3C%2FP%3E%3CP%3E-%20Execute%20the%20tasks%20under%20the%20context%20of%20a%20user%20who%20has%20access%20to%20premium%20connectors%20(not%20sure%20if%20this%20is%20allowed%20%2Fpossible)%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMaybe%20we%20have%20overlooked%20other%20options%2C%20and%20all%20suggestions%20are%20welcome.%20Ideally%2C%20we%20would%20stick%20with%20the%20Power%20Virtual%20Agents%2C%20but%20without%20the%20ability%20to%20call%20HTTP%20endpoint%2C%20the%20usage%20of%26nbsp%3BPower%20Automate%20is%20very%20restricted.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EThank%20you%20in%20advance.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2833353%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EDeveloper%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMicrosoft%20Teams%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2837258%22%20slang%3D%22en-US%22%3ERe%3A%20Power%20Virtual%20Agents%20for%20Microsoft%20Teams%20%26amp%3B%20Power%20Automate%20connectors%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2837258%22%20slang%3D%22en-US%22%3ECould%20you%20explain%20your%20requirement%20in%20more%20detail%3F%20So%20that%20we%20can%20suggest%20you%20something%20accordingly.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2844424%22%20slang%3D%22en-US%22%3ERe%3A%20Power%20Virtual%20Agents%20for%20Microsoft%20Teams%20%26amp%3B%20Power%20Automate%20connectors%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2844424%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1092873%22%20target%3D%22_blank%22%3E%40HunaidHanfee-MSFT%3C%2FA%3E%26nbsp%3BThank%20you%20for%20your%20reply.%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%3CP%3EWe%20want%20to%20use%20the%20bot%20as%20the%20entry%20point%20for%20our%20internal%20knowledge%20base%2Fsupport%20team.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EManually%20created%20topics%20are%20in%20place%20to%20cover%20top%20X%20questions.%20Each%20flow%20has%20a%20generic%20exit%20in%20case%20the%20topic%20isn't%20able%20to%20provide%20a%20suggestion.%20Within%20this%20flow%2C%20we%20would%20like%20to%20create%3A%3CBR%20%2F%3E%3CBR%20%2F%3E1.%20Create%20a%20Jira%20ticket%20(but%20we%20are%20fine%20with%20using%20azure%20boards%20as%20well)%3CBR%20%2F%3E2.%20Create%20a%20new%20conversation%20in%20a%20dedicated%20internal%20support%20Teams%26nbsp%3B%3C%2FP%3E%3CP%3E3.%20Initial%20message%20should%20include%20the%20ticket%20name%20as%20well%20as%20tagging%20the%20name%20of%20the%20person%20initiating%20the%20bot%20conversation%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20don't%20have%20any%20problems%20implementing%20items%202%20and%203%3B%20however%2C%20the%20first%20point%20requires%20a%20premium%20connector.%20We%20tried%20to%20use%20the%20HTTP%20connector%3B%20however%2C%20it%20also%20requires%20a%20premium%20Power%20Virtual%20Agents%20Plan.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIt%20would%20be%20great%20to%20use%20the%20free%26nbsp%3BPower%20Virtual%20Agents%20for%20Microsoft%20Teams%20plan%20in%20conjunction%20with%20an%20azure%20app%20service%20plan.%20Our%20bot%20traffic%20is%20internal%20only%26nbsp%3B(Teams)%20and%20has%20meager%20traffic.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20want%20to%20create%20awesome%20experiences%20using%20lots%20of%20automation%20at%20the%20end%20(only%20HTTP%20would%20be%20good%20enough).%20Creating%20our%20own%20bot%20is%20an%20option%2C%20but%20we%20really%20like%20the%20low-code%20way%20of%20creating%20topics.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EKind%20regards%2C%3CBR%20%2F%3EKevin%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2845571%22%20slang%3D%22en-US%22%3ERe%3A%20Power%20Virtual%20Agents%20for%20Microsoft%20Teams%20%26amp%3B%20Power%20Automate%20connectors%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2845571%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1181762%22%20target%3D%22_blank%22%3E%40bronsdijk%3C%2FA%3E%26nbsp%3B-%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThe%20only%20two%20possible%20options%20available%20is%20premium%20connector%20and%20the%20bot.%20That%20you%20are%20already%20aware.%20I%20checked%20to%20see%20any%20other%20low%20code%20option%20but%20there%20isn't.%3C%2FP%3E%0A%3CP%3EYou%20need%20the%20handle%20the%20situation%20using%20bot%2C%20that's%20what%20I%20can%20say.%3C%2FP%3E%0A%3CP%3EThanks%2C%20%3CBR%20%2F%3EHunaid%20Hanfee%3CBR%20%2F%3E-----------------------------------------------------------%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22TextRun%20%20BCX8%20SCXO124924259%22%20data-contrast%3D%22auto%22%3E%3CSPAN%20class%3D%22NormalTextRun%20%20BCX8%20SCXO124924259%22%3EIf%20the%20response%20is%20helpful%2C%20please%20click%20%22**%3CSTRONG%3EMark%20as%20Best%20Response%3C%2FSTRONG%3E**%22%20and%20like%20it.%20You%20can%20share%20your%20feedback%20via%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FSPAN%3E%3CA%20class%3D%22Hyperlink%20%20BCX8%20SCXO124924259%22%20href%3D%22https%3A%2F%2Faka.ms%2FDevSupportFeedback)%22%20target%3D%22_blank%22%20rel%3D%22noreferrer%20noopener%22%3E%3CSPAN%20class%3D%22TextRun%20%20BCX8%20SCXO124924259%22%20data-contrast%3D%22auto%22%3E%3CSPAN%20class%3D%22NormalTextRun%20%20BCX8%20SCXO124924259%22%3EMicrosoft%20Teams%20Developer%20Feedback%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FA%3E%3CSPAN%20class%3D%22TextRun%20%20BCX8%20SCXO124924259%22%20data-contrast%3D%22auto%22%3E%3CSPAN%20class%3D%22NormalTextRun%20%20BCX8%20SCXO124924259%22%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3Elink.%20Click%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FSPAN%3E%3CA%20class%3D%22Hyperlink%20%20BCX8%20SCXO124924259%22%20href%3D%22https%3A%2F%2Faka.ms%2FDevCommunityEscalationForm%22%20target%3D%22_blank%22%20rel%3D%22noreferrer%20noopener%22%3E%3CSPAN%20class%3D%22TextRun%20%20BCX8%20SCXO124924259%22%20data-contrast%3D%22auto%22%3E%3CSPAN%20class%3D%22NormalTextRun%20%20BCX8%20SCXO124924259%22%3Ehere%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FA%3E%3CSPAN%20class%3D%22TextRun%20%20BCX8%20SCXO124924259%22%20data-contrast%3D%22auto%22%3E%3CSPAN%20class%3D%22NormalTextRun%20%20BCX8%20SCXO124924259%22%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3Eto%20escalate.%3C%2FSPAN%3E%3C%2FSPAN%3E%3CSPAN%20class%3D%22EOP%20%20BCX8%20SCXO124924259%22%3E%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2969632%22%20slang%3D%22en-US%22%3ERe%3A%20Power%20Virtual%20Agents%20for%20Microsoft%20Teams%20%26amp%3B%20Power%20Automate%20connectors%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2969632%22%20slang%3D%22en-US%22%3EThanks%20for%20this%2C%20can%20I%20just%20check%20what%20you%20mean%20by%20the%20response.%3CBR%20%2F%3E%3CBR%20%2F%3EAm%20I%20able%20to%20license%20one%20user%20with%20Power%20Automate%20(%2415pm)%20that%20the%20bot%20then%20uses%20to%20execute%20flows%20against%3F%3CBR%20%2F%3EThank%20you%3CBR%20%2F%3EMorne%3C%2FLINGO-BODY%3E
New Contributor

Hello, Teams developer friends.

 

We have discovered how simple and powerful Power Virtual Agents for Teams is and currently exploring how we can integrate with other systems. We plan to use Power Automate connectors; however, we have noticed that all premium connectors fail to execute with a generic error. 

 

We believe that an additional license/subscription is required to use Power Virtual Agents for Teams in conjunction with premium connectors. The plan is named "Standalone Power Virtual Agents subscription"; however, it introduces a $1,000 monthly fee (not consumption-based). This is a lot of money when building a small system for our internal department and therefore wondering if there are any other options. 

 

So far, we are thinking of the following
- Stop using the Power Virtual Agents and create a custom teams bot.

- Execute the tasks under the context of a user who has access to premium connectors (not sure if this is allowed /possible)

 

Maybe we have overlooked other options, and all suggestions are welcome. Ideally, we would stick with the Power Virtual Agents, but without the ability to call HTTP endpoint, the usage of Power Automate is very restricted. 

 

Thank you in advance.

 

3 Replies
Could you explain your requirement in more detail? So that we can suggest you something accordingly.

@HunaidHanfee-MSFT Thank you for your reply.

We want to use the bot as the entry point for our internal knowledge base/support team.

 

Manually created topics are in place to cover top X questions. Each flow has a generic exit in case the topic isn't able to provide a suggestion. Within this flow, we would like to create:

1. Create a Jira ticket (but we are fine with using azure boards as well)
2. Create a new conversation in a dedicated internal support Teams 

3. Initial message should include the ticket name as well as tagging the name of the person initiating the bot conversation

 

We don't have any problems implementing items 2 and 3; however, the first point requires a premium connector. We tried to use the HTTP connector; however, it also requires a premium Power Virtual Agents Plan. 

 

It would be great to use the free Power Virtual Agents for Microsoft Teams plan in conjunction with an azure app service plan. Our bot traffic is internal only (Teams) and has meager traffic.

 

We want to create awesome experiences using lots of automation at the end (only HTTP would be good enough). Creating our own bot is an option, but we really like the low-code way of creating topics.

 

Kind regards,
Kevin

best response confirmed by bronsdijk (New Contributor)
Solution

@bronsdijk - 

The only two possible options available is premium connector and the bot. That you are already aware. I checked to see any other low code option but there isn't.

You need the handle the situation using bot, that's what I can say.

Thanks,
Hunaid Hanfee
-----------------------------------------------------------

If the response is helpful, please click "**Mark as Best Response**" and like it. You can share your feedback via Microsoft Teams Developer Feedback link. Click here to escalate. 

www.000webhost.com