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: 270/272 feeds/APIs · 469/469 docs · 7/9 advisories · checked 00:25 UTC Customize Public modeDiscuss ChangeIntel on Discord

Teams Phone call transfer improvements

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

Rollout

Roadmap
561028

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

What the notice says

Microsoft’s text, with source markup removed
Introduction Microsoft Teams is improving the call transfer experience on desktop (Windows and Mac) to make transferring calls faster and more intuitive. This update simplifies the workflow, reduces the number of steps required, and helps users quickly find the right transfer target. This message is associated with Roadmap ID 561028. When this will happen: Targeted Release: We began rolling out in early June 2026 and expect to complete by early June 2026. General Availability (Worldwide): We will begin rolling out in late June 2026 and expect to complete by late June 2026. How this affects your organization: Who is affected: All Microsoft Teams users on desktop (Windows and Mac) using Teams Phone What will happen: Transfer and Consult transfer are now separate top-level actions in the call controls. Previously, both options were grouped under a single Transfer button that opened a dropdown menu, requiring two clicks to initiate either action. Transfer and Consult transfer buttons are now available directly in the call controls, reducing each to a single click. Screenshot: Teams call screen showing an active call; the call control bar at the top shows that the Consult and Transfer buttons are available during the call: Suggested transfer targets. When a user opens the transfer dialog, they’ll see a list of suggested contacts based on their transfer history, displayed as quick-select options beneath the search bar. This helps users who frequently transfer calls to the same people quickly find the right person without searching. Suggestions are scoped to the user’s primary line and do not include transfers made on behalf of delegate or shared lines. Updated default transfer behavior. Based on user feedback, the default transfer type has changed from safe transfer to blind transfer. With blind transfer, the call is handed off immediately, and the user can move on without waiting for the target to answer. Previously, the default was safe transfer, which kept the call window open until the target picked up and rang back if the target did not answer. Safe transfer is still available by enabling the “Ring Back” toggle in the transfer dialog. What you can do to prepare: No admin action is required before the rollout. You may consider the following: Inform users about the updated call transfer experience. Update internal training materials or documentation. Prepare helpdesk teams to support user questions. Learn more: Transfer a call in Microsoft Teams | Microsoft Support (will be updated before rollout) Compliance considerations: No compliance considerations identified, review as appropriate for your organization.

What changed

Between archive captures, newest first

The archive supplies one version of this notice.

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 00:25 UTC · 270 of 272 readable · 268 fully read · documentation 469/469 current