Teams Chat Assist ARM Deployment

Teams Chat Assist Bot can be provided as an Azure Resource Manager (ARM) template that automatically provisions and starts the required resources in your Azure subscription.

Deploy To Azure Visualize

Note: You must have registered an application beforehand.

Note: For an introduction to Azure Resource Manager see docs.microsoft.com.

This ARM Template will install resources in your Azure tenant. The template will deploy the following resources:

Service Type Description
Web App Bot S1 Standard
Web App Service S1, 100 Total ACU, 1.75GB memory, A-Series Compute Equivalent
Key Vault Securely stores Web App Bot Secret
SignalR Service 1 Unit, 1K Connections, 1M Messages per day
Application Insights Logs for Web App Bot and Web App Service
Storage Accounts Block Blob Storage, General Purpose V2, RA-GRS Redundancy, 1,000 GB Capacity, 100 Storage transactions

Installation

  1. Click on the ARM template link that was provided by us. You will be taken to Microsoft Azure Portal and a deployment form will open as shown below.

    Custom deployment form

  2. Carefully fill in the fields. In some cases the tooltips may provide extra guidance.

    • Basics
      • Subscription - Choose the Azure subscription to which deployed resources will be billed.
      • Resource group - It is strongly recommended that you create a new resource group for logical grouping and management of Teams Chat Assist. When applying an upgrade choose the Resource Group that already contains Teams Chat Assist.
      • Location - The location of the newly created resource group (this only determines the geographical location of resource group and its metadata, to change the location of the resources themselves, see Location below).
    • Settings
      • Azure Application details - Use the details you generated when registering an application.
      • Bot Display Name - This is the name of the Bot that your users will see
      • Environment Name - This is the name of your environment and is used by Modality to help identify within logs when “Logs To Modality” is set to yes. The name of your company would be a good choice. Must be between 2 and 6 characters long and contain letters only.
      • Logs To Modality - Defaults to Yes will send logging information to Modality for better troubleshooting
      • Storage Name - It is strongly advised to leave this as default which will create a storage account starting tg followed by a unique string.
      • Deploy Code - For changes that require no updates to the Teams Chat Assist codebase, such as adding additional Bot instances, choose No. Otherwise stick with the default which is Yes
  3. Read the Terms and Conditions, then click “I agree to the terms and conditions stated above” and click “Purchase” (this refers to the resources hosted on Azure, and is not a usage agreement for Teams Chat Assist.)

  4. After a period of deployment you should see the following confirmation screen.

    Deployment Complete

  5. Click on Outputs and you will get the following.

    Deployment Complete

  6. Copy the value for agentAuthResponseURL somewhere safe as you will need it later.

  7. By clicking on Go to Resource Group you should get a Resource group in your tenant with the following components

    Resource Group

    The name of the Web App Bot is the Azure Application ID you entered in step 2. The other resources have a suffix of the ResourceGroup ID (not visible in Microsoft Azure Portal).

  8. Go to your Application Registration, Azure Active Directory -> App registrations -> Teams Chat Assist Bot -> Authentication and click Add a Platform, then click Web

    Add web platform

  9. Under Redirect URI paste the value from agentAuthResponseURL that you copied earlier.

    Add web platform

  10. The next step is to provision settings for your tenant in the storage account. The easiest way to do this is using the Azure Storage Explorer

    If your company uses AD FS then you might have trouble signing into Azure Storage Explorer so try:

    • On the left vertical tool bar, open Settings. In the Settings Panel, go to Application > Sign in. Enable Use device code flow sign-in.
    • Open the Connect dialog box (either through the plug icon on the left-side vertical bar or by selecting Add Account on the account panel).
    • Choose the environment you want to sign in to.
    • Select Sign In.
    • Follow the instructions on the next panel.
  11. Using Azure Storage Explorer that you have just installed, connect to your Azure Tenant and locate that storage account that was created as part of the ARM Deployment

  12. Import the default values into table storage

  13. Use the Teams Web App to create a new Team for the bot to post agent messages too

  1. Edit the InstanceConfigurations table as desired

Applying Upgrades to Teams Chat Assist

To apply an upgrade to Teams Chat Assist you would simply click on the “Deploy to Azure” button above and ensure that all options are the same as from the initial installation. By redeploying to the same resource group and subscription, you are in affect updating things that are different.

Adding additional Bot Instances

Teams Chat Assist supports multiple Bot Instances for different workloads. Each Bot requires its own unique bot registration in a 1 to 1 relationship. Multiple Bot instances will all link to the same underlying infrastructure so updating the codebase for 1 Bot Instance will upgrade all. To add additional Bot Instances simply click on the “Deploy to Azure” button above and specify the new:

Set Deploy Code to No and ensure that all other values match the initial deployment

When applying updates to environments with multiple Bot Instances, you can use the App ID, App Secret, Bot Display Name of any of your Bot Instances

Bot Manifest

  1. The backend deployment is now complete but for people to interact with the Bot you will need to create a manifest file and install into Microsoft Teams.