iot hub routing, publish device twin tags in message properties
message routing is an extremly powerfull mechanism. but once the message is routed on a custom endpoint it will be really powerful to have some device twin tags promoted as message properties.
i.e message.body.temp>50 goes in alert queue but promote the $twin.tags.devicelocation and $tein.tags.customerId in the properties. In this way a backend application can Immediately use this information without retrieving it from another system
We just announced that IoT Hub message enrichments (https://docs.microsoft.com/azure/iot-hub/iot-hub-message-enrichments-overview) is now available in public preview in all public clouds except West US, East US and West Europe. You can use this new capability in IoT Hub to stamp additional information and enrich messages egressed from IoT Hub. We have native support to stamp the IoT Hub name and information from your device twins, as well as, any static string.
Till Maurer commented
This is a good Idea. It would also mean that multi tenant solutions would be able to pick up the tenantId from device twin and use it in functions without querying the twin again.