Microsoft Dynamics 365 Blog

Users in Southern Hemisphere time zones that observe Daylight Savings Time (DST) with Datetimes that fall in the Standard Time part of the year are not converted correctly to/from Coordinated Universal Time (UTC).

The issue is twofold

1. datetimes are not converted to UTC when inserted into the CRM database

2. datetimes are not converted from UTC when retrieved from the CRM database

Because this issue affects both insertion and retrieval from the database, users may not observe any symptoms.  From the user perspective, the two issues cancel each other out, and datetimes appear correctly.   However, if an affected user switches to another time zone, or shares data with someone in another time zone, datetimes may appear incorrectly.

Let’s consider a user in affected time zone “(GMT +10:00) Canberra, Melbourne, Sydney”, who creates two appointments:


If the user switches to affected time zone “(GMT + 12:00) Auckland, Wellington”


If the user switches to unaffected time zone “(GMT +12:00) Fiji, Kamchatka, Marshall Is.”


To address this issue:

  • If you have not yet installed Microsoft Dynamics CRM 4.0, choose the “Update installation files (strongly recommended)” option when installing CRM 4.0.
  • If you have already installed Microsoft Dynamics CRM 4.0, please refer to “Hotfix information for Microsoft Dynamics CRM 4.0” in the following KB article:


Leslie Zavisca

We're always looking for feedback and would like to hear from you. Please head to the Dynamics 365 Community to start a discussion, ask questions, and tell us what you think!