Merge pull request #101617 from robinsh/robinsh-0117

Rename TLS files and add redirects for them.

Author: megvanhuygen

.openpublishing.redirection.json

@@ -1746,6 +1746,16 @@
       "redirect_url": "/azure/iot-hub/iot-hub-create-using-cli",
       "redirect_document_id": true
     },
+    {
+      "source_path": "articles/iot-hub/iot-hub-tls.md",
+      "redirect_url": "/azure/iot-hub/iot-hub-tls-support",
+      "redirect_document_id": true
+    },
+    {
+      "source_path": "articles/iot-hub/tls-1.2-everywhere.md",
+      "redirect_url": "/azure/iot-hub/iot-hub-tls-deprecating-1-0-and-1-1",
+      "redirect_document_id": true
+    },
     {
       "source_path": "articles/cognitive-services/custom-decision-service/custom-decision-service-tutorial-analytics.md",
       "redirect_url": "/azure/cognitive-services/custom-decision-service",

articles/iot-hub/TOC.yml

@@ -84,9 +84,9 @@
 - name: Concepts
   items:
     - name: TLS support
-      href: iot-hub-tls.md
+      href: iot-hub-tls-support.md
     - name: TLS 1.0 and 1.1 deprecation
-      href: tls-1.2-everywhere.md
+      href: iot-hub-tls-deprecating-1-0-and-1-1.md
     - name: Message enrichments overview
       href: iot-hub-message-enrichments-overview.md
     - name: Overview of device management

articles/iot-hub/tls-1.2-everywhere.md renamed to articles/iot-hub/iot-hub-tls-deprecating-1-0-and-1-1.md

@@ -1,15 +1,15 @@
 ---
-title: Deprecation TLS 1.0 and 1.1 in IoT Hub and Device Provisioning Service (DPS) | Microsoft Docs
+title: Deprecating TLS 1.0 and 1.1 in IoT Hub and Device Provisioning Service (DPS) | Microsoft Docs
 description: Guidelines regarding deprecation of TLS 1.0 and 1.1 and supported ciphers in IoT Hub and DPS.
-author: rezas
-ms.author: reza
+author: rezasherafat
+ms.author: rezas
 ms.service: iot-hub
 services: iot-hub
 ms.topic: conceptual
 ms.date: 12/16/2019
 ---
 
-# TLS 1.0 and 1.1 deprecation in IoT Hub and Device Provisioning Service
+# Deprecation of TLS 1.0 and 1.1 in IoT Hub and Device Provisioning Service
 
 To provide best-in-class encryption, IoT Hub and Device Provisioning Service (DPS) are moving to Transport Layer Security (TLS) 1.2 as the encryption mechanism of choice for IoT devices and services. As such, legacy support for TLS 1.0 and TLS 1.1 as well as several non-recommended legacy ciphers will be deprecated in **July 1, 2020**.
 
@@ -20,7 +20,7 @@ Based on customers' specific circumstances and configurations, deprecation of TL
 
 ## Supported ciphers
 
-Only the following ciphers will be allowed during TLS handshake:
+Only the following ciphers are allowed during TLS handshake:
 
 * TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
 * TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384

articles/iot-hub/iot-hub-tls.md renamed to articles/iot-hub/iot-hub-tls-support.md

@@ -7,19 +7,17 @@
  ms.topic: conceptual
  ms.date: 01/10/2020
  ms.author: rezas
- ms.custom: Azure IoT Hub TLS
 ---
 
 # TLS support in IoT Hub
 
 IoT Hub uses Transport Layer Security (TLS) to secure connections from IoT devices and services. Three versions of the TLS protocol are currently supported, namely versions 1.0, 1.1, and 1.2.
 
-TLS 1.0 and 1.1 are considered legacy and are [planned for deprecation](./tls-1.2-everywhere.md). It is therefore strongly recommended to use TLS 1.2 as the preferred TLS version when connecting to IoT Hub.
-
+TLS 1.0 and 1.1 are considered legacy and are planned for deprecation. For more information, see [Deprecating TLS 1.0 and 1.1 for IoT Hub](iot-hub-tls-deprecating-1-0-and-1-1.md). It is strongly recommended that you use TLS 1.2 as the preferred TLS version when connecting to IoT Hub.
 
 ## Restrict connections to TLS 1.2 in your IoT Hub resource
 
-For added security, it is advised to configure your IoT Hubs to _only_ allow client connections that use TLS version 1.2 and to enforce the use of [recommended ciphers](#recommended-ciphers).
+For added security, it is advised to configure your IoT Hubs to *only* allow client connections that use TLS version 1.2 and to enforce the use of [recommended ciphers](#recommended-ciphers).
 
 For this purpose, provision a new IoT Hub in any of the [supported regions](#supported-regions) and set the `minTlsVersion` property to `1.2` in your Azure Resource Manager template's IoT hub resource specification:
 
@@ -48,8 +46,8 @@ For this purpose, provision a new IoT Hub in any of the [supported regions](#sup
 
 The created IoT Hub resource using this configuration will refuse device and service clients that attempt to connect using TLS versions 1.0 and 1.1. Similarly, the TLS handshake will be refused if the client HELLO message does not list any of the [recommended ciphers](#recommended-ciphers).
 
-Note that the `minTlsVersion` property is read-only and cannot be changed once your IoT Hub resource is created. It is therefore essential that you properly test and validate that _all_ your IoT devices and services are compatible with TLS 1.2 and the [recommended ciphers](#recommended-ciphers) in advance.
-
+> [!NOTE]
+> The `minTlsVersion` property is read-only and cannot be changed once your IoT Hub resource is created. It is therefore essential that you properly test and validate that *all* your IoT devices and services are compatible with TLS 1.2 and the [recommended ciphers](#recommended-ciphers) in advance.
 
 ### Supported regions
 
@@ -62,8 +60,6 @@ IoT Hubs that require the use of TLS 1.2 can be created in the following regions
 > [!NOTE]
 > Upon failovers, the `minTlsVersion` property of your IoT Hub will remain effective in the geo-paired region post-failover.
 
-
-
 ### Recommended ciphers
 
 IoT Hubs that are configured to accept only TLS 1.2 will also enforce the use of the following recommended ciphers:
@@ -73,7 +69,6 @@ IoT Hubs that are configured to accept only TLS 1.2 will also enforce the use of
 * `TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256`
 * `TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384`
 
-
 ### Use TLS 1.2 in your IoT Hub SDKs
 
 Use the links below to configure TLS 1.2 and allowed ciphers in IoT Hub client SDKs.

includes/iot-secure-your-deployment.md

@@ -72,7 +72,7 @@ While establishing a secure TLS connection with IoT Hub, the IoT device authenti
 
 ## Securing the connection
 
-Internet connection between the IoT device and IoT Hub is secured using the Transport Layer Security (TLS) standard. Azure IoT supports [TLS 1.2](https://tools.ietf.org/html/rfc5246), TLS 1.1, and TLS 1.0, in this order. Support for TLS 1.0 is provided for backward compatibility only. If possible, [configure your hub](../articles/iot-hub/iot-hub-tls.md) to use TLS 1.2 as it provides the most security.
+Internet connection between the IoT device and IoT Hub is secured using the Transport Layer Security (TLS) standard. Azure IoT supports [TLS 1.2](https://tools.ietf.org/html/rfc5246), TLS 1.1, and TLS 1.0, in this order. Support for TLS 1.0 is provided for backward compatibility only. Check [TLS support in IoT Hub](../articles/iot-hub/iot-hub-tls-support.md) to see how to configure your hub to use TLS 1.2, as it provides the most security.
 
 ## Securing the cloud