Tell me where you need to set these permissions to be able to use the created bot ?
As suggested by #Prithvi-MSFT in the comment section, Please check with your admin to enable custom app uploading.
if you are installing the app directly from the App Studio instead of that, download it, then Upload it by clicking "Upload a custom app" in Apps.
Check this for Reference
Related
I deploy an app to play store console but the app was rejected due to privacy policy concern, So I update the app with privacy policy link in App content in the play console account also update the app bundle with privacy policy and then create a new release and upload by clicking on 'Rollout to Production'.
I want to know that-
Should I do anything else to tell google that I update the app and also provide a privacy policy link in the app content or google automatically review my app again?
As you've added the privacy policy link in the play console and submitted the app for review in the production track, your app will be reviewed. You don't have to do anything else.
I'm trying to allow the users that are already talking to the bot upload files (attaching the files to the bot).
I uploaded a manifest with "supportsFiles": true through "Upload Custom App".
But this only affects my conversation with the bot, the other users' manifest doesn't look like its updated because they can't see the attachment button.
Is there a way to update the bot's manifest for all the users in the organization?
This is not a published application, the users talk to the bot through the link from the registered bot in Azure Portal.
Any help is appreciate.
Thanks!
The Bots which are accessed via link won't update as there is no metadata associated with it. You need to create App Manifest for you Microsoft Teams.
Once you've created your app there are three options for distributing it.
Upload your app directly.
Publish your app to your organization's app catalog
Publish your app through AppSource
Please go through the options provided in the documentation and let us know if you need any help.
I have 2 different Microsoft Teams Accounts that are not linked in any way.
On one account I was able to sideload my bot and if I chat with my Bot in an Teams Channel my bot does Answer. Also it answeres me if I private message it.
On the other account I also sideloaded my bot but my Bot does not react if I message him in an Teams Channel. But it answeres me if I private message it.
I created both bots via App Studio in Teams.
Now I've noticed a difference in App Studio and I think this is why my Bot does not react.
Image of App Studio where the Bot works:
Image of App Studio where the Bot does not work:
The settings in App Studio where the Bot does not work are a bit shorter.
What is happening here? How can I make my Bot work?
Colby's answer might be the fix to you problem, however there are also other permissions settings that you can consider as well, if that doesn't fix it.
I have 2 different Microsoft Teams Accounts that are not linked in any way.
If your accounts are in different organizations, then it's possible that the lack of ability to see your bot that you've added in a Team Channel is due to settings set up by your org's admin. It states here in the Admin settings for apps in Microsoft Teams article in the Important text block:
Be sure you've turned on apps for Teams in Tenant-wide settings in the Microsoft 365 admin center. If you want to add external apps (provided by third parties), you'll need to turn on External apps settings.
From what I can see I think your issue is because the scope on your other bot is set to only Personal. If you click on edit and select "Team" via the Scope section it should fix your issue. Let me know if that helped.
First, new to creating Bots so please be patient.
I created a KB using QnAMaker. Created new Bot in Azure Bot Service. New bot was created using Template for QnA. Followed the steps below per documentation:
In Azure portal, open the newly created Web App Bot resource.
Click on "Application Settings" and in the App Settings list, add QnASubscriptionKey and QnAKnowledgebaseId. The corresponding values can be obtained from the KB Settings page in http://qnamaker.ai.
The QnAMaker-enabled Azure bot service app is now ready to use. To try it out click on "Test in Web Chat" to chat with your QnA bot.
Test in Web Chat does not respond
Also created new App, using Basic template. Made to other updates. Test in We Chat does send a response.
Again, new to the process but have read a great deal of documentation but nothing that speaks to this issue specifically. Any help would be greatly appreciated.
I created a QnAMaker bot this weekend with Bot Service. The documentation is a little confusing at the moment, although Microsoft generally refines it over time until it's quite good. Here's what I did to get this going.
Provisioned a QnAMaker service at qnamaker.ai. I created a knowledge base, saved and retrained, and published. To make sure everything is good on the QnAMaker service, go to the Test tab (https://qnamaker.ai/Edit/Test?kbId=:your-service-id to make sure you can chat with it and it responds as expected.
Created a new Web App bot by going to the portal, clicking "Create a resource", choosing "AI + Cognitive Services", then "Web App Bot".
When entering the Web App Bot settings, I made sure to choose a Basic C# bot, and chose the "Question and Answer".
Once you provision the Web App Bot service, you'll also have a Web App provisioned as well. You'll need to create a web application that will answer requests from the web, hand them to your QnAMaker service, and return the results. Navigate to your Web App Bot service, then choose the Build menu option under Bot Management. Then Download the zip file containing your starter code.
Open the starter code. You'll need to add some keys to your web.config file. Make sure that you have keys for the following, and that they're populated: MicrosoftAppId, MicrosoftAppPassword, QnaSubscriptionKey, QnAKnowledgebaseId, and AzureWebJobsStorage. If memory serves, these values are read within the code, but there's no empty stubs in the web.config that prompts you to enter them. This was a little frustrating.
After updating web.config, publish the web app to your Azure Web App instance associated with your bot.
Now go back to your Web App Bot in the portal. Under Bot Management, go to the Settings page. You're going to need to enter in the Messaging endpoint so that your bot service knows where to send HTTP requests to your web app, which will in turn talk to your QnAMaker service. In this example project, your messaging endpoint should be https://[web app name].azurewebsites.net/api/messages.
NOW you're ready to Test in Web Chat. Everything should link up then.
I had this issue just now. It was caused by having extraneous data at the end of my QNA service key, something like (format=json) which somehow ended up after the key. I suggest you re-copy and paste the knowledgebase id and key into the fields and make sure they are the correct length with no garbage.
Apart from not returning responses it gave no other clue as to what might be wrong.
Since the new Azure Bot Service (released GA 2017-12-13), I've created a "WebAppBot" named "SanoBot" and I can't choose any channel to plug it for another services like Telegram: the page is empty when I click on "Channels". I've done a little screenshot to show you what I see:
I've check the documentation sent by the Azure Support from Twitter but the pages return 404 error.
Just to be clear: the bot works well and I can modify it from the Online Editor, build, deploy & test it. It's only "channels" feature that doesn't work.
Thanks for your help.
I can't use pictures because I haven't enough reputation...