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 · 8/9 advisories · checked 09:15 UTC Customize Public modeDiscuss ChangeIntel on Discord

Microsoft Teams: Enhanced peripheral data in Pro Management portal reports for BYOD spaces

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

Rollout

Roadmap
493319

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 11 Aug 2026 early August 2026 → end of August 2026
  • Seen 28 Jul 2026 late July 2026 → early August 2026
  • Seen 23 Jun 2026 early June 2026, mid-June 2026 → late June 2026, late July 2026
  • Seen 29 Apr 2026 early May 2026, mid-May 2026 → early June 2026, mid-June 2026
  • Seen 26 Mar 2026 early April 2026, mid-April 2026 → early May 2026, mid-May 2026
  • Seen 16 Jan 2026 late February 2026, early March 2026 → early April 2026, mid-April 2026
  • Seen 28 Oct 2025 early November 2025, late November 2025 → late February 2026, early March 2026
  • Seen 24 Sep 2025 early October 2025, late October 2025 → early November 2025, late November 2025
  • Seen 27 Aug 2025 early September 2025, late September 2025 → early October 2025, late October 2025
  • Seen 16 Jun 2025 early July 2025, late July 2025 → early September 2025, late September 2025

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 August 11, 2026: We have updated the timeline. Thank you for your patience.   We’re adding new peripheral health reporting capabilities to the Pro Management portal, enabling admins to proactively monitor device issues in bring your own device (BYOD) rooms and desks. These reports help identify when peripherals are faulty, missing, moved, or undetectable by a PC—allowing admins to take action before users report problems. Reports for rooms require a Teams Shared Devices license. Desk reporting is currently in public preview. This change is associated with Microsoft 365 Roadmap ID: 493319 When this will happen: General Availability (Worldwide and GCC): Rollout will begin in late June 2026 (previously early June) and is expected to complete by end of August 2026 (previously early August). How this affects your organization: Admins can now use peripheral status data to detect hardware issues in BYOD rooms and desks before they impact users. This proactive monitoring can reduce support tickets and improve meeting space reliability. Reports for rooms require a Teams Shared Devices license. Reports for desks are available in public preview and do not yet require a license. What you can do to prepare: To ensure accurate peripheral status reporting: Use multiple peripherals in each room or desk setup. The system compares expected device pairings (e.g., if Peripheral A and B are usually connected together, but A is missing, it will be flagged). Simplify connectivity for users by using a single cable solution to connect all peripherals. Ensure rooms and desks are bookable and have associated peripherals—this enables the Teams desktop client to send the necessary telemetry. Peripheral association can be done manually or automatically. Compliance considerations: Does the change alter how existing customer data is processed, stored, or accessed? Maybe (device telemetry is used for reporting)

What changed

Between archive captures, newest first
  1. Updated June 28August 11, 2026: We have updated the timeline. Thank you for your patience.   We’re … late June 2026 (previously early June) and is expected to complete by earlyend of August 2026 (previously late July).early August). How this affects your organization: Admins can now use peripheral status data …

  2. Updated June 2328 2026: We have updated the timeline. Thank you for your patience.   We’re … late June 2026 (previously early June) and is expected to complete by late Julyearly August 2026 (previously mid-June).late July). How this affects your organization: Admins can now use peripheral status data …

  3. Updated April 29,June 23 2026: We have updated the timeline. Thank you for your patience.   We’re … this will happen: General Availability (Worldwide and GCC): Rollout will begin in earlylate June 2026 (previously  early May) June) and is expected to complete by mid-Junelate July 2026 (previously mid-May). mid-June). How this affects your organization: Admins can now use peripheral status data …

  4. Updated March 26,April 29, 2026: We have updated the timeline. Thank you for your patience.   We’re … will happen: General Availability (Worldwide and GCC): Rollout will begin in early MayJune 2026 (previously early April)May) and is expected to complete by mid-Maymid-June 2026 (previously mid-April).mid-May). How this affects your organization: Admins can now use peripheral status data …

  5. Updated January 16,March 26, 2026: We have updated the timeline. Thank you for your patience.   We’re … will happen: General Availability (Worldwide and GCC): Rollout will begin in early AprilMay 2026 (previously late February)early April) and is expected to complete by mid-Aprilmid-May 2026 (previously early March).mid-April). How this affects your organization: Admins can now use peripheral status data …

  6. Updated October 28, 2025:January 16, 2026: We have updated the timeline. Thank you for your patience.   We’re adding … this will happen: General Availability (Worldwide and GCC): Rollout will begin in late Februaryearly April 2026 (previously early November 2025) late February) and is expected to complete by early March mid-April 2026 (previously late November 2025).early March). How this affects your organization: Admins can now use peripheral status data …

  7. Updated September 24,October 28, 2025: We have updated the timeline. Thank you for your patience.   We’re … this will happen: General Availability (Worldwide and GCC): Rollout will begin in late February 2026 (previously early November 20252025) and is expected to complete by early March 2026 (previously late November 2025.2025). How this affects your organization: Admins can now use peripheral status data …

  8. Updated August 27,September 24, 2025: We have updated the timeline. Thank you for your patience.    We’re adding new peripheral health reporting capabilities to the Pro Management portal, … will happen: General Availability (Worldwide and GCC): Rollout will begin in early OctoberNovember 2025 and is expected to complete by late OctoberNovember 2025. How this affects your organization: Admins can now use peripheral status …

  9. Updated June 16,August 27, 2025: We have updated the timeline below. timeline. Thank you for your patience. We’re adding new peripheral health reporting capabilities … will happen: General Availability (Worldwide and GCC): Rollout will begin in early SeptemberOctober 2025 (previously early July) and is expected to complete by late September 2025 (previously late July).October 2025. How this affects your organization: Admins can now use peripheral status data …

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

    Updated June 16, 2025: We have updated the timeline below. Thank you for your patience. We’re adding new peripheral health reporting capabilities to the Pro Management portal, … will happen: General Availability (Worldwide and GCC): Rollout will begin in early JulySeptember 2025 (previously early July) and is expected to complete by late July 2025.September 2025 (previously late July). How this affects your organization: Admins can now use peripheral status data …

  10. · 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 26 Oct 09:15 UTC · 272 of 272 readable · 270 fully read · documentation 469/469 current