Merge pull request #314785 from cwatson-cat/patch-74

IoT Hub - Update certificate management overview date and fix duplicate

Author: prmerger-automator[bot]

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

@@ -7,7 +7,7 @@ ms.author: cwatson
 ms.service: azure-iot-hub
 services: iot-hub
 ms.topic: overview
-ms.date: 03/16/2026
+ms.date: 04/15/2026
 ai-usage: ai-assisted
 #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.
 ---
@@ -36,7 +36,6 @@ The following features are supported with certificate management for IoT Hub dev
 | 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. |
 | 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). |
 | 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. |
-| 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. |
 | 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.|
 
 ## Onboarding vs. operational credentials