BotBuilder-Samples | Here you will find task | Bot library

Located in the BotBuilder-Samples GitHub repo: https://github.com/microsoft/BotBuilder-Samples

There is a sample app: 54.teams-task-module. This app demonstrates a task/fetch action with a Url to a Custom Form which is rendered by a Razor Page.

https://github.com/microsoft/BotBuilder-Samples/tree/main/samples/csharp_dotnetcore/54.teams-task-module

In the Bot, the OnTeamsTaskModuleFetchAsync method is overridden to return a TaskModuleResponse which tells the system to fetch the URL passed back to Teams in the response.

https://github.com/microsoft/BotBuilder-Samples/blob/main/samples/csharp_dotnetcore/54.teams-task-module/Bots/TeamsTaskModuleBot.cs

I have a c# Teams bot that uses multiple Generic Oauth2 providers. As an example I have used this sample https://github.com/microsoft/BotBuilder-Samples/tree/main/samples/csharp_dotnetcore/46.teams-auth

Also I have added Generic OAuth2 to Bot Registration in Azure. Everything works fine with single Oauth provider.

User after logout process must be able to authenticate to another oauth2 provider. But I'm faced with problem that OauthPrompt caches previous credentials, and I don't know how to clear this cache and properly sign out user

I've already tried different approaches to sign out user:

• Using UserTokenClient

I want to build a Teams bot that can send proactive messages, including creating conversations even if the user has never had a conversation with the bot.

I followed the proactive sample and adapted it to send a notification as POST in the notify controller. I am able to continue a conversation, but when I try to create one, the user does not get any messages.

Here is my code to create a conversation from the notify controller:

I have searched a bit but didn't found something which is helping me. I created a bot for teams and like described in all examples I am using the appsettings.json to store the ID and the password for the bot (MicrosoftAppId and MicrosoftAppPassword). These are both handled by the framework somehow. But now I want to use an Azure Key Vault to store the secret instead of having the appsettings file.

So I found some examples explaining how to do this in BotFramework V3 with BotAuthentication Attribute and even something for BotFramework V4 here (working link for the linked example here). But even that example is old and does not exist anymore like that.

How am I supposed to do this for a teams bot and c# dotnet 3.1?

I have an authentication issue when sending requests to MS Teams from a corporate environment (with a dedicated tenant). I don't know if this is a bug or if I misuse the SDK. I already saw Teams samples provided by Microsoft but all of these run on public Azure without dedicated tenant, and I suspect my issue is somewhat related to using a dedicated tenant (having a dedicated tenant, with either a bug in SDK, either a misconfiguration somewhere in my code or in the bot manifest).

The application I'm working on is very business specific, so I made a project to reproduce issue with minimal code in this github repository: msteams-bot-auth-issue. Using this sample project requires to have a Teams bot on a dedicated tenant (I obviously cannot publish my corporate tenant details).

Basically, our application is splitted in two parts: one receives bot activities from MS Teams channel. Another processes them (first part forwards activities to the second one).

We correctly receive activities from MS Teams. But we are unable to call an MS Teams API to get Teams members in conversation (HTTP 401 with response message { "message": "Authorization has been denied for this request." }).

Interestingly, if I use Microsoft.Bot.Connector v4.7.3 (version we actually use in our application), behavior is a bit different from Microsoft.Bot.Connector v4.15.0: in v4.7.3, no access token is requested before request to get conversation members; in v4.15.0, access token is successfully obtained, and put in request to conversation members request, but we still get an HTTP 401 response. Because we get HTTP 401 and not HTTP 403, I suppose access token is not recognized by MS Teams.

MS Teams response is always the same (HTTP 401 and error message), regardless an access token was included or not in request.

Access token request is composed of two requests:

• discovery (GET https://login.microsoftonline.com/common/discovery/instance?api-version=1.1&authorization_endpoint=https://login.microsoftonline.com/XXX/oauth2/authorize where XXX is our tenant name).
• client credentials request (POST https://login.microsoftonline.com/XXX/oauth2/authorize where XXX is our tenant name).

Response contains access token, logs are showing "GetTokenAsync: Acquired token using ADAL in 876" (logs emitted by Bot Framework SDK).

Then actual conversation members request is sent with access token (with HTTP header Authorization: Bearer ...), and response is always HTTP 401.

When I decode the JWT in https://jwt.io, I see these fields (among others):

• aud: https://api.botframework.com
• iss: https://sts.windows.net/XXX/ (where XXX is our tenant name)
• idp: https://sts.windows.net/XXX/ (where XXX is our tenant name)
• appid: YYY (where Y is our MicrosoftAppId)

Interestingly, if a set scope parameter in MicrosoftAppCredentials class to AuthenticationConstants.ToChannelFromBotOAuthScope, nothing changes in the JWT. So maybe access rights are not correctly setup for our application.

Maybe this is an issue with our application manifest, but I think we followed samples for MS Teams bots. permissions field in our manifest is set to [ "identity", "messageTeamMembers" ].

There are lots of resources about Bot Framework and MS Teams, but I did not found any meaningful documentation for this scenario.

This may be caused by a corporate proxy, but I don't think so (I cannot guarantee it).

I precise this is an app to app authentication, also sometimes described as "regular bot scenario" (no user authentication involved here).

I am developing a Teams application with AspNetCore and React with typescript. I would like to add the messaging extension functionality to my app. I have tested the available samples for Action based Messaging extension from here - https://github.com/microsoft/BotBuilder-Samples/tree/main/samples/csharp_dotnetcore/51.teams-messaging-extensions-action

I could run this sample and successfully connect to the bot I created in my Azure resource group.

Since I already have a Teams project created, I want to know if I can just add the code that makes the messaging extension work from this sample or do I need to have a separate project just for running the bot and messaging extension?

Note- I do not have a Bot implementation in my original project.

I am sending an adaptive card to teams with the bot framework. That is working fine. The card should contain an action that opens a task module like explained here.

My code for the card looks like this:

I have created a simple Azure Bot from a Typescript template from this tutorial. I have tested it in the Bot Framework Emulator and now want to deploy it to Azure. I am trying to follow the instructions here. I get as far as the step "Deploy via ARM template with existing resource group" (I have already created a Resource Group).

So I am trying to run this command from the command line:

I can run this Teams Bot sample: https://github.com/microsoft/BotBuilder-Samples/tree/main/samples/csharp_dotnetcore/57.teams-conversation-bot

When I need to add an AudioCard to play a mp3 song, I updated my code: