Published Oct 23, 2024
The message details an update on call hold synchronization between Microsoft Teams and Skype for Business, with a revised rollout timeline. It explains that calls in one service will automatically go on hold when answering a call in the other, requiring Teams client version 24261.1100.3128.2662 or greater. Users must enable this feature by adjusting specific group policy registry keys. Rollouts will occur from mid-October to early December 2024, depending on the service availability area.
Updated December 6, 2024: We have updated the rollout timeline below. Thank you for your patience.
Improving interop between the new Microsoft Teams client and Skype for business
Currently when making or receiving a call in the new Microsoft Teams client while an existing Skype for Business (SfB) call is ongoing, the call in Skype for Business does not automatically go on hold. The reverse scenario has the same problem.
When this will happen:
General Availability (Worldwide): We will begin rolling out mid-October 2024 and expect to complete by late October 2024.
General Availability (GCC): We will begin rolling out mid-October 2024 and expect to complete by late October 2024.
General Availability (GCC High): early November 2024 and expect to complete by mid-November 2024.
General Availability (DoD): We will begin rolling out mid-November 2024 and expect to complete by early December 2024 (previously late November).
How this affects your organization:
We have addressed this issue so that when the user is on a call in SfB and answers a call in Microsoft Teams the SfB call will go on hold. Similarly, if they are on a call in Teams and answer a call in SfB the Teams call will go on hold. The user must be using the new Microsoft Teams client version 24261.1100.3128.2662 or greater.
What you can do to prepare:
Once this feature is available it must be enabled following the steps below.