Thank you for your feedback! We’ve started the work to enable Consumption Plan in China North 2. Please expect the next update by August.
Thanks for the feedback! We are interested in collecting feedback on this request – please vote for it if this is something you like to see.
We’re also interested in learning more what people want to use the SFTP/FTPS for and which protocol they prefer. Please feel free to leave us a comment letting us know more detail!
Program Manager, Azure Files
Thank you for your feedback. While it is unlikely we’ll address this suggestion in the near future, we’ll reassess based on the number of votes it receives.
Azure Search Product Team
Due to various technical limitations, the first iteration of the customer-owned domains functionality will not be available for a few more months. We will provide an update as soon as we can get a more specific ETA.
As a workaround, the IoT Hub IP address can be discovered by using a reverse DNS lookup on the cname (*.azure-devices.net). However, the IP mapped is subject to change without notice. This also doesn’t help discover the geo-paired Hub IP address, that would be needed in case of a failover/disaster recovery.
Something we’re considering is to add a new API which would return the current IP address for an IoT Hub + the geo-paired IP address. This API could be queried frequently to keep firewall rules up-to-date. Please comment and vote on the potential usefulness of this proposed feature.
This request is for custom domain and custom SSL certificate support for the IoT Hub endpoint. This work is currently unplanned for IoT Hub but we’re listing to customer requests and may chose to support this in the future.
If you have interest in have a deterministic way of understanding your IoT Hub IP address (and corresponding geo-pair IP address) in order to keep firewall rules up-to-date, see and vote on this request: https://feedback.azure.com/forums/321918-azure-iot/suggestions/15714243-iot-hub-network-address instead.