Azure Functions are a blessing for IoT solutions. To be so flexible executing code whenever messages are arriving, every IoT project is fully depending on it.
But one of the biggest frustrations is the casting of (EventHub) messages towards a string! Only the message body is left! Once a message is passed on to an Azure Function, I only have access to the body of the message. I can not access the (routing) properties anymore.
And before we got Azure Functions, we had to work with Stream Analytics. And I still do! And it's so nice to have access to the IoT Hub values like the device name of the message. Because I am working with Azure Functions, I have to put it in the Message body first???
It would be great to have access to both the properties and the IoTHub values!
Well, it's possible now with some clever casting...
Read the full story here