Community

Community

Loading...

397 Ideas

Add the custom domain name support for IOTHub Endpoint

Hi,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

Company Response

Hi, we have planned to add support for this feature soon.

GO SDK for Azure IoT

Offer Go as a language for Azure IoT SDK

Support multitenant solutions in IoT Hub

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.

Should be able to Stop any service, including IoT Hubs

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.

Auto-scale for IoT hub instances

I would like to have auto-scaling option.Or API to scale instances so I can script the auto-scaling

Company Response

Hi, we�re reviewing this request but don�t have timeline yet. Please vote on this idea!

Support data compression for telemetry

Supporting formats such as Protobuf and/or compressing in DeviceClient.SendEventBatchAsync

Company Response

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).

Allow to use connectionState to identify conected devices

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).

Under Review

All Ideas

Microsoft

Company Response

We are considering improving the connection information provided by IoT Hub

Add samples/support for Azure Storage blob download down to device

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 device

CoAP support for IoT Hub

The Constrained Application Protocol (CoAP) is a specialized web transfer protocol for use with constrained nodes and constrained networks in the Internet of Things. The protocol is designed for machine-to-machine (M2M) applications such as smart energy and building automation.It would be helpful if you could support CoAP in IoT Hub. It provides a lightweight REST model messaging which can be used in constrained devices with ease.COAP also provides stronger security at implementation level and will be a game changer for IoT Hub.

extend the route to blob file name format with dynamic parameters such as deviceId or messageType

from this text https://docs.microsoft.com/en-us/azure/iot-hub/iot-hub-devguide-messages-d2c :Azure Blob StorageIoT Hub only supports writing data to Azure Blob Storage in the Apache Avro format. IoT Hub batches messages and writes data to a blob whenever the batch reaches a certain size or a certain amount of time has elapsed.IoT Hub defaults to the following file naming convention:Copy{iothub}/{partition}/{YYYY}/{MM}/{DD}/{HH}/{mm}You may use any file naming convention, however you must use all listed tokens. IoT Hub will write to an empty blob if there is no data to write.It would be nice to be able to add {deviceId} or {messageType} to the url to create more structure.

All Ideas

Filters

Quick links