Explanation:
Box 1: Marked
Query parameter
* profanityAction
Optional parameter.
Specifies how profanities should be treated in translations. Possible values are: NoAction (default), Marked, or Deleted.
Box 2: Tag
* profanityMarker
Optional parameter.
Specifies how profanities should be marked in translations. Possible values are: Asterisk (default) or Tag.
Note: Handle profanity
Normally, the Translator service retains profanity that is present in the source in the translation.
The degree of profanity and the context that makes words profane differ between cultures, and as a result the degree of profanity in the target language can be amplified or reduced.
Reference:
https://learn.microsoft.com/en-us/azure/ai-services/translator/reference/v3-0-translate

Bot Framework Emulator is a desktop application that allows bot developers to test and debug bots, either locally or remotely.
ngrok is a cross-platform application that "allows you to expose a web server running on your local machine to the internet." Essentially, what we'll be doing is using ngrok to forward messages from external channels on the web directly to our local machine to allow debugging, as opposed to the standard messaging endpoint configured in the Azure portal.
Reference:
https://docs.microsoft.com/en-us/azure/bot-service/bot-service-debug-emulator

Step 1: Clone a version
1. Select the version you want to clone (1u12345678) then select Clone from the toolbar.
2. In the Clone version dialog box, type a name for the new version. Type 1.0

Step 2: Set active version
Select a version from the list, then select Activate from the toolbar.
Reference:
https://docs.microsoft.com/en-us/azure/cognitive-services/luis/luis-how-to-manage-versions

Customer-managed keys require an additional billable service, Azure Key Vault, which can be in a different region, but under the same subscription, as Azure AI Search. Enabling CMK encryption will increase index size and degrade query performance. Based on observations to date, you can expect to see an increase of 30%-60% in query times, although actual performance will vary depending on the index definition and types of queries. Because of this performance impact, we recommend that you only enable this feature on indexes that really require it.
Reference:
https://docs.microsoft.com/en-us/azure/search/search-security-overview#data-protection
https://docs.microsoft.com/en-us/azure/search/search-security-overview#customer-managed- keys-cmk