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.
-
Need guidance on CI/CD for Edge
Customers should be provided example CI/CD workflows in VSTS for build IoT Edge modules and complete deployment packages.
4 votesThis is currently in progress. You should see upcoming feature release in VS Code to help with CI/CD for Edge.
-
influxdb as Paas
For IoT Scenarios is a influxdb the most efficent one. We can use only in azure Docker instance without persitents or we install it on IaaS.
Please extent your paas offer.4 votes -
Read from IoT Hub like a generic MQTT server
I appears that you cannot read from IoT Hub without using one of the prescribed SDKs. Furthermore it seems like reading is not well supported outside of the .NET SDK (I am talking about monitoring messages, not reading back ACKs after writing).
I would be a lot easier if IoT Hub could be connected to with a generic MQTT connector.
4 votes -
Provide a more flexible billing model for customers who build IoT SaaS products on top of Azure IoT
IoT Hub needs to have an ISV model. For partners, the current pricing model is not an option for them. While their overall volume warrants the higher pricing tiers, using IoT Hub as a level of isolation (1 hub per customer), puts them back into the expensive pricing tier.
Ideally, we would duplicate the SQL Database Pooling pricing model where the pricing is based on the resources use for a pool of resources.
Suggestion: Allowing the customer to pay per message instead of buckets of messages would be the way to go.
4 votes -
Custom path for blob in DeviceClient.UploadToBlobAsync()
When invoking the UploadToBlobAsync method the file is added to a DeviceId folder in the root of the blob container. I would like to put all files in a custom location omitting the DeviceId root.
4 votes -
Add support for plain text content to IoT Hub messages
Messages are now created as a byte[].
For connection with Stream Analytics plain text is needed.Solved it by writing my own helper class to sent plain text 'messages' for my UWP app running on a RaspberryPI.
Please add plain text content to the message class for easier development.
4 votes -
Add system property SessionId to the Message
Add a new system property SessionId to the Message (Microsoft.Azure.Devices.Client) to enable usage of
https://docs.microsoft.com/en-us/azure/service-bus-messaging/message-sessions in case of following path of messages: device -> IoT Hub -> Service Bus Topic -> Azure FunctionService bus demands system property, but does not take into account custom properties.
Without such support it is almost impossible (or demands additional effords and resources) to implement sequential messages processing using Service bus
Discussions of this problem:
https://github.com/Azure/azure-iot-sdk-csharp/issues/10713 votes -
Support C2D Messages in IoTEdge Modules
Please support C2D messages in IoTEdge Modules as an enhancement.
I am migrating from iotdevice to iotedge and need this support.
3 votes -
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.
3 votes -
Connection strings for an IoT Hub should be easier to find
Connection strings for an IoT Hub are currently too hard to find -- they should be made easier to find.
3 votes -
Support binary file upload to blob storage for Python
We need to upload media data from our IoT edge devices and the Python SDK only supports txt upload. Please add binary support. Can you give an estimate on the availability of this?
3 votesHi there, this is indeed a limitation on the Python SDK due to the limitation from C SDK.
We are working on a native Python SDK that will remove this restriction. I don’t have a clear ETA, but we will be public previewing the native version in the next few months.
If you are waiting on this feature for production, please let me know. -
ECC certificats support
ECC (Eliptic Curve Cryptography) certificats have smaller key size and footprint for TLS handshakes providing optimal security in tiny IoT devices. The technology is mature and future proof at the same time.
https://www.digicert.com/ecc.htm3 votes -
We should monitor IoT Hub Messages on Azure Portal without using any JS tool (iothub-explorer node.js)
There is only a card box about remainig dailly message count. It would useful if there will be a drill down for information about the message content. In other words, it's better to have "iothub-explorer monitor-events" command functionality on IoT Hub section at Azure Portal.
3 votes -
IoT Hub partitions monitoring
This could be valid for Event Hubs as well. At the moment there is no tool for monitoring individual IoT Hub Device to cloud/EH partitions. Recently we had a problem where one partition got virtually stuck while others were processed fine. It would de good to see at least simplified data for:
- "fullness" of partitions compared to each other
- position of consumer for each consumer group on the partition relative to the oldest and newest message in the partition
- timestamp of the last read message for each consumer and partitionThe data doesn't have to be live,…
3 votes -
C2D Support in REST APIs
The REST APIs do not include C2D capabilities. Customers who need REST only solutions need this.
3 votes -
Need guidance on hierarchical architecture
Customer wants to accomplish a scenario where a sensor goes into an edge device which in turn goes into another edge device instead of an upstream (IoT Hub) target.
3 votes -
Need an update flow for deployments
Customer found that they were deleting the device deployment each time they wanted to add a new module or redeploy an existing module. They felt they should be able to update the deployment, and the runtime would only create or rm the changed modules.
3 votes -
Max Concurrent Active Job Quota is too limited
The maximum number of active jobs allowed to run simultaneously is 10. This is the quota for the highest pricing tier of Iot Hub (S3, at 5k per month). When managing tens of thousands of devices, manually managing the queuing of job slots becomes impractical.
3 votes -
Subscribe to IoTHub messages by device or message criteria
Similar to message routing but client driven.
Currently clients have to receive all messages and filter out the ones they don't want. This is very inefficient, for example in the case where you might send a command to a particular device and just want to check the value of the next message sent to IoT Hub from that device. Temporary subscriptions (even if limited to a short period) on device or message value would help a lot in such situations.
3 votes -
3 votes
- Don't see your idea?