Microsoft Teams: Shared call history in Queues app

Microsoft Teams Queues app will introduce shared call history for queue members to view all call events. Rolling out January–February 2026, the feature is disabled by default and requires Teams Premium license and admin enablement. Tenant migration of call history is not supported initially.

We’re introducing shared call history in the Microsoft Teams Queues app. This feature provides queue members with a unified view of all call events—missed, incoming, and outgoing—within a call queue. By enabling shared history, teams can access consistent, up-to-date information, follow up efficiently, and improve operational responsiveness.

user settingsView image in new tab

This message is associated with Roadmap ID 530579 and applies to Teams for Windows desktop and Teams for Mac desktop.

When this will happen:

  • Targeted Release: Rolling out early January 2026, expected completion by mid-January 2026.
  • General Availability (Worldwide): Rolling out mid-January 2026, expected completion by early February 2026.

How this affects your organization:

Who is affected:

What will happen:

What you can do to prepare:

Learn more:

    Compliance considerations:

    • Organizations using Microsoft Teams Queues app on desktop, web, and Mac.
    • Users with appropriate permissions and a Teams Premium license.
    • Queue members will be able to view shared call history for all missed, incoming, and outgoing calls.
    • Feature is disabled by default; admins must enable it in Teams Admin Center (TAC).
    • Admins can grant shared call history access to all queue members or restrict access to authorized users only.
    • Known limitation: Tenant migration is not supported for Queues call history. If your organization moves to a new region, existing history will not transfer; a new history will begin. Support for migration will be added in a future update.
    • Enable shared call history in Teams Admin Center.
    • Configure permissions for queue members or authorized users.
    • Communicate this change to your helpdesk and affected users.
    • Update internal documentation to reflect this feature.

    No compliance considerations identified; review as appropriate for your organization.

    Message ID: MC1188999


    Comments are closed.


    I've been working with Microsoft Technologies over the last ten years, mainly focused on creating collaboration and productivity solutions that drive the adoption of Microsoft Modern Workplace.

    %d bloggers like this: