ChangeIntelIT change radar
Public mode

No access to your tenant or devices. Every item links to its source. What this means

Some sources, documents or advisories need attention: 272/272 feeds/APIs · 469/469 docs · 7/9 advisories · checked 03:32 UTC Customize Public modeDiscuss ChangeIntel on Discord
MC1186374 Plan for changeUpdated messageNew featureUser impactAdmin impact

Microsoft Teams: Miracast support for Teams Rooms on Windows (Teams Rooms Pro only)

Microsoft 365 Message Center Archive by Merill Fernando · Microsoft may not have sent this notice to your tenant.
Microsoft Teams
Microsoft 365 admin center

Rollout

Roadmap
506748

Rollout dates are often only in the text. When Microsoft moves them, the change shows under "What changed".

Schedule dates changed in the text

Date phrases in schedule sentences differ between the versions this installation saw
  • Seen 6 May 2026 early May 2026
  • Seen 27 Feb 2026 mid-March 2026, end of March 2026, mid-April 2026 → early May 2026, mid-May 2026, late May 2026
  • Seen 22 Jan 2026 mid-February 2026, end of February 2026 → mid-March 2026, mid-April 2026
  • Seen 10 Dec 2025 mid-January 2026, end of January 2026 → end of February 2026, end of March 2026

Read from date phrases in Microsoft's text, not from notice metadata. A changed phrase can be a moved rollout, a new milestone or just rewording; "What changed" below shows which.

What the notice says

Microsoft’s text, with source markup removed
Updated May 6, 2026: We have updated the timeline. Thank you for your patience.  Introduction To enhance wireless content sharing in meeting spaces, Microsoft Teams Rooms on Windows devices will soon support Miracast. This complements existing options like Teams Cast and HDMI ingest and is available for devices including touch boards. This feature is exclusive to Teams Rooms Pro. This message is associated with Roadmap ID 506748. When this will happen: Targeted release: We will begin rolling out in mid-May 2026 (previously early May) and expect to complete by mid-May 2026 (previously end of March). General Availability: We will begin rolling out mid-May 2026 (previously end of March) and expect to complete by late May 2026 (previously mid-April). How this affects your organization: Who is affected: Admins managing Teams Rooms on Windows devices with Teams Rooms Pro licenses. What will happen: Miracast will be available as a wireless sharing option in Teams Rooms on Windows. The feature will be OFF by default and can be enabled via a tenant-wide toggle in the IT admin portal. Laptop devices must support Miracast to use this feature. No impact to end-user workflow unless enabled by admin. What you can do to prepare:Review your Teams Rooms device compatibility with Miracast. Enable the feature via the IT admin portal if desired. Communicate the availability of Miracast to helpdesk and meeting room support staff. Update internal documentation to reflect the new sharing option. Compliance considerations: No compliance considerations identified, review as appropriate for your organization.

What changed

Between archive captures, newest first

  1. Updated February 27,May 6, 2026: We have updated the timeline. Thank you for your patience.  Introduction … When this will happen: Targeted release: We will begin rolling out in early May mid-May 2026 (previously mid-March)early May) and expect to complete by mid-May 2026 (previously end of March). General …

  2. Updated January 22,February 27, 2026: We have updated the timeline. Thank you for your patience.  Introduction … When this will happen: Targeted release: We will begin rolling out in mid-Marchearly May 2026 (previously mid-February)mid-March) and expect to complete by end of March mid-May 2026 (previously end of February).March). General Availability: We will begin rolling out end of March mid-May 2026 (previously end of February)March) and expect to complete by mid-Aprillate May 2026 (previously end of March).mid-April). How this affects your organization: Who is affected: Admins managing Teams Rooms …

  3. Updated December 10, 2025:January 22, 2026: We have updated the timeline. Thank you for your patience.  Introduction To … When this will happen: Targeted release: We will begin rolling out in mid-Februarymid-March 2026 (previously mid-January)mid-February) and expect to complete by end of FebruaryMarch 2026 (previously end of January).February). General Availability: We will begin rolling out end of FebruaryMarch 2026 (previously end of January)February) and expect to complete by end of March 2026 (previously mid-February).mid-April 2026 (previously end of March). How this affects your organization: Who is affected: Admins managing Teams Rooms …

    • Tags New feature, User impact, Admin impact → Updated message, New feature, User impact, Admin impact

    Updated December 10, 2025: We have updated the timeline. Thank you for your patience.  Introduction To enhance wireless content sharing in meeting spaces, Microsoft Teams Rooms … When this will happen: Targeted release: We will begin rolling out in mid-Januarymid-February 2026 (previously mid-January) and expect to complete by end of January 2026.February 2026 (previously end of January). General Availability: We will begin rolling out in end of JanuaryFebruary 2026 (previously end of January) and expect to complete by mid-February 2026.end of March 2026 (previously mid-February). How this affects your organization: Who is affected: Admins managing Teams Rooms …

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

No related evidence found in this installation's recent collection. This does not establish that no announcement exists.

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.
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 27 Oct 03:32 UTC · 272 of 272 readable · 270 fully read · documentation 469/469 current

No accounts or analytics; your preferences stay in your browser. Information, not advice. ChangeIntel is an independent tool and is not affiliated with or endorsed by Microsoft, Apple, Google, Broadcom (VMware), Jamf, Oracle, Mozilla, or any other vendor it covers. Product names are trademarks of their owners. Built by Evotec.