Update: Microsoft will be moving away from UserVoice sites on a product-by-product basis throughout the 2021 calendar year. We will leverage 1st party solutions for customer feedback. Learn more here.

Azure IoT (Hub, DPS, SDKs)

This forum is to get feedback on Azure IoT Hub, Azure IoT HubDevice Provisioning Service (DPS), and Azure IoT SDKs. This forum will help the engineering team collect feedback from our customers and users and help us understand and prioritize the roadmap.

For providing feedback on other IoT related services, please do so on the corresponding forums.


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

    111 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    under review  ·  8 comments  ·  Flag idea as inappropriate…  ·  Admin →
  2. 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.

    70 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    under review  ·  15 comments  ·  Flag idea as inappropriate…  ·  Admin →
  3. Support data compression for telemetry

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

    65 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    8 comments  ·  Flag idea as inappropriate…  ·  Admin →

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

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

    59 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  Flag idea as inappropriate…  ·  Admin →
  5. 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).

    46 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    10 comments  ·  Flag idea as inappropriate…  ·  Admin →
  6. Consider a pricing model that bills based om the number of messages instead a fixed number per day

    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.

    32 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  7. Support Iot hub upload requests monitoring

    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.

    29 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    under review  ·  1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  8. Add native support for GSM modules such as SIM900 or SIM800

    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.

    23 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    5 comments  ·  Flag idea as inappropriate…  ·  Admin →
  9. Add TLS Session Ticket support to reduce data exchange during TLS connection

    Since many IOT devices could use SIM cards with limited internet data contract, I think it could be a great idea to support TLS Session Ticket to reduce the data exchanged by peers at each Iothub connection/disconnection: certificates exchange can be ignored if the peers are already paired by a previously successful connection, so we can avoid about 10kB of data each connection.

    "When the server sends the “Server Hello” message, it can include a session identifier. The client should store it and present it in the “Client Hello” message of the next session. If the server finds the corresponding…

    20 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    under review  ·  0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  10. SSH Tunneling to Devices

    Customer uses a Linux box to wire all the sensors which runs an OPC UA server. A user with SU privileges will SSH into the box and fix any issues related to malfunctioning OPC server, configuration change, etc. In terms of the number of sessions, the SSH session is only used occasionally on a per device basis. This falls under broader device management category for non-constrained devices like PLC and RTU used in a lot of industrial automation scenarios. If IoT Hub wants to be the focal point for industrial automation devices, it is prudent to offer that capability. If…

    15 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    5 comments  ·  Flag idea as inappropriate…  ·  Admin →
  11. IoT features free for DreamSpark User

    This Build you showed some Kids using your tech. It would be great if you enable Student all over the world to use azure iot tech for free. Just think about it...

    11 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  12. Allow to attach metadata to blob when uploading files via IoT Hub SDK

    Allow to add blob metadata when uploading files using the IoT Hub SDK

    9 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  13. Robust file upload (with resume) for the C device SDK

    Azure supports uploading large files in chunks to support continuing broken uploads. This should be added in the C device SDK as well.
    I could also imagine having the user implement this and just providing a hook to doing something with a CloudBlockBlob:
    public Task UploadBlobAsync(string blobName, Func<CloudBlockBlob, Task> upload);

    8 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  14. Method to determine real size of message in Device/Service Client SDK

    Since the SDK is adding its own headers and serializes the content which is sent to the IoT Hub, then it is not possible to upfront know if a message will be too large.

    Would be nice it there was a method that could give the size, so we can compare to the limits of the IoT Hub.

    6 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  15. Field Gateway SDK: Please provide a Device Management module

    The Field Gateway SDK will be used to manage leaf node devices. Device Management module is a must have and at this point must be coded by each developer implementing a gateway. Please provide a baseline Device Management module that ships with the Gateway.

    6 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    under review  ·  0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  16. Connect with managed service identity

    Currently the registry manager needs a connection string with a shared secret. From a security point of view, it would be great if a can connect my code withtl the managed service identity of my azure function or web app. So I can connect on the cloud side passwordless to the iothub. If there is no secret, noone can steal it.

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    under review  ·  0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  17. Documentation - Manufacturing customers need example of mapping Device Twins to physical equipment

    Customer needs and example of how to map a Device Twin to a physical device like a PLC. E.G. map a value from a Device Twin to a PLC register.​

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  18. Need guidance on how to handle twin data > 8kb

    The customer anticipates needing to push larger configurations via Device Twins than the currently supported 8K limit. We need to detail the best patterns and practices to push larger configuration files to/from devices & module twins.

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    under review  ·  1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  19. Build integrated device enrollment including cellular SIM enrollment using Jasper

    Build integrated device enrollment portal/API including cellular SIM provisioning using Jasper - so it can be done all in one place when adding a new cellular IoT device

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    under review  ·  1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  20. Write Cordova Plugin for Azure IoT SDK.

    Write cordova plugin for Azure IoT SDK. It will benefit the hybrid app developer and hybrid app's can leverage the both Azure IoT SDK Java and C function's in iOS and Android apps.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    under review  ·  0 comments  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1
  • Don't see your idea?

Azure IoT (Hub, DPS, SDKs)

Categories

Feedback and Knowledge Base