Merge pull request #90915 from ecfan/tls

Add Transport Layer Security version info

Author: PRMerger20

articles/connectors/connectors-native-reqres.md

@@ -9,8 +9,8 @@ ms.author: estfan
 ms.reviewers: klam, LADocs
 manager: carmonm
 ms.assetid: 566924a4-0988-4d86-9ecd-ad22507858c0
-ms.topic: article
-ms.date: 09/06/2019
+ms.topic: conceptual
+ms.date: 10/11/2019
 tags: connectors
 ---
 
@@ -22,7 +22,9 @@ With [Azure Logic Apps](../logic-apps/logic-apps-overview.md) and the built-in R
 * Trigger a workflow when an external webhook event happens.
 * Receive and respond to an HTTPS call from another logic app.
 
-The Request trigger supports *only* HTTPS. To make outgoing HTTP or HTTPS calls instead, use the built-in [HTTP trigger or action](../connectors/connectors-native-http.md).
+> [!NOTE]
+> The Request trigger supports *only* Transport Layer Security (TLS) 1.2 for incoming calls. Outgoing calls 
+> continue to support TLS 1.0, 1.1, and 1.2. If you see SSL handshake errors, make sure that you use TLS 1.2.
 
 ## Prerequisites
 

articles/connectors/connectors-native-webhook.md

@@ -1,18 +1,18 @@
 ---
-title: Create event-based tasks and workflows in Azure Logic Apps
-description: Trigger, pause, and resume automated tasks, processes, and workflows based on events that happen at an endpoint by using Azure Logic Apps
+title: Wait and respond to events - Azure Logic Apps
+description: Automate workflows that trigger, pause, and resume based on events at a service endpoint by using Azure Logic Apps
 services: logic-apps
 ms.service: logic-apps
 ms.suite: integration
 author: ecfan
 ms.author: estfan
 ms.reviewer: klam, LADocs
 ms.topic: conceptual
-ms.date: 07/05/2019
+ms.date: 10/10/2019
 tags: connectors
 ---
 
-# Automate event-based tasks and workflows by using HTTP webhooks in Azure Logic Apps
+# Create and run automated event-based workflows by using HTTP webhooks in Azure Logic Apps
 
 With [Azure Logic Apps](../logic-apps/logic-apps-overview.md) and the built-in HTTP Webhook connector, you can automate workflows that wait and run based on specific events that happen at an HTTP or HTTPS endpoint by building logic apps. For example, you can create a logic app that monitors a service endpoint by waiting for a specific event before triggering the workflow and running the specified actions, rather than regularly checking or *polling* that endpoint.
 
@@ -33,6 +33,11 @@ An HTTP webhook action is also event-based and *subscribes* to a specific servic
 
 For example, the Office 365 Outlook connector's [**Send approval email**](connectors-create-api-office365-outlook.md) action is an example of webhook action that follows this pattern. You can extend this pattern into any service by using the webhook action.
 
+> [!NOTE]
+> Logic Apps enforces Transport Layer Security (TLS) 1.2 when 
+> receiving the call back to the HTTP webhook trigger or action. 
+> If you see SSL handshake errors, make sure that you use TLS 1.2.
+
 For more information, see these topics:
 
 * [HTTP Webhook trigger parameters](../logic-apps/logic-apps-workflow-actions-triggers.md#http-webhook-trigger)

articles/logic-apps/logic-apps-securing-a-logic-app.md

@@ -181,7 +181,7 @@ To prevent others from changing or deleting your logic app, you can use [Azure R
 
 ## Access to run history data
 
-During a logic app run, all the data is encrypted during transit by using [Transit Layer Security (TLS)](https://azure.microsoft.com/updates/app-service-and-functions-hosted-apps-can-now-update-tls-versions/) and at [rest](../security/fundamentals/encryption-atrest.md). When your logic app finishes running, you can view the history for that run, including the steps that ran along with the status, duration, inputs, and outputs for each action. This rich detail provides insight into how your logic app ran and where you might start troubleshooting any problems that arise.
+During a logic app run, all the data is encrypted during transit by using [Transport Layer Security (TLS)](https://azure.microsoft.com/updates/app-service-and-functions-hosted-apps-can-now-update-tls-versions/) and at [rest](../security/fundamentals/encryption-atrest.md). When your logic app finishes running, you can view the history for that run, including the steps that ran along with the status, duration, inputs, and outputs for each action. This rich detail provides insight into how your logic app ran and where you might start troubleshooting any problems that arise.
 
 When you access your logic app's run history, Logic Apps authenticates your access and provides links to the inputs and outputs from the requests and responses in your logic app's run. However, for actions that handle any passwords, secrets, keys, or other sensitive information, you want to prevent others from viewing and accessing that data. For example, if your logic app gets a secret from [Azure Key Vault](../key-vault/key-vault-overview.md) to use when authenticating an HTTP action, you want to hide that secret from view.