Host Bot in Azure for MS Teams

2 minute read

Host Bot in Azure for MS Teams

Overview

During previous article - Develop Bots For MS Teams With Bot Builder V4 SDK, we developed an echo bot with Bot Builder v4 utilizing ngrok to develop and test locally. ngrok is used during the development phase. It allows us to build and test the bot without publishing the app on MS Azure (or other hosting environments).

In this article, we will publish our app (Bot) to MS Azure and channelize to MS Teams.

Publish Bot to MS Azure

Follow below steps to publish the Bot application to MS Azure App Service.

  1. Open the Bot application (i.e. office-content-management) in Visual Studio.
  2. Open “\office-content-management\Manifest\manifest.json”.
  3. Update the package name as a generic name representing Bot.
  4. Update websiteUrl, privacyUrl, and termsOfUseUrl as an organization url.

     {  
       "$schema": "https://developer.microsoft.com/en-us/json-schemas/teams/v1.3/MicrosoftTeams.schema.json",  
       "manifestVersion": "1.3",  
       "version": "1.0.0",  
       "id": "619674bb-c724-4fa0-b42d-22787d35f569",  
       "packageName": "com.contoso.contentmanagement",  
       "developer": {  
         "name": "Office Developer",  
         "websiteUrl": "https://www.microsoft.com",  
         "privacyUrl": "https://www.microsoft.com/privacy",  
         "termsOfUseUrl": "https://www.microsoft.com/termsofuse"  
       },  
       "icons": {  
         "color": "bot-icon-color-192x192.png",  
         "outline": "bot-icon-outline-32x32.png"  
       },  
       "name": {  
         "short": "office-content-management-bot ",  
         "full": "Office Content Management Bot"  
       },  
       "description": {  
         "short": "Office Content Management",  
         "full": "Sample bot for the Office Content Management"  
       },  
       "accentColor": "#AB00B0",  
       "bots": [  
         {  
           "botId": "619674bb-c724-4fa0-b42d-22787d35f569",  
           "supportsFiles": true,  
           "scopes": [  
             "personal",  
             "team"  
           ]  
         }  
       ],  
       "composeExtensions": [],  
       "permissions": [  
         "identity",  
         "messageTeamMembers"  
       ],  
       "validDomains": []  
     }
    
  5. Click Build menu, select Publish office-content-management.

  6. Pick a publish target as App Service.
  7. Select to create new App Service.

  8. Click Advanced…
  9. Set Configuration to Release.
  10. Under File Publish Options, select option Remove additional files at destination to remove outdated files during deployment.

  11. Click Save to close the Advanced dialog.
  12. Click Publish on the main screen.
  13. In the Create App Service dialog, specify the needed information.

  14. Click Create.
  15. The Bot application will be deployed to MS Azure App Service.

  16. Post successful deployment, the app service url will open in a browser. (e.g. https://office-content-management20190918031143.azurewebsites.net/)

Update Manifest

Follow below steps to update the manifest with App service details:

  1. In the visual studio, open “\office-content-management\Manifest\manifest.json”.
  2. Set websiteUrl, privacyUrl, and termsOfUseUrl to the app service url.

  3. Build the solution. The AfterBuild target will run and compressed .zip file will be available under the bin folder.
  4. Upload app into Microsoft Teams. (Follow instruction from previous article Develop Bots For MS Teams With Bot Builder V4 SDK, section Upload app into Microsoft Teams).

Update Bot Channels Registration

From Azure portal, open the Bot Channels Registration, under settings, set the messaging endpoint as app service url.

Test the Bot in MS Teams

  1. Open MS Teams.
  2. From the left menu, click Chat.
  3. Our Bot (named OfficeContentManagement) should be listed out.
  4. Send the messages to Bot, it should echo back.

Summary

ngrok is used during the development phase. Once the Bot is ready it can be deployed hosted in Azure for public use. Visual Studio offers an easy option to deploy the app in Azure.

This content was originally posted here.

Hits

Leave a comment