Thanks for taking the time to provide us with feedback. We’ll take this into consideration as we plan feature roadmaps. We’ll post updates here as we determine next steps.
Luis on behalf of the Azure IoT Central team
We are adding support for Aggregate functions and Time windowing in Rules that will enable monitoring telemetry over a certain timeframe before alerting.
I will update the thread once the feature is available to try out.
We are exploring APIs to enable sending C2D messages without using the UI.
Today a workaround is by using Microsoft Flow to build your workflow and updating a property/setting of a specific device through the IoT Central connector.
We have added support for the complex objects with the latest preview update of Azure IoT Central. We also have array support on the roadmap and will share more details as they become available.
Please note that these features are in preview and we are listening to the feedback to further refine them.
You can read more about the new capabilities in the device template here: https://docs.microsoft.com/en-us/azure/iot-central/core/tutorial-define-iot-device-type-pnp?toc=/azure/iot-central-pnp/toc.json&bc=/azure/iot-central-pnp/breadcrumb/toc.json#prerequisites
Due to various technical limitations, the first iteration of the customer-owned domains functionality will not be available for a few more months. We will provide an update as soon as we can get a more specific ETA.
This is not planned for the next 6 months, but is on the roadmap.
Reopening this user voice item as our support for Skip/Take (Offset/Limit) was only limited to single partition queries.
The newly released .NET SDK v3 now includes support for x-partition queries using Offset/Limit. You can learn more about v3 SDK and try it and provide feedback on our github repo here.
We will also be back-porting this functionality to our .NET v2 SDK. This work will begin shortly and we anticipate it to be released in September.
Once that is released we will mark this feature as complete.
Thank you for your patience and votes.
Work on this feature has started. Will update here when this becomes generally available.
Thank you for your suggestion and votes.
We continue evaluating several alternatives to provide full email customization. We are actively working on an alternative.
Unfortunately we do no yet have an ETA.
This is planned for the next 6 months.
We have reviewed this and have elected to not include this on our road map for the time being. We may revisit this in the future so will leave as unplanned rather than declined or closed.
Thanks for your suggestion and comments.
Azure Cosmos DB supports the CONTAINS, STARTSWITH, and ENDSWITH built-in functions which are equivalent to LIKE.
We are planning to add support for LIKE since this is a top requested item, but meanwhile, please use the other equivalent keywords.
We definitely recognize the popularity of this feature, and we discuss it constantly during the planning phases. However there are certain technical limitations in the system that add a large amount of development cost. Because of the cost and the fact that there is a workaround available, other features get prioritized over this one.
That being said, please keep voting for it. The popularity of the feature does help bring it up and makes us reconsider every time.
Apologies for the delay.
We’re doing some research both on the specifics of this ask as well as what it would take to support this.
Is the ask here to do the same thing that regular Azure AD does (see: https://blogs.technet.microsoft.com/enterprisemobility/2014/12/18/azure-active-directory-now-with-group-claims-and-application-roles/) or is are there different requirements around this for Azure AD B2C?
We’re working on increasing the size limits for twin properties and will use this feedback item to track that. We are also looking at how to best support binary data.
78 votestg shared this idea ·