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 07:24 UTC Customize Public modeDiscuss ChangeIntel on Discord

Microsoft Teams: Native Bluetooth call controls using hands-free protocol for multiple peripheral devices

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

Rollout

Roadmap
475853

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 25 Apr 2025 mid-April 2025 → mid-May 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 April 25, 2025: We have updated the timeline below. Thank you for your patience. Coming soon for Microsoft Teams: When you have several peripheral devices connected to Teams, the one you use to answer a call will temporarily become the main device that will sync with Teams when using the device's buttons. After the call, the original device selected in Teams settings will take over again as the main device. After this rollout, users can use multiple native Bluetooth devices can be confident that call controls will function correctly with all of them. This message applies to Teams for Windows desktop. This message is associated with Microsoft 365 Roadmap ID 475853. When this will happen: Targeted Release: We will begin rolling out early March 2025 and expect to complete by late March 2025. General Availability (Worldwide, GCC, GCC High): We will begin rolling out mid-March 2025 and expect to complete by mid-May 2025 (previously mid-April). How this will affect your organization: After this rollout, users will be able to switch between their connected peripheral devices when answering a call without manually changing the selected device in Teams settings.  This change will be available by default. What you need to do to prepare: This rollout will happen automatically by the specified date with no admin action required before the rollout. You may want to notify your users about this change and update any relevant documentation. Learn more: Phones and Devices for Microsoft Teams - Microsoft Teams | Microsoft Learn Personal peripherals for Microsoft Teams - Microsoft Teams | Microsoft Learn

What changed

Between archive captures, newest first
  1. Updated March 3,April 25, 2025: We have updated the content.timeline below. Thank you for your patience. Coming soon for Microsoft Teams: When you … We will begin rolling out mid-March 2025 and expect to complete by mid-April 2025.mid-May 2025 (previously mid-April). How this will affect your organization: After this rollout, users will be …

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

    Updated March 3, 2025: We have updated the content. Thank you for your patience. Coming soon for Microsoft Teams: When you have several peripheral devices connected … Phones and Devices for Microsoft Teams - Microsoft Teams | Microsoft Learn Before rollout, we will update this post with new documentationPersonal peripherals for Microsoft Teams - Microsoft Teams | Microsoft Learn

  2. · 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 07:24 UTC · 272 of 272 readable · 270 fully read · documentation 469/469 current