(Teams) Incorrect SAST Time Zone in Generated Meeting Invitation

Robby Petrotekno Online 0 Reputation points
2026-10-27T02:47:42.5133333+00:00

I would like to report a time zone display issue in Microsoft Teams Personal and request your assistance in investigating it.

Issue description:

When I create a meeting directly in Microsoft Teams and click Copy invite in the “Meeting created” window, the generated invitation displays the time zone as SAST (South Africa Standard Time) instead of Jakarta time (WIB, UTC+07:00).

However, the meeting time displayed in the Teams calendar remains correct.

Troubleshooting steps already performed

  • Verified that Windows is configured to use (UTC+07:00) Bangkok, Hanoi, Jakarta.
  • Confirmed that Teams has Follow OS settings enabled and displays the current time zone as Asia/Jakarta.
  • Verified that Outlook Calendar is configured for Jakarta time.
  • Cleared the Microsoft Teams cache.
  • Tested both the Teams desktop application and Teams web version. The issue persists in both.
  • Created a Teams meeting through Outlook.com Calendar with the Teams meeting option enabled. The resulting invitation did not display SAST.

Based on these tests, the issue appears to be isolated to the invitation text generated through the -Copy invite- function when creating a meeting directly in Teams.

Could you please investigate why the generated invitation displays SAST despite the correct Jakarta time zone settings? I would appreciate your guidance on whether this is a known issue or if any additional account-level configuration or troubleshooting is required.

I can provide screenshots and additional details if needed.

Thank you for your time and support. I look forward to your response.

Best regards,

Microsoft Teams | Microsoft Teams for business | Meetings and calls | Schedule meetings
0 comments

2 answers

Sort by: Oldest
Most helpful Newest Oldest

  1. AI answer

    2026-10-27T02:48:37.2366667+00:00

    Report this through Teams Personal → Settings and more → Feedback → Report a problem, because your cross-client testing isolates the symptom to Teams Personal’s Copy invite output rather than the calendar time or local time-zone configuration.

    Microsoft documents Copy invite as the Teams Personal function that places the meeting invitation on the clipboard, but no published Microsoft notice identifies the exact Asia/Jakarta → SAST behavior as a known issue.^1^

    Submit a reproducible report

    1. In Teams Personal, create a short test meeting directly in Meet → Schedule a Meeting.
    2. Select Copy invite and save the unmodified output.
    3. Go to Settings and more → Feedback → Report a problem.^2^
    4. Include:
      • Expected result: Jakarta/WIB, UTC+07:00.
      • Actual result: SAST in the copied invitation.
      • Whether only the zone label is wrong or the numerical start/end times are also shifted.
      • Confirmation that the Teams calendar itself shows the correct time.
      • Confirmation that the same result occurs in desktop and web Teams.
      • A comparison showing that a meeting created through Outlook.com does not produce SAST.
      • Screenshots of the Teams calendar entry and copied invitation, with participant details and meeting links obscured.
      • The affected account type, operating-system version, Teams version, browser/version, and approximate test time.
    5. Immediately after reproducing it in the desktop client, press Ctrl+Alt+Shift+1. Teams creates an MSTeams Support Logs folder in Downloads. Compress it and attach it through Upload files in the feedback form.^2^

    Teams Personal diagnostic logs are intended to help identify problems in the application’s components and can also be included by enabling Include Troubleshooting info when that option appears.^3^

    Do not include phone numbers, addresses, participant email addresses, or other sensitive information in the report.^4^

    Workaround

    Until Microsoft investigates the generated text, continue creating affected invitations through Outlook.com Calendar with the Teams meeting option, since your test confirms that path generates the correct invitation. Alternatively, copy only the meeting link and manually state the meeting time as WIB (UTC+07:00).

    Before distributing an invitation, compare its numeric start/end times with the correct Teams calendar entry:

    • If the times match and only SAST is shown, treat it as an invitation-label/output problem.
    • If the times differ by five hours, do not send that copied invitation; use the Outlook.com version instead and include this distinction in the report.

    What not to change

    No further cache reset, OS time-zone change, or Teams reinstall is indicated: the issue reproduces in both desktop and web Teams while the calendar remains correct. Teams normally follows the device time zone when Follow OS settings is enabled, which you have already verified.^5^

    The Exchange mailbox PowerShell fixes reported for Teams for business should not be applied here unless Microsoft Support first confirms that the affected personal account has an applicable Exchange mailbox configuration. Those fixes concern mailbox regional or working-hours settings, whereas your Outlook.com-generated invitation is already correct.

    If in-product feedback does not provide sufficient follow-up, use the Contact us option referenced in the Teams Personal diagnostic documentation and provide the same reproduction package and feedback submission details.^3^

    References

    1. [Desktop](https://support.microsoft.com/teams/personal/meetings-calls/schedule-a-meeting-in-microsoft-teams-personal#update-meeting-details)
    2. [Desktop](https://support.microsoft.com/teams/personal/troubleshoot/send-feedback-or-suggest-a-feature-in-microsoft-teams-personal)
    3. Diagnostic data in Microsoft Teams for personal use | Microsoft Support
    4. Microsoft Teams feedback privacy
    5. [Desktop](https://support.microsoft.com/teams/notifications-settings/change-settings-in-microsoft-teams#change-your-time-zone)
    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

  2. Michelle Nguyen 2,620 Reputation points Independent Advisor
    2026-10-27T04:31:49.3+00:00

    Hello @Robby Petrotekno Online

    Thank you for the detailed description and for listing the steps you've already checked. I'm only a community member, so I can't see your account or confirm the cause on Microsoft's side. I also couldn't find any official Microsoft notice about the Copy invite function displaying the wrong time zone as you describe.

    Based on your test results (the Teams calendar is correct, an invitation created from Outlook.com doesn't have the problem, and only the text from Copy invite shows SAST), this is more likely an issue with how Teams generates the invitation text than with your Windows or Outlook configuration. I can't confirm this.

    You could try the following to narrow down the cause:

    1. Temporarily turn off "Follow OS settings" and manually select (UTC+07:00) Bangkok, Hanoi, Jakarta, then create the meeting again and select Copy invite. You could also try selecting a different UTC+7 time zone to see whether the label changes accordingly. This is only a test to help find where the problem is.
    2. Compare different ways of getting the invitation. Reopen the meeting from the Teams calendar and copy the link and details from there, then compare them with the Copy invite text you get right after creating the meeting.

    To narrow it down further, could you let us know:

    • In the copied text, is the time itself off (for example, shown in SAST, about 5 hours different), or is only the time zone label wrong?
    • Are you using Teams with a personal Microsoft account, or Teams for work or school?
    • What is your Teams version, and does the problem happen with every meeting or only some?

    When sharing screenshots, please remember to hide any personal information.

    Please let me know the result.

    Was this answer helpful?

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.