Share via

Unable to make outbound calls using “Call as Call Queue” in Teams Phone with Calling Plan

Rajasekar K 36 Reputation points
2026-04-22T12:13:20.4966667+00:00

We are using Microsoft Teams Phone with Calling Plan (Country Zone 1 - US) along with Teams Phone Resource Account license for Call Queue and Auto Attendant.

Scenario

Users are enabled with:

Teams Phone + Calling Plan license

Enterprise Voice enabled

Resource Accounts:

 Licensed with Teams Phone Resource Account

Assigned phone numbers

  Used for Call Queue and Auto Attendant

Call Queue:

Configured with agents

Conference mode enabled

Caller ID policy:

C onfigured to replace caller ID with Resource Account (Call Queue number)

Observed Behavior

When users make calls using “Call as myself”:

Call connects successfully

Caller ID is correctly masked with Call Queue number (via policy)

When users select from dial pad:

“Call as Test-Callqueue” or “Call as Test-Auto”

Call fails with error:

**“You are not set up to use this calling feature. Please contact your admin.”

Kindly help me on this.

**User's image

Microsoft Teams | Microsoft Teams for business | Meetings and calls | Other
0 comments No comments

2 answers

Sort by: Most helpful
  1. Rin-L 19,085 Reputation points Microsoft External Staff Moderator
    2026-04-22T14:14:22.4733333+00:00

    Hi @Rajasekar K,

    Thank you for laying out the scenario. I hope I can share a few ideas that may help explain what you’re seeing.

    Since this behavior is occurring after November 2025, it may be related to recent changes in how Microsoft handles outbound PSTN calls made on behalf of Call Queues or Auto Attendants. In some scenarios, outbound OBO (on‑behalf‑of) calls might not function as expected if the resource account is using a standard Calling Plan license.

    To support outbound calls when users choose Call as Call Queue or Call as Auto Attendant, it’s often recommended to assign a Pay‑As‑You‑Go Calling Plan to the resource account. This allows Microsoft Teams to meter and charge outbound calls on a per‑minute basis, which aligns more closely with OBO calling requirements in Call Queue or Auto Attendant scenarios. Depending on your tenant configuration, this plan can be added alongside, or in place of, the existing Calling Plan.

    You can refer: Plan for Teams Auto attendants and Call queues - Microsoft Teams | Microsoft Learn

    Additionally, it’s worth checking one more setting in your tenant. In the Microsoft 365 admin center, go to Billing > Your products, open the Teams Phone with Calling Plan license, and scroll to the very bottom. There you’ll see Phone service consumption. Please make sure this setting is switched to On, as it’s disabled by default and is required for consumption‑based calling scenarios like this. User's image

    If you have any updates, please leave a comment under this post. This is the best way for me to receive notifications and follow up with you promptly. 

    Thank you again for your understanding and cooperation.


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


  2. Q&A Assist
    2026-04-22T12:13:40.5033333+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    The failure when placing outbound calls as “Call as Test-Callqueue/Test-Auto” is caused by missing outbound calling capability on the resource accounts that are being used as the calling identity.

    For on‑behalf‑of outbound PSTN calls (including “Call as Call Queue/Auto Attendant”), the resource account whose number is used as caller ID must have:

    1. A Microsoft Teams Phone Resource Account license, and
    2. A PSTN connectivity entitlement attached to that resource account (Calling Plan, Operator Connect number, or Direct Routing policy), and
    3. For Calling Plan scenarios, from November 1, 2025 onward, a funded pay‑as‑you‑go Calling Plan or Communications Credits balance for those on‑behalf‑of calls.

    In the current configuration, agents can successfully call “as myself” and have the Call Queue number presented via Caller ID policy masking, but direct “Call as Call Queue/Auto Attendant” uses the resource account itself to originate the call. If that resource account does not have the required PSTN calling entitlement and funded pay‑as‑you‑go/Communications Credits, Teams returns the error “You are not set up to use this calling feature.”

    To fix this for Calling Plan usage:

    1. Ensure each Call Queue/Auto Attendant resource account used as a calling identity has:
      • Microsoft Teams Phone Resource Account license assigned.
      • A Calling Plan number, Operator Connect number, or Direct Routing voice routing policy assigned, as described under “Assign a calling ID (optional).”
    2. For Calling Plan numbers, add outbound funding for on‑behalf‑of calls:
      • Purchase a pay‑as‑you‑go Calling Plan or Communications Credits for the tenant.
      • Assign the funded pay‑as‑you‑go license or Communications Credits to the relevant resource accounts that are used for on‑behalf‑of outbound calls (Call Queues, Auto Attendants, and any resource accounts configured under Assign calling ID).
    3. Verify that the resource accounts used in the Assign calling ID section of the Call Queue configuration are exactly the ones that have the above licenses and PSTN configuration.

    After licenses and numbers are correctly assigned and funded, “Call as Test-Callqueue” and “Call as Test-Auto” will be able to originate outbound PSTN calls instead of failing with the feature‑not‑set‑up error.


    References:

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.