![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(233.6, 88%, 32%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Azure IoT Hub
An Azure service that enables bidirectional communication between internet of things (IoT) devices and applications.
1,217 questions
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(214.4, 74%, 30%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAM%3C/text%3E%3C/svg%3E)
Hello @adems ,
it seems you are routing incoming IoT Hub messages to Azure Blob Storage.
Each message is enriched by the IoT Hub with 'system properties' (eg. name of the IoT Hub, Partition key)
The IoT Hub also adds the timestamp regarding the arrival of the messages.
This is in UTC (no time zone, universal time) because the devices can be positioned all over the world. By using UTC for all devices, you get a historically correct list of events.
This is a 'hard-coded' behavior and not changeable.
It's up to you to convert this in the local time of the user. This is a common programming pattern. Internally use UTC, externally use the converted timezone the user is familiar with. This is more work on the UI but the experience is as expected.