MC1187801 - Microsoft Teams - Native MacOS screen and window sharing in Teams meetings

Message Center

Summary

Microsoft Teams will introduce an opt-in native macOS screen and window sharing feature using Apple's APIs, starting early December 2025 for targeted release and general availability by mid-May 2026. It is disabled by default, requires no app restart, and improves performance for Mac users in Teams meetings.

Last Updated

Mar 17, 2026

Published Nov 18, 2025

View version history

Service

Microsoft Teams

Tag

Updated message
New feature
User impact
Admin impact

Platforms

Mac

More information

Updated March 17, 2026: We have updated the timeline. Thank you for your patience. 

As part of our ongoing commitment to delivering a polished, platform-native experience for Mac users, Microsoft Teams is introducing native screen and window sharing capabilities tailored specifically for macOS. This opt-in experience leverages Apple’s macOS native screen sharing APIs, allowing users to share their screen or window directly from macOS during Teams meetings.

This message is associated with Microsoft 365 Roadmap ID 502523.

When this will happen:
  • Targeted Release: Begins early-December 2025, completes mid-December 2025.
  • General Availability
    • Worldwide and GCC: Begins early January 2026, completes by mid-May 2026 (previously mid-January).
    • GCC High and DoD: Begins mid-January 2026, completes by late May 2026 (previously late January).
How this affects your organization:

Who is affected: Mac users participating in Teams meetings across Microsoft 365 tenants.

What will happen:

  • Users will be able to opt in to native macOS screen and window sharing via Teams settings.
  • The feature is disabled by default and must be enabled by the user.
  • No application restart is required after enabling.
  • The experience uses macOS native APIs for improved performance and integration.
What you can do to prepare:
  • Notify your macOS users about this new capability.
  • Update internal training materials and documentation as needed.
  • No admin action is required unless you wish to communicate or document the change internally.
Compliance considerations:

No compliance considerations identified, review as appropriate for your organization.

Version history

2 versions tracked

Updated 1 time since Nov 18, 2025. Microsoft Message Center only ever shows the current version; this archive preserves the history.

Compare any two versions

From
To
  1. Mar 17, 2026 · 04:36 PMLatest · v2

    Changed: Body, Tags, End date

  2. Nov 18, 2025 · 08:56 PMOriginal · v1

    Changed: Initial version