Public mode

No tenant, Graph, or device access. Every item links to its source. What this means

Some sources or documents need attention: 258/260 feeds/APIs · 417/444 docs · checked 21:28 UTC Customize Public modeDiscuss ChangeIntel on Discord

(Updated) Microsoft Teams: Recently used emojis sync across devices

Rollout

Ends
30 Nov 2026
Roadmap
554927
Platforms
Android, Desktop, iOS, Mac, Web

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, with its sections, lists and tables; source markup removed

Updated September 22, 2026: We have updated the timeline. Thank you for your patience.

Introduction

We’re releasing an improvement to Microsoft Teams that syncs your recently used emojis and reactions across devices. With this update, users will see the same set of “recently used” emojis when using Teams on Android, iOS, Mac, Windows desktop, and Teams for the web, creating a more consistent and seamless experience when communicating across chats and channels. This enhancement aligns with customer feedback requesting a unified emoji experience across platforms.

This message is associated with Microsoft 365 Roadmap ID 554927.

When this will happen

  • Targeted Release: We expect to complete rollout by mid-July 2026 (previously mid-June).
  • General Availability (Worldwide): We will begin rolling out in mid-July 2026 (previously mid-June) and expect to complete in late July 2026 (previously late June).
  • General Availability (GCC and GCCH): We will begin rolling out in mid-July 2026 (previously mid-June) and expect to complete by end of October 2026 (previously mid-September).
  • General Availability (DoD): We will begin rolling out in mid-August 2026 (previously mid-July) and expect to complete by end of October 2026 (previously mid-September).

How this affects your organization

Who is affected

  • All Microsoft Teams users across supported clients.

What will happen

  • Recently used emojis and reactions will sync across devices.
  • Users will see the same “recently used” list regardless of which Teams client they use.
  • The feature will be enabled by default; no configuration is required for rollout.
  • Existing Teams admin settings and messaging policies will continue to apply.
  • There is no impact to message flow, data storage, compliance boundaries, or customer data pathways.

What you can do to prepare

No action is required. This update will roll out automatically.

Admins may optionally:

  • Inform helpdesk or support teams about this user experience update.
  • Update internal documentation if you reference emoji behavior or Teams UI details.
  • Review your Messaging settings and Messaging policies if you manage custom emoji usage.

Learn more about emoji and reaction usage in Microsoft Teams: Send an emoji, GIF, or sticker in Microsoft Teams | Microsoft Support

Compliance considerations

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

This feature does not introduce new data storage, processing changes, AI/ML capabilities, communication pathways, admin reporting changes, or modifications to Purview‑governed workflows.

What changed

Between the versions this installation saw, newest first
  1. Only details this page does not show changed.

  2. Only details this page does not show changed.

  3. Only details this page does not show changed.

  4. Only details this page does not show changed.

  5. Only details this page does not show changed.

  6. · 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.

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.
  • Versions before 19 Oct 2026: this installation first saw the notice after Microsoft posted it.
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 19 Oct 21:28 UTC · 258 of 260 readable · 256 fully read · documentation 417/444 current