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

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

  2. 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…

    13 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 →
  3. Option to turn off system properties being put in MQTT topic name

    Currently when you send a message to a device via the IoT Hub, system properties are output in the topic name, such as:
    devices/matt/messages/devicebound/%24.mid=c7c6ee3d-9c90-4114-be93-a5c7f06740c4&%24.to=%2Fdevices%2Fmatt%2Fmessages%2FdeviceBound&iothub-ack=full&et=stmd
    Gets lot longer if you use more features like custom expiry, etc.

    For constrained MQTT devices not using the SDK (eg a 16 bit device), this eats a massive amount of bytes. It doesn't seem a great reason to have to implement a protocol gateway.

    It would be great to be able to turn system property output off on a device by device basis when registering devices.

    Still allow custom properties to be output.

    5 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 →
  4. From an MQTT client, you can publish on a different topic than expected

    I have seen this behaviour, is this as expected?
    I connect as deviceid1, and I can publish to devices/deviceid2/messages/events/ . The message is publish to devices/deviceid1/messages/events/

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

    We’ll send you updates on this idea

    0 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  5. Add support for verb tunnelling

    IoT Hub must support verb tunnelling to allow resource constrained devices that only have POST and GET to perform all the required operations (e.g. send DELETE requests).

    3 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 →
  6. Add ability for IoT Hub device SDKs to use specific Network connection

    When a device has multiple network cards or connection (say, Wifi and Ethernet, or 2 Ethernet cards), the IoT Hub device SDKs today pick the "default" one. It'd be interesting to allow the user to configure which connection the IoT Hub device SDK should use.

    2 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 →
  7. Share a Node.js version of Azure IoT Suite Predictive Maintenance Example

    It would be great to see a Node.js version of the predictive maintenance example: https://github.com/Azure/azure-iot-predictive-maintenance

    This would demonstrate for instance, how to use Node.js for building Azure IoT Event Processor.

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

    We’ll send you updates on this idea

    unplanned  ·  1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  8. Deploy to pre-established resource group

    Our enterprise Azure admin assigns resource group per user (i.e. Jon-Doe_Lab-rg) for security reasons. I am only allowed to deploy resources to this group. The RM solution wants to create it own resource group. I used a different subscription for creation and then tried to move all the resources to my enterprise group but ran into many errors. It would be nice to have a target "Resource Group" option on the deployment page.

    1 vote
    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 →
  9. Add support for SAM3X8E Cortex-M3 to the C device SDK

    There is Arduino Due build on SAM3X8E Cortex-M3 which is very similar to Mega 2560 from the number of pins perspective.
    Is is possible to bring the support of this SDK to this platform?

    1 vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    unplanned  ·  0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  10. Provide alternate authorization hook mechanism

    Customer needs to support Authz at the IoT Hub end point. They need to ensure that the security token is valid, not tampered with and that the Tenant Id in the message is allowed to send data from the associated devices.

    Suggestion:
    Support an Authentication mechanism that allows them to inject a module or a function in the pipeline and after or before messages are shredded.

    Standing up a protocol gateway for this is not an acceptable workaround because they will need to manage another SF service just for this.

    1 vote
    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 →
  • Don't see your idea?

Azure IoT

Categories

Feedback and Knowledge Base