Almanac
Microsoft/teamsMicrosoft 365

Consultant-focused KB for Microsoft Teams: implementation notes, gotchas and configuration decisions beyond the official docs — across chat and collaboration, meetings, webinars and town halls, Teams Phone, PSTN connectivity (Direct Routing, Operator Connect, Calling Plans, Teams Phone Mobile), auto attendants, call queues and contact centre integration, Teams Rooms and devices, apps and extensibility, Copilot in Teams, administration and governance, security and compliance, network and call quality, and licensing — plus cross-cutting decision guides.

feature-licensing-resource-account-and-voice-app-outbound.mdv1 · history
CurrentApplies to Teams Phone · Teams PremiumUpdated 3 weeks agoSource Microsoft Learn ↗

What it does

Every resource account behind an auto attendant or call queue needs the Microsoft Teams Phone Resource Account licence — a zero-cost SKU that you still have to "buy". Outbound PSTN calls placed on behalf of that resource account need funded pay-as-you-go or Communications Credits on top, and the Queues app layer needs Teams Premium for its users.

Key facts

  • There's no charge for Teams Phone Resource Account licences, but you still go through the purchase flow (Marketplace > All products in the Microsoft 365 admin center for Web Direct).
  • Buy them through the same channel as the subscription that contains Teams Phone. An EA customer orders through the EA.
  • Every resource account must have the Resource Account licence, whether or not it ever gets a phone number.
  • The tenant needs at least one Teams Phone licence to enable Teams Phone Agent, Auto Attendant and Call Queue services.
  • Never assign Teams Phone Standard to a resource account, and never assign the Resource Account licence to a normal user.
  • A Microsoft Calling Plan isn't needed on a resource account unless it dials out.
  • Since 1 November 2025, Calling Plan licences on resource accounts no longer cover on-behalf-of outbound PSTN calls. A funded pay-as-you-go licence or Communications Credits is required for agents calling out as the queue, auto attendant/call queue forwarding to an external number, and similar outbound scenarios. Without it, those calls fail.
  • For Operator Connect or Direct Routing numbers, the equivalent outbound arrangement has to be set up with the carrier, or outbound calls for agents, auto attendants, call queues and API scenarios fail.
  • All Queues app users need a Teams Premium licence, and the Queues app also requires Teams Phone.
  • Creating and licensing resource accounts needs User Administrator or higher.

When to use / skip

There's no "skip" here — any auto attendant or call queue that answers calls needs a licensed resource account, full stop. The real decisions are about outbound. If the client's queues only ever receive calls and route internally, the free licence is all you need. The moment someone sets an overflow to an external mobile, lets agents present the queue's number as caller ID, or wires up an after-hours divert to an outsourced answering service, the resource account needs funded outbound capacity.

The Queues app is where Premium sneaks into a Teams Phone project. Supervisors who want real-time metrics, historical reporting and barge/whisper/takeover in Teams are asking for Teams Premium for those users. If they only need agents to answer calls, they don't.

Configuration decisions

  • One resource account per auto attendant/call queue, or nested designs with fewer numbered accounts? Each still needs the licence.
  • Which resource accounts make outbound PSTN calls (caller ID masking for agents, external redirects, exception handling to external numbers)? Those need pay-as-you-go or Communications Credits on Calling Plan numbers.
  • For Operator Connect/Direct Routing numbers, agree outbound-on-behalf-of handling with the carrier or SBC owner.
  • Which supervisors and agents need the Queues app, and therefore Teams Premium.
  • Communications Credits auto-recharge thresholds and who gets the alert.
  • Whether any legacy resource accounts still carry Teams Phone Standard and need swapping.

Gotchas

  • Swapping Teams Phone Standard for the Resource Account licence must happen in one licence change. Remove, save, add, save, and the auto attendant or queue can stop working — Learn's fix is to build a new resource account and delete the broken one.
  • Older tenants often have resource accounts with no licence at all. Learn tells you to go back and license them — do it before you touch anything else in the voice estate.
  • The November 2025 change catches out tenants who set up queues years ago with a Calling Plan on the resource account. Outbound on-behalf-of calls just start failing. Audit the "Assign calling ID" and external-redirect settings.
  • You can't see "outbound on behalf of" in a licence report. You have to walk each auto attendant and call queue's routing, exception handling and caller ID settings to find which accounts need funding.
  • Teams Premium for the Queues app is per user. Licensing one supervisor doesn't light it up for the rest of the team.

Consultant notes

  • Add "resource account licensing" and "outbound funding" as explicit lines in the voice design, separate from user licensing.
  • When inheriting an older tenant, run a quick check for resource accounts holding MCOEV and plan the swap in a maintenance window.
  • Get Communications Credits set up early — it's also needed for toll-free numbers, so it's rarely wasted.
  • Where the Queues app is being sold as a light contact centre, be clear on what it isn't; certified contact centre options are a decision-guide conversation, not a licensing one.

Recheck after any change to how Microsoft bills on-behalf-of outbound calling, or if the Queues app moves out of Teams Premium

Was this accurate?