Microsoft
MicrosoftHi rajanpatel,
The flow you're referring to is how IoT Hub authenticates devices; there are 3 methods - Symmetric Key, X.509 self signed, and X.509 CA. These flows are not impacted. The TLS Server Certificates of Hub and DPS are changing and hence impacted. This means that when establishing a TLS connection with the IoT Hub or global DPS endpoint, the device must validate the server by looking up at the root chain and validating that the root certificate (in this case 'Baltimore Cyber Trust Root') is indeed a trusted CA on the device.
The error you are receiving is because the test DPS instance does not have your device enrolled. If you'd like to test that, please open a support ticket as described in the Support section above, and our support team will be happy to enroll your device and allow you to perform an end to end test. If you're able to independently test that you're able to establish a TLS connection using wireshark then that's the only validation required. Hope this helps! 🙂