Deploy a Calls & Meetings Automation scenario (CAT)

Note: this is for CAT (Customer Azure Tenant) customers, who manage their own Azure components for Teamwork Analytics but use the Modality automation service. If you have Modality manage TWA for you (SaaS or CSP models), this is done for you by Modality.

Deploy

1. Deploy the ‘GA’ (for customers ONLY) or ‘Mod’ (for Modality ONLY) version ARM template for the C&M Automation Notification Service from the ARM list here.
2. Select the Resource Group you want to deploy into (e.g. twa-perf-customername)
3. Scenario Name: Type a scenario name which is most relevant to your notification. Select your desired trigger criteria & schedule
4. Tenant ID: Input the your own Azure Tenant ID
5. Service Bus Connection String: Modality will provide the current connection string for the automation service.
6. SQL Connection String: Located in the Calls & Meetings Azure SQL Database. Copy the ADO.NET string & replace the password with the your database password and put this into the field for this section like below.
   
   
   
7. Bot Preshared Key: Modality will provide the current pre-shared key to use.
8. Leave the rest of the ARM fields as default & deploy.

Scenario Template Creation

The template is stored in the Modality tenant and Modality will set up this part for you.

SQL Database Configuration

Now to configure the SQL side to tie in the storage account data to the SQL database.

1. Connect to Calls & Meetings SQL Database via SQL Server Management Studio on your desktop.
2. Right click on the TeamsDiags-Ga > Select New Query & Paste in your ‘Stored Procedure’ SQL query for the specified scenario (example Built in Device Teams Reminder – Calls and Meetings Automation (mdalitysystems.com) )
3. Expand TeamsDiags-ga, Tables area & right click on automation.scenarios > Edit top 200 rows
4. Enter a new row of details for the new scenario:
   1. Name – This must match the scenario name used in both the ARM deployment name & from the storage account
   2. StoredProcedureName – this must match the stored procedure name within SQL DB > Programmability > Stored Procedures
   3. IsSentOnce – False usually, unless the alert is a onetime message only