Public mode

No access to your tenant or devices. Every item links to its source. What this means

Some sources, documents or advisories need attention: 271/272 feeds/APIs · 469/469 docs · 8/9 advisories · checked 16:49 UTC Customize Public modeDiscuss ChangeIntel on Discord

Automatic synchronization with device time zone, no client restart required

From Microsoft 365 Message Center Archive by Merill Fernando · Microsoft may not have sent this notice to your tenant.

Rollout

Rollout dates are often only in the text. When Microsoft moves them, the change shows under "What changed".

What the notice says

Microsoft’s text, safely structured

Introduction

Microsoft Teams is improving time zone handling in the Teams desktop client for Windows and Mac and Teams on the web. With this update, Teams will automatically apply the new device time zone when a time zone change is detected, without requiring a client restart. This enhancement provides a smoother, more seamless experience for users who travel or work across multiple regions.

When this will happen

Targeted Release: Rollout will begin in early February 2026 and complete in early February 2026.

General Availability (Worldwide, GCC, GCC High, DoD): Rollout will begin in mid-February 2026 and complete in late February 2026.

How this affects your organization

Who is affected:

  • Users on the Teams Desktop Client for Windows and Mac and Teams on the web.

What will happen:

  • Teams will automatically synchronize to the updated device time zone when a time zone change is detected.
  • No restart will be required when the OS time zone changes.
  • The active time zone will be shown in Teams Settings > General.
  • This update is applied automatically and does not require any admin configuration.

What you can do to prepare

No admin action is required.

  • The feature becomes available once users update to a supported Teams client build.
  • Optionally notify users of this improvement.
  • Update internal documentation if it references client restarts for time zone changes.

Compliance considerations

No compliance considerations identified. Review as appropriate for your organization.

What changed

Between archive captures, newest first

The archive supplies one version of this notice.

No related evidence found in this installation's recent collection. This does not establish that no announcement exists.

Not confirmed here

What this page cannot tell you
  • Whether your tenant is affected: this is Microsoft's notice, not a check of your settings.
ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 27 Oct 16:49 UTC · 271 of 272 readable · 269 fully read · documentation 469/469 current