Industry sector (with integrated IIOT) will certainly appreciate Azure Stack - power of Azure in own Datacenter.117 votes
many client is asking to have Azure PaaS services avail not on public endpoints but only via internal vnet connected to client side services via server to server VPN.
this request come especially for:
- iot hub
- event hub
- sql database
We are reviewing this request
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.69 votes
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.
I want to allow each tenant to connect directly to IoT hub (as service) to communicate with devices. Of course I would want each tenant to have access only to their own devices and not have the possibility to connect to devices from other tenants (thus I require the proper SAS).Following the documentation on the ServiceConnect permissions, it would seem that it is not possible to do this restriction on a SAS level.66 votes
Supporting formats such as Protobuf and/or compressing in DeviceClient.SendEventBatchAsync35 votes
This is not in our plans for now but definitively an interesting scenario.
As of today you can already do so in different ways such as compressing data in your device code before sending and using an Azure Function on the back end that will be triggered each time a compressed message arrives. Not totally integrated into IoT Hub but gives you the choice of the compression format and flexibility in routing messages before decompressing content (using message headers for routing).
Similar to Amazon's Amazon IoT Button found here: https://aws.amazon.com/iot/button/
This would be an interesting way to quickly get simple hardware buttons that execute functions in Azure and could be managed via the Azure IoT system.
Just make sure the batter lasts longer than Amazon's limited 1000 button presses...34 votes
As mentioned by Ilias in the thread, our approach has been to work with partners to offer several starter kits (https://aka.ms/azureiotstarterkits) that can be used to implement this type of solutions, giving more choice.
The MXChip devkit (https://aka.ms/azureiotdevkit) is a great option and gives you exactly what the AWS button does, plus other features (microphone, several buttons, an OLED screen, several sensors…). Samples on the kit’s page show how simple patterns can be implemented and come with code samples.
I would like to have auto-scaling option.
Or API to scale instances so I can script the auto-scaling.32 votes
HTTP/2 is a lot more performant than HTTP/1. HTTP/2 is in the Proposed Standard phase of the standardization process, so it's time to get on implementing support for it in IoT Hub!29 votes
Bring Azure IoT Hub to AzureStack28 votes
Iot hub should be able to log upload requests, not only upload notifications from the device.
At the moment a production team is not able to check if a device has tried to upload a blob.26 votes
It'd be interesting to be able to leverage the same mechanism as IoT Hub File Upload to Download files from blob storage to a device25 votes
The device twins could support array types for tags.23 votes
Please include "Stop" as a feature of any service that "runs." You can stop a VM, App Services and Stream Analytics jobs. Why not a SQL Database, DocumentDB, IoT Hub, EventHub, etc? Heck, should be able to Stop a Resource Group, which obviously would stop every service within.23 votes
Consider a pricing model that bills based om the number of messages instead of a tier model with a fixed number per day. This is much more flexible when dealing with spiky traffic. It is also much easier to predict traffic volumes over a long period, than estimating a reasonable day average.23 votes
We are considering pricing changes to address the daily quota inconvenience.
Certain applications requires to know if device is disconnected with accuracy<1 minute. By implementing heartbeat pattern as advised (https://docs.microsoft.com/en-us/azure/iot-hub/iot-hub-devguide-identity-registry) with large amount of devices it creates enormous volumes of heartbeat messages and it results in generating 99.9% of quota messages just to know when device goes offline (Disconnected).22 votes
We are considering improving the connection information provided by IoT Hub.
Right now there seems to be no possibility to validate incoming messages which the IoT Hub ingests. It would be great if it'd be possible to add a JSON Schema file so that invalid messages would be rejected.15 votes
GSM Modules such as SIM800 and SIM900 are controlled using AT commands. The idea would be to add support in the SDK for establishing SSL connection and sending/receiving messages to/from IoT Hub over HTTP using AT commands under the hood.14 votes
Thanks for the feedback. We will evaluate this request.
One of the primary uses of the Field Gateway SDK will be to do message compression before sending to IoT Hub. Being the case, we would like the Azure IoT team to provide an included compression module. It should allow the developer to specific the compression type (Gzip by default).13 votes
- Don't see your idea?