Add the custom domain name support for IoTHub Endpoint
More and more company care about their Brand and specially over the Internet exposure. (for many reason: Marketing, Security (PKI),...).
It could be great to have the ability to use Custom Domain name for the IotHub Endpoint.
Hi, we are currently reviewing this feature for implementation.
Andre Podnozov commented
This may be a good time to re-consider this suggestion, especially in light of recent PKI events that underscore the need for IoT solution developers to have better control of their endpoint security -- https://techcommunity.microsoft.com/t5/internet-of-things/azure-iot-tls-changes-are-coming-and-why-you-should-care/ba-p/1658456
Denis Oliana commented
any news here?
+1 vote for custom domain and certificate support
Definetely I vote for this as I would like to define a short filtering list like
which would cover trust for REST interfaces to IOThub and DPS
Denis Oliana commented
This would be a great feature - also in regard to being more flexible. Imagine the scenario where an IoT-Hub gets deleted (by accident, or on purpose because of some reconfiguration) and it has to be made sure, that the same DNS can be regained for the devices to be able to communicate. BTW: the same goes for the DPS.
Briton Zurcher [MSFT] commented
Some of these comments indicate requests for ways to undertsand the IoT Hub IP address to keep firewall rules up-to-date (rather than having a custom domain/ssl certificate). If this is what you're after, please use this request for voting/comments:
Any updates on this yet? There are people who are facing issues in production because changes in iothub endpoints are affecting firewall rules thereby preventing devices from connecting to the IoTHub
Omri Cohen commented
Veit Sanner commented
It would be really helpful to have the options to use a custom domain. Otherwise there is the issue that thousands of devices would have to be reconfigured because of a change of the IoT hub's hostname. With a custom domain name, only the DNS entry would have to be updated.
The instructions to use a CNAME do not work because the provided SSL certificate is not valid for a custom domain.
No response from Microsoft after 5 months.
The comments about using CNAME records do not work as there is SSL involved.
Robin Jones commented
Wouldn't a cname record be a sufficient workaround?