Hello Noel,
Welcome to Microsoft Q&A!
We are very sorry for the delay in giving you a response to your topic in this forum. If you still have the same problem, it sounds like you're experiencing a significant issue with your Azure IoT Hub setup. There have been some recent updates and changes related to X.509 certificate attestation in the Device Provisioning Service (DPS) that might be affecting your devices.
- TLS Certificate Changes: Azure IoT Hub and DPS endpoints have undergone updates to their TLS certificates, which could impact device connectivity if the devices do not have the updated root certificates in their trusted certificate store.
- X.509 Certificate Chain: The documentation on X.509 certificate attestation has been updated to emphasize the importance of the certificate chain of trust. This includes ensuring that all intermediate and root certificates are correctly configured and trusted by your devices.
- Authentication and Authorization: There have been clarifications on the use of X.509 certificates for authentication (AuthN) and the distinction from authorization (AuthZ). This might require reviewing your device configurations to ensure they align with the updated guidelines.
Given these changes, I recommend checking the following:
- Ensure your devices have the latest root certificates required by Azure IoT Hub and DPS.
- Verify the entire certificate chain is correctly configured and trusted by your devices.
- Review the updated documentation on X.509 certificate attestation to ensure your setup complies with the latest guidelines.
Additionally, please kindly note that if we do not receive a response to this thread within 4 business days, we will consider it closed. In case you have the same question, and the information provided was not useful, feel free to create another thread and we will be more than happy to help you.
Regards,
Gao
If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".