[SOLVED] MS teams displays the wrong time (timezone)

Anonymous
2023-06-06T07:01:14+00:00

Ive been having this issue since i started using teams. The correct timezone for me is CEST (Central European Summer Time). For some reason, Teams always displays the wrong time although in my MS Account the timezone and language settings are correct. Also, for people that work in the same office, Teams shows me that they apparently are in the same timezone..???? How can i resolve this?

OS: MacOS Ventura 13.4

Teams Version 1.6.00.11156.

Thanks!

My Profile:

Other People in the same office:

Solution in comments

Microsoft Teams | Microsoft Teams for business | Settings | Other

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments
Answer accepted by question author
Anonymous
2023-07-28T15:51:29+00:00

Hello,

I had the same issue and tried just about everything, including the troubleshooting steps provided here. I discovered a solution that worked for me.

  1. Go to Outlook website.
  2. Click the settings gear icon on the top right corner.
  3. Go to "General" in the left pane and then ensure you are viewing "Language and time".
  4. Click "Change" under "Time zone".
  5. In the newly-opened pane, under "Time zones", there should be a message saying your "meeting time" is set to a different time zone. Click "Yes, update" button to reconcile the time zones.
  6. Restart Teams.

Was this answer helpful?

500+ people found this answer helpful.
0 comments No comments

41 additional answers

Sort by: Newest
  1. Anonymous
    2024-06-10T19:32:18+00:00

    I have the same problem, this did not fix for teams web or app.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  2. Anonymous
    2024-04-12T16:44:36+00:00

    If your device is getting its IP Address from a DHCP Server, one of the "Options" for the Scope that can be additionally sent (along with the address) is a Time Offset. The Time Offset amount should correspond to where the receiving IP Address's subnet is located, and be used to set the total seconds to add or subtract from UTC time (as received from NTP), thus reflecting the correct Time zone for time display. So NTP provides the Time as UTC (basically) Greenwich Mean Time minus any DST adjustments. The local device gets the Time Offset, from the DHCP Server. When the DHCP Server Admin added the subnet to the DHCP server, the admin took note of the address for the subnet range being set and added the offset value reflecting the subnets time zone. Perhaps local settings on the device determine whether it further adjusts time for Daylight Savings Time. So if your Desktop/Laptop or office Teams phones etc. are on a Corporate Network, check with the Network Admin to see if there is a Time Offset in place for your subnet.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  3. Anonymous
    2024-03-25T14:39:19+00:00

    The issue is not solved at all.
    I'm on GMT+2 timezone, and Teams shows that I am with 3h in advance (ex: 4PM => it shows 7PM) ;(
    This is on Windows 11 and the Teams New application. I can mention the Win11 itself, shows the correct time and timezone.
    I did setup this on outlook.com as well, without any modifications under computer Teams app (even if I restarted the app multiple times).

    Was this answer helpful?

    7 people found this answer helpful.
    0 comments No comments
  4. Anonymous
    2024-03-21T13:45:41+00:00

    I'm encountering a recurring problem with scheduling functionalities within Teams. Despite implementing all previously recommended solutions, the issue persists without resolution.

    It's puzzling that although deliberate attempts are made to modify scheduling times for testing purposes, the changes fail to reflect, thereby maintaining the resource within its original time zone that is incorrect.

    Was this answer helpful?

    0 comments No comments