Native auto attendants and call queues vs a certified contact centre

What it does

The call on whether a customer-facing or internal service line runs on Teams' built-in auto attendants and call queues (optionally with the Teams Premium Queues app), or on a third-party contact centre platform certified by Microsoft and integrated through one of its integration models.

Key facts

Microsoft's certified contact centre programme uses three integration models: Connect (certified SBCs and Direct Routing), Extend (Azure bots and Graph Communications APIs as a Teams app) and Unify (Azure Communication Services-based CCaaS on Teams calling infrastructure).
Microsoft states it supports contact centre solutions only from certified partners and may reject support cases where a non-certified solution is involved.
Call queues allow up to 20 individually added agents, or 200 via a group, Teams channel or Shifts schedule. Beyond 200 members, only the first 200 voice-enabled members alphabetically become agents.
Maximum calls in a queue is 0–200 (default 50). Call timeout ranges from 0 seconds to 45 minutes.
Routing methods: attendant, serial, round robin and longest idle. Longest idle forces presence-based routing on.
Conference mode is recommended on, but isn't supported for Direct Routing with Location-Based Routing.
Callback, compliance recording (up to two templates per queue) and up to 15 authorised users per queue are available natively.
Each auto attendant or call queue resource account needs the free Teams Phone Resource Account licence. Outbound PSTN from voice apps needs pay-as-you-go or Communications Credits since 1 November 2025.
The Queues app, including shared call history, requires a Teams Premium licence for every user of it.

When to use / skip

Native queues are fine — genuinely fine — for reception lines, IT service desks, HR and facilities lines, small sales teams and anything where the question is "who picks up next?" rather than "who is this customer and what happened last time?". With the Queues app on Teams Premium, supervisors get real-time stats, agent opt-in control and call history in the Teams client, which covers a lot of what people used to buy a "light" contact centre for.

Go to a certified contact centre when the requirements include any of: omnichannel (email, chat, social, messaging alongside voice), skills-based routing beyond what a queue per skill can model, CRM screen-pop and case creation, workforce management and forecasting, quality management and scoring, PCI-DSS payment handling, wallboards with contractual SLA reporting, or outbound dialling campaigns. Also go there when the queue would breach native limits — more than 200 agents in one queue, or more than 200 callers waiting. If you find yourself chaining six queues and four auto attendants to fake skills routing, you've already outgrown native.

The integration model matters as much as the vendor. Connect-model solutions sit in front of or alongside Teams via Direct Routing, which means SBCs and a second routing brain. Extend and Unify solutions live inside the Teams fabric, so agents stay in the Teams client and Teams Phone does the media. For a client already on Operator Connect with no SBC estate, a Connect-model platform quietly drags Direct Routing back into the design.

Configuration decisions

Native, native plus Queues app (Teams Premium for every agent and supervisor using it), or certified platform — decide per line of business, not per organisation.
Integration model if certified: Connect (SBC/Direct Routing), Extend (Teams app, Graph) or Unify (ACS-based).
Where the main number lands: Teams auto attendant handing to a platform, or the platform owning the number with Teams agents behind it.
Recording: Teams compliance recording on the queue, the platform's own recorder, or both — and which one is the record of truth.
Agent licensing: Teams Phone for every agent, plus Teams Premium (Queues app) or the platform's per-seat licence.
Reporting: native historical reporting and Queues app, or the platform's analytics, and who owns the numbers in the weekly ops review.

Gotchas

The 200-agent ceiling counts the first 200 voice-enabled members alphabetically. A large group as a queue source silently drops the Zs.
"Longest idle" switches presence-based routing on for you. Agents on a Teams call for another reason won't get queue calls — usually what you want, sometimes not.
Conference mode is the recommended setting but breaks with Direct Routing plus Location-Based Routing. Check before you tick it.
Queue outbound calling broke quietly for tenants that didn't license resource accounts with pay-as-you-go or Communications Credits by November 2025. Check older deployments.
Non-certified contact centre products may work technically but leave the client unsupported by Microsoft on any call-path issue. Check the certified list, not the vendor's slide deck.
Platform vendors often appear under more than one model. Confirm which model the product you're actually buying uses — it changes the network and SBC design.

Consultant notes

Run a requirements workshop with the actual operations manager, not IT. Ask what they report on monthly and what their agents complain about. That list decides native vs certified within an hour.
Prototype on native first for internal lines. It's cheap, it's quick, and it shows the client exactly where the gaps are before they sign a three-year CCaaS contract.
For Dynamics 365 shops, look at Microsoft's own customer service and contact centre stack before defaulting to a third party — the CRM integration story is a large part of the value.
Budget for Teams Premium for supervisors at least, even on a certified platform, if they also run native internal queues.
Keep an eye on Teams Phone Agent (sits alongside auto attendants and call queues, in Frontier preview, with Bookings, Copilot Studio and Power Automate options on Teams Premium): it changes how much of the IVR needs a contact centre at all.

Revisit when Teams Phone Agent goes GA, or the certified partner list on Learn changes models