Este explorador ya no se admite.
Actualice a Microsoft Edge para aprovechar las características y actualizaciones de seguridad más recientes, y disponer de soporte técnico.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(182.40000000000003, 40%, 27%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EN%3C/text%3E%3C/svg%3E)
Hi,
I have several devices that were successfully reporting to an instance of Azure IoT Hub. They are provisioned using X.509 certificate attestation in the Device Provisioning Service (DPS).
A few days ago, the IoT Hub stopped receiving messages from the devices, and at the same time, the number of attestation attempts in the DPS scaled from being 0 for almost all of the time, to being constantly non-zero:
I have also observed that the documentation on X.509 certificate attestation was updated recently. I want to ask: has anything changed in the DPS attestation chain that could have impacted my architecture?
Thank you very much in advance.
