Teams Phone Agent "Agents & queues" option not visible for Teams Administrator but visible for Global Administrator in same tenant

Shalev Bokobza 0 Reputation points
2026-08-31T07:50:57.54+00:00

In our tenant, when configuring an Auto Attendant call flow (Play menu options > Set menu options > Redirect to), the destination dropdown shows the newer options Tools and Agents & queues (tagged "New") for one user, but these options do not appear for another user in the same tenant.

The key difference between the two users is their directory role:

  • User A (options ARE visible): Global Administrator + Privileged Role Administrator (permanent)
  • User B (options NOT visible): Teams Administrator + User Administrator (PIM-activated, active)

Both users are in the same tenant. User B has a Microsoft Copilot Studio User License and Power Automate assigned.

My questions:

  1. Is visibility of the Agents & queues / Teams Phone Agent options in the Auto Attendant destination menu gated to Global Administrator, or should Teams Administrator be sufficient to see and configure them?
  2. Is this feature currently limited to tenants enrolled in the Frontier Public Preview program, and if so, does enrollment affect per-user visibility or only tenant-level availability?
  3. What is the exact minimum licensing/role combination required for a non-Global-Admin user to see and use the Agents & queues (Copilot Studio voice agent) routing target, so we can follow least-privilege and avoid assigning Global Administrator?

We want to delegate this to a Teams Administrator without granting Global Administrator. Any clarification on whether this is a role gating, a preview rollout behavior, or a licensing requirement would be appreciated.

Thank you.

Microsoft Teams | Microsoft Teams for business | Settings | Other
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Darren Bruce 1,315 Reputation points Independent Advisor
    2026-08-31T09:15:14.0433333+00:00

    Dear @Shalev Bokobza,

    Regarding to your questions, here are some information you can refer to:

    1/Is visibility of the Agents & queues / Teams Phone Agent options in the Auto Attendant destination menu gated to Global Administrator, or should Teams Administrator be sufficient to see and configure them?

    Microsoft does not require the Global Administrator role. The Teams Administrator role is considered a valid administrative role for Teams Phone Agent.

    2/Is this feature limited to tenants enrolled in the Frontier Public Preview program?

    Yes. Teams Phone Agent is currently available only to tenants participating in the Frontier Public Preview. Additionally, the tenant must have access to the Teams Phone Agent integration preview enabled by Microsoft.

    Does Frontier Public Preview enrollment affect per-user visibility or only tenant-level availability?

    Current documentation only confirms the requirement for tenant-level enablement. Microsoft has not yet released documentation regarding whether the preview affects per-user visibility.

    3/What is the minimum licensing/role combination for a non-Global-Admin user?

    The requirements announced by Microsoft include:

    Copilot Studio tenant entitlement

    Copilot Studio user license

    Tenant enabled for Teams Phone Agent preview

    Microsoft has not currently published a detailed role matrix for the "Agents & queues" menu, but there is no documentation indicating that the Global Administrator role is a mandatory requirement.

    For reference

    Setup - Teams Phone Agent - Agents and Queues

    Planning - Overview of voice applications

    If the answer is helpful, please click "Yes". If you have extra questions about this answer, please click "Comment".   

    Note: Please follow the steps in the forum documentation to enable e-mail notifications if you want to receive the related email notification for this thread. 

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.