Botframework
7 TopicsRegister bot without Azure process
Hi Microsoft Teams, I was looking on creating and hosting bots. I thought that it is required to host the bot in Azure but according to documentation it is not but it needs to registered in Azure bot framework using https://dev.botframework.com/bots/new. It also tells that we should also add Microsoft Teams as channel after the bot is registered. How does it work? What are the requirements to host it outside of Azure? Does it mean that it is free to register our bot? Please let me know the details because the documentation doesn't tell more information about this. Thank you.13KViews0likes10CommentsHow to capture replies to a bot's message in a Microsoft Teams Channel without mentioning the bot?
I have developed a message extension bot app for Microsoft Teams and I want to capture replies to a message posted by the bot in a Teams channel without requiring users to mention the bot directly. I am using Node.js and TypeScript for my bot. The bot is registered in the Azure Bot Service. I want to capture replies to this message without users needing to mention the bot. How can I achieve this? Any guidance or examples would be greatly appreciated!895Views0likes5CommentsHow to Send Replies in Microsoft Teams Using Bot Name Instead of Username via Graph API?
I'm working on an external application that sends replies to messages in Microsoft Teams using the Microsoft Graph API. Currently, the replies are sent using the username associated with the authenticated account. However, I want the replies to appear as if they're coming from the bot itself, using the application name registered in the Azure portal. The bot is also registered as a message extension app. Ideally, I want the responses to display the bot's name, rather than the username of the account making the API call. Here are the steps I'm currently following: The bot is authenticated and authorized using OAuth2 with the appropriate permissions. I use the /reply Or /message endpoint to send messages. I know we can use incoming webhook, but we can't use it. What I'm looking for: Any specific configurations needed in the Azure portal or Microsoft Graph API to achieve this. How to Send the message with the bot's name instead of the user's name. Any help would be greatly appreciated!604Views0likes5CommentsHow to Implement OAuth for a Bot-Based Message Extension App in Microsoft Teams for Graph API?
I have created a bot-based message extension app using the Teams Toolkit and need to call the Microsoft Graph API, which requires OAuth implementation. So far, I have created the app in the Teams Developer Portal, registered the app in Azure App registration, and registered the bot in the Bot Framework Developer Portal (dev.botframework.com). However, I am unclear about the OAuth flow and the specific configurations required. Can someone provide a detailed guide on how the OAuth flow works for a bot-based message extension in Microsoft Teams, the specific configurations needed in the Azure app registration, how to configure permissions and consent for accessing the Microsoft Graph API, and any additional settings required in the Teams Developer Portal or Bot Framework Developer Portal? Any guidance, code examples, or references to detailed documentation would be highly beneficial.324Views0likes0CommentsInconsistent Display of Array Property in Bot Framework Composer
Not sure if this is the right space for this. I have a Teams Bot built with the Bot Framework Composer and recently noticed the following behavior change. I grab the user's response via = turn.activity.text I set an array property to user.inputData [ { "role": "user", "content": "${turn.activity.text}" } ] Prior to a few days ago, step Send a Response: ${user.inputData} showed: [ { "role": "user", "content": "test" } ] now the step Send a Response shows: { "lgType": "Activity", "text": [ { "role": "user", "content": "test" } ] } however if I concatenate a string to it in step Send a Response: input is ${user.inputData} then it displays correctly: the input is [ { "role": "user", "content": "test" } ] It seems like the Bot Framework Composer is interpreting ${user.inputData} differently now. The new output format is treating user.inputData as an object with properties lgType and text, where text holds my array. Did the template engine change in processing expressions? I attempted to display user.inputData in two ways: directly and by concatenating it with a string. When displayed directly, I received an output showing the object with its properties ({ "lgType": "Activity", "text": [array] }). However, when I concatenated user.inputData with a string (e.g., input is ${user.inputData}), it displayed the array as expected, without the object properties. I was expecting consistent behavior in both cases, where user.inputData would simply display the array.Solved723Views0likes2CommentsBuilding and installing a Teams bot app for on-premises softwares
I am quite new to Teams and to building bots for it, so I am still trying to figure things out and find my way through the documentation. Using NodeJS, I built a simple prototype one that can receive notifications and send requests to my software. However, my software is installed on-premises, which means all users using it have a different domain name for it (xxx.com, abc.com…). To be able to use it, the app needs to know what is the endpoint of the requests. I wonder how I can build my bot app in those conditions and have it in the Teams Marketplace. My question is : I assume I want a team admin to set the domain name in some app settings before installing it for a team and users to use. Is it even possible? If yes how? I suppose it is possible to achieve that by having the users install a custom app, but then the app cannot be in the Marketplace. I also suppose I can ask individual users to first enter the name of the domain, it sounds repetitive and the info would then be stored in some userData. Isn't there some teamData instead? Could it mean having one user set those information and have them stored for everyone?1.4KViews0likes1Comment