> The server is set up with a different timezone can somehow create conflicts with azure.
I can not think of any side effects of changing the timezone but please be aware that Azure Storage, SQL Azure are still using UTC timeone. If you want to confirm this with our auzre support, please check the following link.
Hi, I have folow your idea and I have asked to support.
This is the response:
Changing the server time on the Azure Virtual Machines using a startup task is not recommended, you should rather use methods like
TimeZoneInfo.ConvertTimeFromUTCTime in your code. This is a good reference
article (Coding Best Practices Using DateTime in the .NET Framework).
for newly created application, i would recommend using UTC timezone. this is not only because the official recommendation on Windows Azure. But also to enable interfacing with other external system to be more standardized.
However, considering you've bunch of current existing data in local time. It would be very troublesome and much effort to convert all of your data to UTC timezone. Then one day if you are about move back to on-premise, how do you deal with those data again?
convert back again, uh....
I've got an idea mentioned
here, it may not be a real solution, but it's at least a workaround to solve the issue.
Proposed As Answer byDaniell.ChongMonday, January 28, 2013 7:09 AM