Azure IoT

This forum is to get feedback on the new IoT services: Azure IoT Hub and Azure IoT suite. This forum will help the engineering team collect feedback from our customers and users and help us understand and prioritize the roadmap.

  1. Bring IoT Hub into Azure Stack

    Industry sector (with integrated IIOT) will certainly appreciate Azure Stack - power of Azure in own Datacenter.

    128 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    91 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    90 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    10 comments  ·  Flag idea as inappropriate…  ·  Admin →

    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.

  4. new feature for IoT Hub and Event router

    Hello,
    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
    - storage
    - sql database

    thanks
    BR
    Rino

    87 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  5. Support arrays for tags in Device Twins

    The device twins could support array types for tags.

    69 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    planned  ·  10 comments  ·  Flag idea as inappropriate…  ·  Admin →
  6. Support data compression for telemetry

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

    49 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

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

  7. 44 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    39 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    37 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  Flag idea as inappropriate…  ·  Admin →
  10. iot hub routing, publish device twin tags in message properties

    message routing is an extremly powerfull mechanism. but once the message is routed on a custom endpoint it will be really powerful to have some device twin tags promoted as message properties.
    i.e message.body.temp>50 goes in alert queue but promote the $twin.tags.devicelocation and $tein.tags.customerId in the properties. In this way a backend application can Immediately use this information without retrieving it from another system

    33 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  11. HTTP 2.0 support

    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!

    32 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    28 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    8 comments  ·  Flag idea as inappropriate…  ·  Admin →
  13. stack

    Bring Azure IoT Hub to AzureStack

    28 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    26 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    25 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    25 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  17. 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.

    24 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  18. Field Gateway SDK: Please provide a module that does message aggregation before sending to IoT Hub.

    IoT messages are very small and Azure IoT message block size is 4k. The Field Gateway will be used to aggregate messages before sending to IoT Hub so we can take advantage of that. Since message aggregation will be one of the primary uses of the Field Gateway, the Azure IoT team should provide that as an included module. The module should allow the developer to specific a block size (default to 4k) and a tolerance (default to 100 bytes). If the message is block size - tolerance, it should push the aggregated block to the queue.

    23 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    5 comments  ·  Flag idea as inappropriate…  ·  Admin →
  19. 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 Storage
    IoT 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}…

    22 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  20. Add CORS Support on IoT Hub Endpoints

    Please add CORS Support on IoT Hub endpoints so we can call them from browser based JavaScript applications.

    20 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1 3 4 5 12 13
  • Don't see your idea?

Feedback and Knowledge Base