MC1256307: Microsoft Teams Syncs Recently Used Emojis and Reactions Across Devices

MWPRO IMPACT SCORE
OPERATIONAL IMPACT
23
0 25 50 75 100
LOW IMPACT • MONITOR ONLY
Recommended Action:
No immediate action needed. Keep this on your radar.
What is MWPro Impact Score? Watch our 60‑second explainer

Primary Audience

Microsoft 365 AdminsTeams AdminsIT ManagersService Owners
Why this score?
AI Confidence
HIGH
Enough detail is available to trust this assessment.
Assessment Reasoning
The update only shifts rollout dates and introduces an automatic user experience improvement. Admin impact is low as no configuration or policy change is required, though helpdesk awareness and documentation updates may be useful. Users will notice a minor cross-device consistency improvement, but there is no disruption or training need. Urgency is low because it is informational and requires no action beyond optional awareness.
20
🛡️ Admin Impact
30
👥 User Impact
25
Urgency
15
🔧 Effort
ℹ️ WHAT YOU NEED TO KNOW
📌

AT A GLANCE

Teams will sync recently used emojis and reactions across all devices for a consistent experience. The feature is on by default.
👥

END USERS

Users will see the same ‘recently used’ emojis across all Teams clients.
🛡️

IT ADMINS

No action needed, but you may want to inform support teams and update documentation if it references emoji behaviour.
📅

ROLLOUT TIMELINE

Rolling out:
In progress

📢 Official Microsoft Message Center Announcement


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

Updated September 2, 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 mid-September 2026 (previously mid-August).
  • General Availability (DoD): We will begin rolling out in mid-August 2026 (previously mid-July) and expect to complete by mid-September 2026 (previously late August).

[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. 

Source: Microsoft Message Center • Analysed by MWPro

<<< [MC1256307] Archive
Tooltip: View earlier revisions of this post

Share This Update