Emulator - add support for app insights service configuration

[vishwacsena]

Bot file supports keeping track of app insights service configuration.

Emulator does not provide any affordance at all to manage this today (both through the azure login flow as well as through manual mode).

Filing this ticket to track the work for emulator to support app insights service configuration.

[mewa1024]

@vishwacsena
Can you confirm that this is the right flow? Using the QnA Maker/LUIS/Dispatch flow as a model:

Modals for adding a Service X when:
(A) user has signed into Azure, and user has a Service X service - user picks from a list
(C) user has not signed into Azure - gets modal to sign in or connect manually
(D) user adds app by entering required fields - modal with fields to enter manually

And these are the fields required (according to the doc for msbot connect appinsights):

• Name (defaults to serviceName)
• Azure Tenant id (either GUID or xxx.onmicrosoft.com)
• Azure Subscription Id
• Azure resource group name
• Azure service name
• App Insights Instrumentation Key
• (OPTIONAL) App Insights Application Id

Comps of the modals are here:
https://microsoft-fuse-design.invisionapp.com/d/#/projects/prototypes/14863139 (look in App Insights section)

Other questions:

• the LUIS, QnA, and Dispatch flows had links to create those services and learn more. Do we want to do the same for App Insights and storage? Might be necessary for Azure resources that are not specifically bot-related.
• Also, Azure App Insights is being rebranded as Azure Monitor. Do we care? https://docs.microsoft.com/en-us/azure/azure-monitor/azure-monitor-rebrand

This is the order for the Add menu:

(Adding the word "Add" in front of all the service names because participants in the user study mistakenly thought that clicking on the service name navigated to the service.)

[vishwacsena]

@mewa1024 - this is great and yes following along the patterns established by the current flows for LUIS, QnA and dispatch is the right model for other service types. Yes, we should have pointers to doc pages for the respective services. We can have it be application insights for now and update the copy later if needed.

[mewa1024]

@vishwacsena Cool. Assigning to Justin. @justinwilaby Designs are on Invision. The links are not ready yet, and I will set up aka links next week.

[mewa1024]

@justinwilaby I updated the designs with the links:
Link: https://aka.ms/bot-framework-emulator-create-appinsights
Link: https://aka.ms/bot-framework-emulator-appinsights-docs
Link: https://aka.ms/bot-framework-emulator-appinsights-keys

Updates to the designs are on Invision and also copied below:

[mewa1024]

@justinwilaby I have found a few typos in the comps and just corrected them. Sorry about this:

• changed the wording in the Azure picker modal from "Select a resource below to your resource's information in your bot file or connect to an Application Insights resource manually" to "Select a resource below or connect to an Application Insights resource manually."

• changed the wording in the Azure picker modal from "Create a new Application Insights service." to "Create a new Application Insights resource."

• changed the wording in the not-signed-in-yet modal from "Alternatively, you can connect to an Azure Application Insights resource manually with the app ID, version, and authoring key" to "Alternatively, you can connect to an Azure Application Insights resource manually. "

[mewa1024]

@justinwilaby similar issues as #934.
In the link to the Azure portal,

• please exclude the word "the" from the link.
• Please remove the words "App Insights " altogether, so the text should be "the Azure portal." with "Azure portal" as the linked text.
• Please add a period to the end of the sentence

Please use semibold for all the links (the accessibility people require a font weight change for links in text, so this should be the style throughout the Emulator.

Also, the deep link to App Insights is not working.

[mewa1024]

@justinwilaby One more thing, the modal is looking for "Azure Subscription Key" instead of "Azure Subscription ID". This means the modal is showing the field as blank, even though the .bot file has an entry for "subscriptionId":

[tonyanziano]

Addressed in #1160