Skip to content

Commit 9060cee

Browse files
Merge pull request #297213 from SoniaLopezBravo/add-note-iotTLS
Update note in IoT Hub TLS support
2 parents e0f4e41 + c6161e1 commit 9060cee

File tree

1 file changed

+13
-3
lines changed

1 file changed

+13
-3
lines changed

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

Lines changed: 13 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -4,8 +4,8 @@
44
services: iot-hub
55
author: SoniaLopezBravo
66
ms.service: azure-iot-hub
7-
ms.topic: conceptual
8-
ms.date: 02/24/2025
7+
ms.topic: how-to
8+
ms.date: 03/24/2025
99
ms.author: sonialopez
1010
---
1111

@@ -16,7 +16,17 @@ IoT Hub uses Transport Layer Security (TLS) to secure connections from IoT devic
1616
> [!NOTE]
1717
> Azure IoT Hub will end support for TLS 1.0 and 1.1 in alignment with the Azure wide service announcement for [TLS 1.0 and 1.1 retirement](https://azure.microsoft.com/updates?id=update-retirement-tls1-0-tls1-1-versions-azure-services) on **August 31, 2025**.
1818
>
19-
> It's 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](#cipher-suites) in advance. It's highly recommended to use the [minimum TLS enforcement feature](#enforce-iot-hub-to-use-tls-12-and-strong-cipher-suites) as the mechanism for testing and compliance
19+
> It's 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](#cipher-suites) in advance. It's highly recommended to use the [minimum TLS enforcement feature](#enforce-iot-hub-to-use-tls-12-and-strong-cipher-suites) as the mechanism for testing and compliance.
20+
>
21+
> It’s important to distinguish between **TLS 1.2 support** and **TLS 1.2 enforcement**. TLS 1.2 is supported on all IoT Hubs, meaning that IoT Hubs can handle connections using the TLS 1.2 protocol. On the other hand, TLS 1.2 enforcement ensures that IoT Hub **only** accepts connections using TLS 1.2 or higher. When TLS 1.2 enforcement is enabled, the service also enforces the use of [strong cipher suites](#cipher-suites) as described above. Future updates will allow for the enforcement of TLS 1.2 while permitting non-recommended cipher suites.
22+
>
23+
> Currently, TLS 1.2 enforcement is supported only in select regions:
24+
>
25+
> - East US
26+
> - South Central US
27+
> - West US 2
28+
> - US Gov Arizona
29+
> - US Gov Virginia (Note: TLS 1.0/1.1 support isn't available in this region. TLS 1.2 enforcement must be enabled, or IoT Hub creation will fail).
2030
>
2131
> To find out the version of TLS your IoT Hub devices are running, refer to [TLS 1.0 and 1.1 end of support guide](#checking-tls-versions-for-iot-hub-devices).
2232

0 commit comments

Comments
 (0)