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. 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 →
  2. PowerShell documentation for AzIoT

    One should be able to setup sending sensor telemetry data from a Rasberry Pi to AzIoT using PowerShell 7 on Rasbian. Please provide documentation like already exists for other languages.

    18 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 →
  3. MQTT over TLS to servers outside Azure IoT Hub, per MSFT's open Cloud pledge

    Enable MQTT over TLS (using remote attestation certificate) to connect to MQTT brokers running on servers other than IOT Hub, per the attached Azure Sphere "Open Cloud" pledge. HTTPS is inadequate for many IoT use cases.

    18 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

    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  4. IoT DPS: Allow customization of Device ID for devices registered via Group Enrollment

    For devices that enrolled via Individual Enrollment, the device can provide Device ID that is different from Registration ID during registration.
    But for devices that enrolled via Group Enrollment, the Device ID can not be customized and is always default to Registration ID.

    Use case: Use device serial number as Registration ID (by setting CN to serial number in the device certificate). But for Device ID, we would like to use a user friendly name.
    Example:
    Registration ID = abc12345678
    Device ID = US-Chicago-Device-1001

    17 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. IoT Hub: Validate JSON schema of D2C messages

    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.

    16 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 →
  6. Field Gateway SDK: Please provide a module that does message compression before sending to IoT Hub.

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

    16 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 →
  7. 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 →
  8. IoT Hub DeviceTwins to store device public ip address

    If the default metadata of the DeviceTwins document could store LastKnownPublicIPAddress value, that would help some customers to further do maintenance on their devices.

    This request came from one of our customers.

    14 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 →
  9. Implement backup/restore option for DPS (Device Provisioning Service)

    DPS has a scope-id that is embedded in a device during manufacturing. As such, there can be devices on the shelve with a DPS scope-id embedded, waiting to be enrolled. This makes the scope-id critical information.

    Once a DPS instance is created, a scope-id is assigned. When DPS would be deleted at any time, there is no way to get exactly that scope-id back.

    Pls implement a backup/restore option for this.

    14 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 →
  10. Remove cloud to device time-to-live limit of 48 hours

    We have scenarios where it is valid that a device may not connect in any arbitrary 48 hour period, such as a stationary vehicle, or a specialised machine that is not in use for a long period.

    By having the command messages expiring, we have to monitor expiries and resend the message every 48 hours, if we want to use IoT hub. Or, we could bypass IoT hub and use service bus (which is odd, since IoT hub is built on service bus), or implement some other (http) service that devices can call - both of which mean that we…

    14 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. Add support for "order by" clauses when querying devices in Azure IoT Hub

    Maybe I'm missing something, but in the docs here - https://docs.microsoft.com/en-us/azure/iot-hub/iot-hub-devguide-query-language - there doesn't seem to be any way to order results when querying against the IoT Hub. It seems possible to group results, but not order them.

    I've run into a situation where this would be really handy - e.g.: find all devices that have a certain reported property, and then order them by last connected date. I was a little surprised to not see this mentioned anywhere in the docs.

    13 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

    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  12. Please allow to set 'larger' metadata properties on a device twin

    Hello, I really love the device twin concept. It allows us to query devices, use the reported/desired properties, etc. However, I would love to see an extra 'non-indexed', 'non-searchable' section in the device twin that is not limited to 512 bytes.

    I want to keep some configuration (a json string) and link it to a device twin. That way, I don't have to foresee external data storage (such as DocumentDb), to save those values and everything could be received through the same SDK. Another option could be to save that larger property as a blob and keep the sas in…

    13 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. Support Network Security Groups to restrict access by IP or enable VPN tunneling

    Feedback: Have an optional NSG like feature for IoT Hub. This will enable restricting access to IoT hub from an IP Range or enable VPN tunneling

    Scenario:

    Large enterprises with manufacturing units, factories etc have very stringent policies on connectivity to Internet. Most of them only allow data transfer for VPN. We had a tough time convincing security team to send data over to IOT Hub. They agreed for the PoC with certificate based authentication. However, for production they will not agree to this approach. It has to be over VPN, or there should be a way to restrict the…

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

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  15. iot hub doesn't support "Tags" in the azure portal

    Tags are useful for splitting out billing and most azure services support them, however it seems that iot hub doesn't. Please can support be added.

    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

    3 comments  ·  Flag idea as inappropriate…  ·  Admin →
  16. Increase the message limit for the free tier IoT Event Hub

    Currently there is too much of a gap between the free IoT Event Hub (8k messages per unit) vs the first paid tier (400k messages per unit). The cost jumps from free to an estimated £30 per month. The free tier needs to have its message limit increased. 8k is barely enough for a decent demo during community talks.

    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 →
  17. 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 →
  18. Azure IoT Hub dashboard portal enhancement

    People is curious about how the LAST STATUS UPDATE (UTC) is changed and when. People are confused by the result that occurs differently than the expected result of the column name.

    Normally people thought that when device is active the UTC value is changed but it’s not. The value is only updated when Device Twin’s “Status” value are changed.
    This is little confusing point to users.

    What if the lastActivityTime field is pinned in the table as a default column? It would be better to enhance user experience for checking device status.

    10 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 →
  19. Need a solution for a business rules engine

    IoT Suite seems to depend on ASA for any business rules handling in the samples and reference architectures. ASA can detect the criteria, but seems very lacking in the response action that should be carried out. More functionality, including a canned set of response actions should be available as standalone BRE.

    10 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 →

    We’ve made progress on this scenario/pattern implementing message routing in the IoT Hub service.
    You can today set rules (called routes) based on messages content or headers and have them sent directly to “custom endpoints” (today we support Event Hub, Service Bus Queues and Topics, Blob Storage). Learn more here: https://docs.microsoft.com/en-us/azure/iot-hub/iot-hub-devguide-endpoints#custom-endpoints

    We are considering other custom endpoint types. Your feedback is welcome here.

  20. Allow selecting encoding type (Base64 or JSON) of message body on routing settings to Blob storage

    Body of message routed to Blob Storage will be encoded in Base64 by default, and if users want to store them in JSON, device needs to set contentType and contentEncoding explicitly.
    https://docs.microsoft.com/en-us/azure/iot-hub/iot-hub-devguide-messages-d2c

    But in some cases, device cannot be configured to send these properties even though it actually send correct JSON message body.
    So IoT Hub should allow selecting encoding type (Base64 or JSON) of message body on routing settings to Blob storage. With this setting, IoT Hub will not refer contentType and contentEncoding and try to store data in selected format forcefully.

    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

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Azure IoT (Hub, DPS, SDKs)

Categories

Feedback and Knowledge Base