msteams | script allows you to login into your meetings or classes | Automation library

The requirement is printing the FAQ ( QnA Maker result consider as an attachment in Adaptive Card Body ) contents in MS Team Bot ( HR Bot ). The core technology that we are using is C# with ASP.NET Core, Bot Framework SDK.

FAQ Bot Example:

• User is asking payroll related details in MS Team Bot.
• The response contains payroll document details ( Embedded as URL with bold or italic ).
• All responses return as an attachment ( Adding this response in attachment in adaptivae card body and after that posting using send activity ).
• AdaptiveCard version is 1.2

It's a FAQ bot and there are no code changes happening yet for the last two weeks. All these issues were encountered after the chrome latest updates ( Chrome updates).

We have tried the following scenario for the embedded hyperlink issue.

1. The Following answer hyperlink is opening on the MS-Teams app

Markdown Syntax in the QnA Maker

1. The Following answer is not opening on the MS-Teams app( embedded hyperlink is changed to Bold/Italic)

Answer Markdown Syntax in the QnA Maker

Note:

• Opening MS teams bot in a Firefox Browser, then all scenarios are working.
• Opening MS teams Bot in a Chrome Browser, then the second point is not working as I mentioned above
• The detailed discussion on the same issue posted on github - expecting a quick fix because of customer need.

Enlarge Image Issue:

We are facing a similar issue mentioned in github.

We are trying the following payload using MSTeams Bot access Token to create the Personel chat Room with the provided topicName.

Request : POST /v3/conversations

I'm having an issue where buttons and actions in ms teams adaptive cards won’t wrap text inside the action button. The button UI is completely broken even if we are applied " full: width" in MS Team. I know the "Wrap: true || false" we can add inside the adaptive card body or title of the textblock, Is there any other way to handle this type of scenario in the action button title in MS Team channel.

The following code we are using for the adaptive card implementation.

We are facing issue on getting the user submitted input data from Adaptive card posted via MSTeams Graph API. We have a Team Channel that has two members:Global Admin and the user. We posted the following Adaptive card using Global Admin token.

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:

It's possible to send a proactive message (=private) to the sender of a message in a teams groups chat using the next part of code:

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 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:

Using botframework with msteams channel.

The adaptive card. Nothing special, just a few textblocks and date inputs. The input values are saved to memory.