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 Central

Azure IoT Central is your IoT app platform that's highly secure, scales with your business as it grows, ensures your investments are repeatable, and integrates with your existing business apps.
  • Get connected: Azure IoT Central connects your IoT devices to the cloud faster than any other platform. Find new devices matched to your solution in the Azure Certified for IoT device catalog.
  • Stay connected: We understand how hard it is to keep devices connected and healthy. Centralized management helps you reconfigure and update them.
  • Transform: Our connectors and extensibility APIs bridge the gap between your business applications and IoT—providing a direct connection between IoT data and your decision makers.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Allow for connection string creation via the web UI

    Right now I need to use another tool - dps-keygen - and provide it with Primary key, Device id and Scope id to generate a device connection string ; it would be great if I could generate and access it without downloading node.js

    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

  2. Support "modules" from IoT Hub, along with multiplexed AMQP connection

    While developing a "field gateway" that takes data from local wireless sensors and passes it on to the cloud we found 2 things:

    1: Device modules work perfectly for this scenario, providing a hierarchy under a gateway device that does no have the resources to act as an "edge"

    2: Using credentials with the proper access (iothubowner e.g.) we can multiplex the sensor data, allowing us to use individual sensors as their own devices without having to manage a dozen sockets to the hub in the field gateway. It would be nice if we could have credentials with the same…

    5 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. Please add setModel() to the generated Python code in IoT Central

    The generated Python Code in IoT Central woul be easier to use and be more generalizable if you would include the setModel method to the code. That way, the device would be automatically created as instance of the Device Template.
    Since PnP is not available in Python yet, this would bring the user closer to the PnP experience.

    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

  4. gps to iot mqtt from devce

    Is there any example that sends GPS from device to IoT?

    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

  5. Implement Default Values

    Sending the Desired Properties every connection adds too much overhead, especially if the data is not changing.
    For cellular communication, constrained memory, and battery devices, this taxation is undesired.

    One way to mitigate this synchronization side-effect is to paint the default values in the UX without sending those to the device.

    IOTC should support "Device Default Values" for writable properties and if the twin element is null, display this value in the UX.

    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

  6. D2D messages

    Hi ,

    Is there a simple way to send device to device messages when using iot central ?

    Thank you in advance.
    Hakim.

    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

  7. Bug: Python sample app for previewing device template is out of sync with iotc python sdk

    The Python sample app that is downloaded for previewing a device template is out of sync with iotc python sdk. It will not even run as it appears to be using an outdated version of the sdk.

    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

  8. Expose the Device Provisioning Service Endpoint

    To export x509 certificates from the Twilio Portal and potentially, other provides, it is necessary to provide the Microsoft Azure IoT Device Provisioning Service Endpoint.

    This is found under shared access policies for DPS (hidden in IoT Central)

    Suggest to have it next to the ID Scope in the Administration > Device Connection page

    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

  • Don't see your idea?

Feedback and Knowledge Base