Back to latest version
Comparing May 19, 2026 latest (May 28, 2026) Swap

MC1287373 - Microsoft Teams introduces efficiency mode to improve app responsiveness

Message Center

Metadata at latest

Last Updated

May 28, 2026

Published Apr 21, 2026

Service

Microsoft Teams

Tag

Updated message
New feature
User impact

Platforms

Desktop
Mac

Metadata

No tracked metadata fields changed between these versions.

Body changes

removed textadded text

Updated May 19,28, 2026: We have updated the timeline.content. Thank you for your patience. 

Introduction

Microsoft Teams is introducing Efficiency Mode, a performance-optimized experience designed for hardware-constrained devices. This change improves app responsiveness and meeting quality by adjusting resource usage based on device capabilities.

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

When this will happen:

General Availability (Worldwide): Rollout begins in late May 2026 (previously early May) and is expected to complete by end of May 2026 (previously mid-May).

How this affects your organization:

Who is affected:

  • Users running Microsoft Teams on hardware‑constrained devices (for example, devices with limited CPU, memory)

What will happen:

  • Efficiency Mode is enabled by defaulton eligible devices.
  • An Efficiency Mode indicator appears in the Teams app title bar.
  • user settings

  • When enabled:
    • Video resolution sent from the user’s camera is dynamically adjusted in meetings.
    • The app launches without a pre-selected chat and shows a static image in the message pane.
  • Users can opt out via Settings > General > “Never use efficiency mode.”
  • To align with the new standardized approach of how indicators are displayed in the title bar, for VDI users the “Optimized” pill is replaced with the new icon.
  • user settings

What you can do to prepare:

  • No action is required if the default behavior works for your organization.
  • Consider informing helpdesk teams about the new mode and opt-out option.
  • Update internal documentation if applicable.

Compliance considerations:

Users can enable or disable the feature themselves. No other compliance considerations were identified.