Skip to content

Commit 9032c93

Browse files
authored
IoT Hub - Update certificate management overview date and fix duplicate
Updated the date for the certificate management overview and removed duplicate policy revocation entry.
1 parent 3a3003d commit 9032c93

1 file changed

Lines changed: 1 addition & 2 deletions

File tree

articles/iot-hub/iot-hub-certificate-management-overview.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ ms.author: cwatson
77
ms.service: azure-iot-hub
88
services: iot-hub
99
ms.topic: overview
10-
ms.date: 03/16/2026
10+
ms.date: 04/15/2026
1111
ai-usage: ai-assisted
1212
#Customer intent: As a developer new to IoT, I want to understand what certificate management is and how it can help me manage my IoT device certificates.
1313
---
@@ -36,7 +36,6 @@ The following features are supported with certificate management for IoT Hub dev
3636
| At-scale provisioning of device certificates | Use policies you define in your ADR namespace to link directly to Device Provisioning Service enrollments to enable certificate provisioning. |
3737
| Device certificate revocation | Revoke individual device certificates to block device connections until a new certificate is issued to the device. Revoked certificates are added to the parent CA's Certificate Revocation List (CRL). |
3838
| Policy revocation | Revoke a policy to remove the CA certificate from IoT Hub and block any devices using certificates issued by that policy. Once revoked, a new CA certificate is created for that policy and synchronized with IoT Hub. |
39-
| Policy revocation | Revoke a policy to remove the CA certificate from IoT Hub and block any devices using certificates issued by that policy. Once revoked, a new CA certificate is created for that policy and synchronized with IoT Hub. |
4039
| Sync CA certificates with IoT Hubs | Sync the CA certificate managed by your policy to the IoT Hubs linked to your namespace. This allows IoT Hub to trust device certificates that have been signed by one of your issuing CAs.|
4140

4241
## Onboarding vs. operational credentials

0 commit comments

Comments
 (0)