As seen in my previous post, The IoT Hub routing feature supports message enrichment, both for IoT devices and IoT edge modules.
Using the routing message enrichments, each incoming message gets extra user properties based on either static values, device twin tags, or device twin desired properties.
Unfortunately, only ten enrichments can be added:
If you want to pass more values, this will not work for you.
It would be great if nested JSON properties would count as one.
Again, unfortunately, only simple types (string, decimal, boolean, date/time, etc.) are supported so this excludes nested JSON (complex types).
Below, a viable solution to overcome both restrictions, using Azure Stream Analytics, is presented.
Let’s see how this works out.Doorgaan met het lezen van “How to cope with IoT Hub enrichment restrictions”