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: 272/272 feeds/APIs · 469/469 docs · 8/9 advisories · checked 19:51 UTC Customize Public modeDiscuss ChangeIntel on Discord

Autocorrect in Microsoft Teams compose

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

Rollout

Roadmap
534487

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

Autocorrect is coming to Microsoft Teams compose. Commonly misspelled words will now be automatically corrected while composing messages.

This message is associated with Roadmap ID 534487 and applies to Teams for Windows desktop and Teams for Mac desktop.

When this will happen

  • Targeted Release: We will begin rolling out early December 2025 and expect to complete by mid-December 2025.
  • General Availability (Worldwide): We will begin rolling out mid-January 2026 and expect to complete by late January 2026.
  • General Availability (GCC High): We will begin rolling out mid-January 2026 and expect to complete by early February 2026.
  • General Availability (DoD): We will begin rolling out early February 2026 and expect to complete by mid-February 2026.

How this affects your organization

Who is affected: All Microsoft Teams users composing messages in chat or channels.

What will happen

  • Commonly misspelled words will be automatically corrected during message composition.
  • The feature is enabled by default; no admin configuration is required.
  • Users can disable this feature by going to Settings > General > Editor spellcheck, then switching off the Correct words while typing toggle.

What you can do to prepare

  • No action is required to enable this feature.
  • Consider updating internal documentation to reflect this new capability.
  • Communicate this change to helpdesk staff to reduce potential support inquiries.

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.

Learn more

Links from the notice and their documentation checks

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