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 08:08 UTC Customize Public modeDiscuss ChangeIntel on Discord

Microsoft Teams: Regional Settings Separation

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

Rollout

Roadmap
498895

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

Schedule dates changed in the text

Date phrases in schedule sentences differ between the versions this installation saw
  • Seen 3 Sep 2025 late September 2025

Read from date phrases in Microsoft's text, not from notice metadata. A changed phrase can be a moved rollout, a new milestone or just rewording; "What changed" below shows which.

What the notice says

Microsoft’s text, with source markup removed
Updated September 3, 2025: We have updated the timeline. Thank you for your patience. Introduction We're introducing the Regional Settings Separation feature in Microsoft Teams to improve the globalization experience and provide users with greater control over their regional preferences. With this update, users can independently configure UI language, date format, and time format within Teams, either by syncing with their operating system or manually selecting their preferences. This change helps eliminate synchronization issues and ensures a more personalized and consistent experience across devices. This update is associated with Microsoft 365 Roadmap ID 498895. When this will happen Targeted Release: Begins early August 2025; expected to complete by mid-August 2025. General Availability (Worldwide): Begins mid-August 2025; expected to complete by late August 2025. General Availability (GCC, GCC High, DoD): Begins mid-August 2025; expected to complete by late September 2025. How this affects your organization Once this feature is rolled out, users on Teams Desktop Client for Windows and Mac will be able to view and modify their date and time format settings directly in Teams by navigating to: Settings > General > Language and regional formats By default, Teams will continue to follow the operating system settings unless users choose to override them manually. This update does not change existing behavior unless users take action. What you can do to prepare No admin action is required. The feature will be available automatically once users update to the supported Teams client build. There are no admin controls or configuration options for this feature. You may consider notifying your users about this update to help them take advantage of the new customization options. Compliance considerations No compliance considerations identified, review as appropriate for your organization.

What changed

Between archive captures, newest first
    • Tags Feature update → Updated message, Feature update

    Updated September 3, 2025: We have updated the timeline. Thank you for your patience. Introduction We're introducing the Regional Settings Separation feature in Microsoft Teams to … (GCC, GCC High, DoD): Begins mid-August 2025; expected to complete by late AugustSeptember 2025. How this affects your organization Once this feature is rolled out, …

  1. · first version seen

Linked documentation

Microsoft pages the notice links to

The notice links to no Microsoft Learn or Support page that this installation reads.

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 08:08 UTC · 271 of 272 readable · 270 fully read · documentation 469/469 current