07 · Attendants and queues
The attendant and the queue are not callable until an account represents them.
Create the resource account, assign the Teams Phone Resource Account license, and attach it to the attendant or queue. A phone number is optional until the PSTN must reach that app. The account stays disabled for sign-in.
At least one Teams Phone license in the tenant turns on the voice-app services. A tenant with zero phone-system licenses will not grow a working queue out of a resource account alone. Read the prerequisite article for the current wording.
Every attendant and queue that answers needs a licensed resource account. Add a phone number only if the PSTN must reach it.
The resource account is the voice app’s identity. The number is optional until you publish it.
If it fails: The queue exists and has no licensed resource account, so it never answers.
Which description of Auto attendant is accurate?
A voice app that answers, plays a greeting, and routes by schedule, menu, directory, or operator. It is the front door. A broken menu is a broken company number. Source: https://learn.microsoft.com/en-us/microsoftteams/create-a-phone-system-auto-attendant accessed 2026-10-14.
A colleague reports: The menu option points at a queue that has no agents and no overflow. Where do you start?
The menu option points at a queue that has no agents and no overflow. Create the attendant, attach a licensed resource account, then assign a number only if the PSTN must reach it. Source: https://learn.microsoft.com/en-us/microsoftteams/create-a-phone-system-auto-attendant accessed 2026-10-14.
Which description of Call queue is accurate?
A voice app that holds callers and offers them to agents by attendant, serial, round robin, or longest idle routing. Presence can skip someone who is already busy, which changes who ‘should’ have rung. Source: https://learn.microsoft.com/en-us/microsoftteams/create-a-phone-system-call-queue accessed 2026-10-14.
Around the call: compliance recording, workforce management, emergency location, analytics, CRM screen pop, and an agent with a human escape. Each one has its own failure.
The queue exists and has no licensed resource account, so it never answers.
Cisco CUBE is one of the SBC families named in this lab’s certification lesson. A certified release can be the Direct Routing SBC between Unified CM and Teams.
The tenant still needs a verified domain on the SBC FQDN, and the user still needs Teams Phone. The studio translator does not open a live AXL session. Confirm the current certified release before you build.
Teams Phone and Webex Calling are separate clouds. This lab does not describe a feature that registers a Webex Calling user into a Teams tenant.
A number move is usually a carrier port, a certified SBC, or a meetings interop product. Confirm before relying.
Unified CCE stays the ACD until you migrate it. Microsoft’s contact-center articles name Connect, Extend, and Unify. They do not name a UCCE connector in the notes this lab cites.
Voice into Teams is still Direct Routing or Operator Connect. The routing script stays on the contact-center product you bought. Confirm the vendor’s current model. Source: https://learn.microsoft.com/en-us/microsoftteams/teams-contact-center.
Copilot Studio, Azure Communication Services, and Graph are later tracks in this lab. Treat any uncited limit as confirm before relying.
Opened 2026-10. A row marked confirm did not open. Wikipedia is background. The Teams blog row is the community index.
