I have an IoT Edge module which connects to an on-premise WCF API. One of the API calls returns a local datetime value to the module, with the local timezone specified. I noticed that when that datetime value is serialized into a D2C telemetry message, it has been converted to UTC and the timezone information has been removed. In most cases that would be fine, however I need to use the local datetime as part of a key for data integration with an on-premise database. It looks like the module container is set to UTC timezone, so it seems to be automatically converting the value either to the container's timezone or to UTC by default. Is there a way I can ensure the local datetime value returned by the API is not automatically converted to the container's timezone?