Published Jul 8, 2024
Microsoft Teams is introducing new skin tone settings and reactions, allowing users to set a preferred skin tone for emojis and reactions within the app. The rollout timeline has been updated, with completion expected from early November to late December 2024, depending on the release stage. No admin action is required for the update.
Updated December 6, 2024: We have updated the rollout timeline below. Thank you for your patience.
With skin tone settings and reactions in Microsoft Teams, users will be able to set a preferred skin tone for relevant emojis and reactions. Each user can change their own skin tone setting in the Teams app Settings > Appearance and accessibility menu or in the emoji/reaction menu on Desktop or web. The skin tone rollout will apply to emojis and reactions in chats, channels, and meetings on all Teams platforms (Teams for Desktop, Teams for web, Teams for Mac, and Teams Mobile).
This message is associated with Microsoft 365 Roadmap ID 323766.
When this will happen:
Targeted Release: We will begin rolling out late October 2024 (previously mid-October) and expect to complete by early November 2024 (previously late October).
General availability (Worldwide, GCC): We will begin rolling out early November 2024 (previously late October) and expect to complete by mid-November 2024 (previously early November).
General availability (GCC High, DoD): We will begin rolling out mid-November 2024 (previously mid-November) and expect to complete by late December (previously late November).
How this will affect your organization:
Changing skin tone in the emoji menu in Teams for Desktop:
Changing skin tone in Teams Settings > Appearance and accessibility in Teams for Desktop:
Changing skin tone in Teams Settings > Appearance on Teams Mobile:
The selected skin tone appears in reactions in chats, channels, and meetings:
What you need to do to prepare:
This rollout will happen automatically by the specified date with no admin action required. You may want to notify your users about this change and update any relevant documentation as appropriate.
We will update this post before rollout with revised documentation.