Merge pull request #110208 from TimShererWithAquent/us1679050di

Change SSL to TLS per 1679050

Author: PRMerger16

articles/connectors/connectors-create-api-ftp.md

@@ -22,7 +22,7 @@ You can use triggers that get responses from your FTP server and make the output
 
 ## Limitations
 
-* The FTP connector supports only explicit FTP over SSL (FTPS) and isn't compatible with implicit FTPS.
+* The FTP connector supports only explicit FTP over TLS/SSL (FTPS) and isn't compatible with implicit FTPS.
 
 * By default, FTP actions can read or write files that are *50 MB or smaller*. To handle files larger than 50 MB, FTP actions support [message chunking](../logic-apps/logic-apps-handle-large-messages.md). The **Get file content** action implicitly uses chunking.
 

articles/connectors/connectors-create-api-smtp.md

@@ -70,7 +70,7 @@ Under the actions list, select the action you want.
    | **User Name** | Yes | Your username for your SMTP account | 
    | **Password** | Yes | Your password for your SMTP account | 
    | **SMTP Server Port** | No | A specific port on your SMTP server you want to use | 
-   | **Enable SSL?** | No | Turn on or turn off SSL encryption. | 
+   | **Enable SSL?** | No | Turn on or turn off TLS/SSL encryption. | 
    |||| 
 
 1. Provide the necessary details for your selected action. 

articles/connectors/connectors-native-reqres.md

@@ -21,7 +21,7 @@ With [Azure Logic Apps](../logic-apps/logic-apps-overview.md) and the built-in R
 > 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. For more information, see [Solving the TLS 1.0 problem](https://docs.microsoft.com/security/solving-tls1-problem).
 >
-> If you see SSL handshake errors, make sure that you use TLS 1.2. For incoming calls, here are the supported cipher suites:
+> If you see TLS handshake errors, make sure that you use TLS 1.2. For incoming calls, here are the supported cipher suites:
 >
 > * TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384
 > * TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256

articles/connectors/connectors-native-webhook.md

@@ -33,7 +33,7 @@ For example, the Office 365 Outlook connector's [**Send approval email**](connec
 > [!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. 
+> If you see TLS handshake errors, make sure that you use TLS 1.2. 
 > For incoming calls, here are the supported cipher suites:
 >
 > * TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384

articles/logic-apps/logic-apps-custom-api-authentication.md

@@ -305,7 +305,7 @@ In the **Authorization** section, include these properties:
 
 | Property | Required | Description |
 | -------- | -------- | ----------- |
-| `type` | Yes | The authentication type. For SSL client certificates, the value must be `ClientCertificate`. |
+| `type` | Yes | The authentication type. For TLS/SSL client certificates, the value must be `ClientCertificate`. |
 | `password` | No | The password for accessing the client certificate (PFX file) |
 | `pfx` | Yes | The base64-encoded contents of the client certificate (PFX file) |
 ||||

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

@@ -22,7 +22,7 @@ To control access and protect data in Azure Logic Apps, you can set up security
 
 ## Access to request-based triggers
 
-If your logic app uses a request-based trigger, which receives incoming calls or requests, such as the [Request](../connectors/connectors-native-reqres.md) or [Webhook](../connectors/connectors-native-webhook.md) trigger, you can limit access so that only authorized clients can call your logic app. All requests received by a logic app are encrypted and secured with Secure Sockets Layer (SSL) protocol.
+If your logic app uses a request-based trigger, which receives incoming calls or requests, such as the [Request](../connectors/connectors-native-reqres.md) or [Webhook](../connectors/connectors-native-webhook.md) trigger, you can limit access so that only authorized clients can call your logic app. All requests received by a logic app are encrypted and secured with Transport Layer Security (TLS), previously known as Secure Sockets Layer (SSL), protocol.
 
 Here are options that can help you secure access to this trigger type:
 
@@ -659,7 +659,7 @@ If the [Client Certificate](../active-directory/authentication/active-directory-
 
 | Property (designer) | Property (JSON) | Required | Value | Description |
 |---------------------|-----------------|----------|-------|-------------|
-| **Authentication** | `type` | Yes | **Client Certificate** <br>or <br>`ClientCertificate` | The authentication type to use for Secure Sockets Layer (SSL) client certificates. While self-signed certificates are supported, self-signed certificates for SSL aren't supported. |
+| **Authentication** | `type` | Yes | **Client Certificate** <br>or <br>`ClientCertificate` | The authentication type to use for TLS/SSL client certificates. While self-signed certificates are supported, self-signed certificates for TLS/SSL aren't supported. |
 | **Pfx** | `pfx` | Yes | <*encoded-pfx-file-content*> | The base64-encoded content from a Personal Information Exchange (PFX) file <p><p>To convert the PFX file into base64-encoded format, you can use PowerShell by following these steps: <p>1. Save the certificate content into a variable: <p>   `$pfx_cert = get-content 'c:\certificate.pfx' -Encoding Byte` <p>2. Convert the certificate content by using the `ToBase64String()` function and save that content to a text file: <p>   `[System.Convert]::ToBase64String($pfx_cert) | Out-File 'pfx-encoded-bytes.txt'` |
 | **Password** | `password`| No | <*password-for-pfx-file*> | The password for accessing the PFX file |
 |||||
@@ -688,7 +688,7 @@ For more information about securing services by using client certificate authent
 * [Improve security for back-end services by using client certificate authentication in Azure API Management](../api-management/api-management-howto-mutual-certificates.md)
 * [Improve security for your RESTfuL service by using client certificates](../active-directory-b2c/secure-rest-api.md)
 * [Certificate credentials for application authentication](../active-directory/develop/active-directory-certificate-credentials.md)
-* [Use an SSL certificate in your application code in Azure App Service](../app-service/configure-ssl-certificate-in-code.md)
+* [Use a TLS/SSL certificate in your code in Azure App Service](../app-service/configure-ssl-certificate-in-code.md)
 
 <a name="azure-active-directory-oauth-authentication"></a>