Incorrect Time Zone in CRM

Andrew Carl 0 Reputation points
2026-10-07T20:19:56.19+00:00

My computer shows the proper time but when I input activities in Dynamics it is off by an hour

Windows for business | Windows Client for IT Pros | User experience | Other
0 comments

2 answers

Sort by: Oldest
Most helpful Newest Oldest

  1. AI answer

    2026-10-07T20:20:11.75+00:00

    An hour offset in Dynamics is typically caused by a time zone or daylight saving mismatch between Windows, the Dynamics user settings, and how the app renders the date/time value.

    1. Verify the Dynamics personal time settings:
      • In Dynamics 365, select Settings in the upper-right corner.
      • Select Personalization Settings.
      • On the Formats tab, confirm the Date Format and Time Format match the regional format in use.
      • Check the Time Zone setting in personal options and make sure it matches the local region.
    2. Verify Windows time zone and DST settings:
      • Go to Start > Settings > Time & language > Date & time.
      • Confirm the correct Time zone is selected.
      • If the time zone is set manually, make sure Adjust for daylight saving time automatically is enabled when applicable.
    3. Check for a browser locale mismatch:
      • If the browser language/locale differs from the Dynamics format settings, the schedule board and other date/time displays can show incorrect times.
      • Make the browser locale match the Dynamics regional format, then refresh the page.
    4. Determine whether the problem is in the stored value or only in the display:
      • Open the activity record directly in Dynamics and check the date/time field there.
      • If the record shows the correct time but another view shows it one hour off, that points to a client-side rendering or DST issue.
      • If the stored value itself is wrong, review whether the column uses User Local, Time-Zone Independent, or Date only behavior, because those display differently.
    5. If the issue happens around a daylight saving transition:
      • Dynamics can show shifted times across a DST boundary in some views.
      • If records are correct but the board or app view is off by one hour, test a date after the DST transition to confirm whether the rendering path is applying the wrong UTC offset.

    If Windows shows the correct local time and only Dynamics activities are off by one hour, the most likely fix is correcting the Dynamics user time zone/format settings and ensuring they align with Windows and the browser locale.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

  2. Daphne Huynh (WICLOUD CORPORATION) 1,980 Reputation points Microsoft External Staff Moderator
    2026-10-08T04:00:12.1933333+00:00

    Welcome to Microsoft Q&A!

    Thank you for sharing the details of the issue.

    This behavior is often related to the time-zone setting configured for your Dynamics 365 user rather than the time displayed on your computer. A mismatch between the Dynamics 365 user time zone and the Windows time zone, particularly with daylight-saving settings, can cause dates or times to appear differently.

    Please check the following:

    1. In Dynamics 365, go to Settings > Personalization Settings.
    2. On the General tab, locate Set the time zone you are in.
    3. Make sure the selected Time Zone matches the time zone configured in Windows.
    4. Save the changes, then refresh Dynamics 365 or sign out and sign back in.

    You can also verify your Windows settings under Settings > Time & language > Date & time. Please confirm that the correct time zone is selected and review the daylight-saving settings.

    If the Dynamics 365 time zone is already correct, it would also be helpful to check the behavior of the affected date/time field. In Dataverse, date/time fields can use different time-zone behaviors.

    For example, User Local values are displayed according to the user's local time zone, while Time-Zone Independent values are displayed without time-zone conversion.

    Since the difference is exactly one hour, I recommend starting by comparing the Dynamics 365 user time-zone setting with the Windows time-zone and daylight-saving settings.

    If the same behavior continues in a clean environment without any relevant policies or customizations configured, I suggest you contacting the Dynamics 365 support team for further investigation. When opening a support request, it would be helpful to include the affected user's Dynamics 365 time-zone setting, the Windows time-zone setting, details of the affected activity or field, and an example showing the one-hour difference.

    I hope this helps you identify the cause of the time difference.

    References:

    Set personal options in Dynamics 365 Customer Engagement (on-premises) | Microsoft Learn

    Specify time zone settings for a user (Microsoft Dataverse) - Power Apps | Microsoft Learn

    Specify time zone settings for a user (Developer Guide for Dynamics 365 Customer Engagement) | Microsoft Learn

    Set a user's preferred time zone - Finance & Operations | Dynamics 365 | Microsoft Learn

    Time zone entities (Developer Guide for Dynamics 365 Customer Engagement) | Microsoft Learn

    If you find it useful, please click Accept Answer.

    Thank you for choosing Microsoft Q&A.

    Was this answer helpful?

    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.