MC1009927 - Microsoft Teams: User setting to optimize battery life in older Bluetooth headsets for the Walkie Talkie app for Android

NOTE: If your organization does not support Android devices, you can safely ignore this message. Coming soon for the Walkie Talkie app in Microsoft Teams: New user Connection Settings for Headset microphones that are designed to optimize battery life for older Bluetooth headsets.

This message applies to Teams on Android only.

This message is associated with Microsoft 365 Roadmap ID 476733.

When this will happen:

General Availability (Worldwide): We will begin rolling out early March 2025 and expect to complete by late March 2025.

How this will affect your organization:

When a Bluetooth headset is connected to the Walkie Talkie app, the new Connection Settings for Headset microphones use SCO (Synchronous Connection-Oriented) to control whether the microphone remains constantly connected or disconnects after a period of inactivity. This helps in reducing battery drain by allowing the headset to disconnect when not in use and reconnect when needed. The user control feature allows users to set a timeout period after which the Bluetooth headset will automatically disconnect if there is no activity.

When the SCO setting is turned on, users may experience a slight delay in transmission as the headset reconnects. However, once the headset is reconnected, users will hear a sound indicating that they can start transmitting on the app. This brief delay is a small trade-off for the substantial battery savings on older Bluetooth headsets.

This setting update is not needed for newer Bluetooth headsets as the battery life is already optimal.

This change will be available by default.

What you need to do to prepare:

Learn more: The section called Get insight into Walkie Talkie usage and performance in Manage the Walkie Talkie app in Microsoft Teams - Microsoft Teams | Microsoft Learn

This rollout will happen automatically by the specified date with no admin action required before the rollout. Review your current configuration to determine the impact for your organization. You may want to notify your users about this change and update any relevant documentation.