| page_type | sample | ||||
|---|---|---|---|---|---|
| description | This sample app demonstrate how to use Task Module using Bot Framework v4 | ||||
| products |
|
||||
| languages |
|
||||
| extensions |
|
||||
| urlFragment | officedev-microsoft-teams-samples-bot-task-module-csharp |
Bot Framework Teams Task Module sample.
This bot has been created using Bot Framework. It shows how to fetch a Task Module from Hero Card or Adaptive Card buttons and receive input from the Task Module in the bot.
- Microsoft Teams is installed and you have an account
- .NET SDK version 6.0
- ngrok or equivalent tunnelling solution
Note these instructions are for running the sample on your local machine, the tunnelling solution is required because the Teams service needs to call into the bot.
-
Run ngrok - point to port 3978
ngrok http --host-header=rewrite 3978
-
Setup for Bot
In Azure portal, create a Azure Bot resource.
- For bot handle, make up a name.
- Select "Use existing app registration" (Create the app registration in Azure Active Directory beforehand.)
- If you don't have an Azure account create an Azure free account here
In the new Azure Bot resource in the Portal,
- Ensure that you've enabled the Teams Channel
- In Settings/Configuration/Messaging endpoint, enter the current
httpsURL you were given by running ngrok. Append with the path/api/messages
-
Clone the repository
git clone https://github.com/OfficeDev/Microsoft-Teams-Samples.git
-
If you are using Visual Studio
- Launch Visual Studio
- File -> Open -> Project/Solution
- Navigate to
samples/bot-task-module/csharpfolder - Select
TeamsTaskModule.csprojorTeamsTaskModule.slnfile
-
Update the
appsettings.jsonconfiguration for the bot to use the MicrosoftAppId, MicrosoftAppPassword, MicrosoftAppTenantId generated in Step 2 (App Registration creation). (Note the App Password is referred to as the "client secret" in the azure portal and you can always create a new client secret anytime.)-
Set "MicrosoftAppType" in the
appsettings.json. (Allowed values are: MultiTenant(default), SingleTenant, UserAssignedMSI) -
Set "BaseUrl" in the
appsettings.jsonas per your application like the ngrok forwarding url (iehttps://xxxx.ngrok.io) after starting ngrok
-
-
Run your bot, either from Visual Studio with
F5or usingdotnet runin the appropriate folder. -
This step is specific to Teams.
- Edit the
manifest.jsoncontained in theTeamsAppManifestfolder to replace your Microsoft App Id (that was created when you registered your bot earlier) everywhere you see the place holder string<<YOUR-MICROSOFT-APP-ID>>(depending on the scenario the Microsoft App Id may occur multiple times in themanifest.json) - Edit the
manifest.jsonforvalidDomainswith base Url domain. E.g. if you are using ngrok it would behttps://1234.ngrok.iothen your domain-name will be1234.ngrok.io. - Zip up the contents of the
TeamsAppManifestfolder to create amanifest.zip(Make sure that zip file does not contains any subfolder otherwise you will get error while uploading your .zip package) - Upload the
manifest.zipto Teams (In Teams Apps/Manage your apps click "Upload an app". Browse to and Open the .zip file. At the next dialog, click the Add button.) - Add the app in personal/groupchat/team scope (supported scopes)
- Edit the
Note this
manifest.jsonspecified that the bot will be installed in "personal", "team" and "groupchat" scope which is why you immediately entered a one on one chat conversation with the bot. You can at mention the bot in a group chat or in a Channel in the Team you installed it in. Please refer to Teams documentation for more details.
You can interact with this bot by sending it a message. The bot will respond with a Hero Card and Adaptive Card with buttons which will display a Task Module when clicked. The Task Modules demonstrate retrieving input from a user, or displaying custom web page content.
- Personal Scope Interactions:
- Group Chat Scope Interactions:
- Team Scope Interactions:
To learn more about deploying a bot to Azure, see Deploy your bot to Azure for a complete list of deployment instructions.






