Teams Phone Agent: It’s not just another voice app—it’s your enhanced Auto Attendant

Most articles on Teams Phone Agent portray it as some new magic tool that answers the phone. When you’re already using Teams for your daily phone calls, this framing is misleading—and it misses the point.

Here is the reality, as it appears on the web Teams admin center : Teams Phone Agent is not a new voice application separate from theAuto Attendant and the Call Queue. It is a mode of theAuto Attendant. You do not create a “ Teams Phone Agent” in a dedicated menu. You create a auto attendant, and then toggle a switch.

This distinction makes all the difference in how it’s integrated into an existing voice architecture. That’s the focus of this article: where it fits in, and how to wire it.

Where does it fit into the voice stack?

If you're already familiar with the trio resource account → auto attendant → call queue, you already know 80% of Teams Phone Agent. It uses exactly the same building blocks:

• The same resource account model. A TPA that is called directly requires a resource account with a Teams Phone Resource Account license (free). To be reachable from outside the network, it needs a service number. To forward calls to external numbers, a pay-as-you-go license or communication credits are required on the resource account—just like for any AA.
• The same call flows. Business hours, after-hours, holidays: the structure is identical to that of a standard “ auto attendant ,” with time zones and configurable time periods.
• The same peripheral concepts: dial scope, authorized users, operator, dial-by-name / dial-by-extension, diagnostic tool (the good old Teams AA diag that verifies that a resource account can receive calls).

What’s truly new can be summed up in one sentence: In the “Play menu options” step, two native AI destinations appear in addition to the usual destinations (person in org, voice app, resource account, external number, voicemail):

• Tools — the Questions & Answers and Appointments tools, managed directly in the TPA.
• Agents & Queues — Access to Microsoft Copilot Studio agents and third-party IVRs for specialized workflows such as billing, order status, and inventory checks.

Most importantly, the caller no longer has to press a button: they can describe their request in natural language, and the TPA routes the call based on the descriptions you have provided for each menu option.

How it integrates with the existing structure

Three key integration points to keep in mind for an existing deployment:

The TPA “extends” theauto attendant —it does not require you to redesign the flow. You can place it at the front end or nest it behind an existing AA/CQ. When creating the TPA, the “Through a voice app (no resource account needed)” option is specifically designed to place it behind another voice app that has already answered the call.

An “ call queue ” can switch to a TPA when the queue becomes overloaded. The “ call queue ” exception handling now accepts a Phone Agent Teams as a destination when there are no more agents logged in, the queue is full, or wait times become unmanageable. This is a powerful pattern: the human queue comes first, with the AI agent serving as a safety net rather than a replacement.

The TPA can itself forward a request to an call queue , or a person. The workload is distributed both ways—the AI handles the repetitive tasks and hands things back to a human when necessary.

In other words: it's not a silo. It's just another layer in a hierarchy that you already know how to manage.

The Deployment Walkthrough

Prerequisites

• Participation in the Frontier program (Public Preview).
• One resource account + Teams Phone Resource Account license purchased directly from TPA.
• A service number for each POS terminal that can be reached from outside the company.
• PAYG / communication credits if the TPA transfers calls to external numbers.
• Workflow-wise: the Questions & Answers and Appointments tools, and the agents Copilot Studio you plan to connect must already exist before you set up the menu.

Creation in the Teams admin center

The initial hurdle everyone runs into: " Quick Setup" doesn't work for a POS terminal. You have to use "Advanced Setup."

The path isn't where you'd expect it to be: Voice > Auto Attendants > Add. Then, on the General Info step, enable the "Teams " toggle, read the splash screen, and confirm.

Next, the seven steps follow the basic structure of a auto attendant, with a few TPA-specific elements:

1. General Information — name, toggle activation, choice between “resource account” (direct call) or “voice app” (nesting), default language, voice, operator. Note for the Swiss context: fr-CH and de-CH are included in the list of supported languages. Voice input is enabled by default and cannot be disabled.
2. Call handling hours — time zone and business/after-hours time frames.
3. Business-hours call flow —this is where it gets interesting. The greeting is text-based or TTS (audio files are not supported). There are three possible routing options after the greeting: Disconnect, Redirect (the AI is not engaged), or Play menu options (the AI is engaged). It’s in this last mode that “Tools” and “Agents & Queues” appear, and each option is assigned a “Description” —the most important field in the TPA, since it tells the AI when to trigger which option based on the caller’s language.
4. After-hours call flow — same logic.
5. Holiday call flow (optional).
6. Dial scope (optional) — which users can be reached via dial-by-name/extension.
7. Authorized users (optional) — which can modify this TPA, depending on the Teams voice applications policy.

Plug in Copilot Studio

Business workflows do not reside in the TPA; they reside in Copilot Studio. A maker builds a voice agent there and then assigns it to the Teams Phone Agent (or to a resource account called directly) via the “Agents & Queues” destination in the menu. The TPA serves as the call center front end; Copilot Studio serves as the business brain. This separation is fundamental to determining who manages what within the organization.

Validate

Before opening the line, the diagnosis Teams , AA (aka.ms/TeamsAADiag) verifies that a resource account can indeed receive calls and flags any issues related to the tenant, policy, or configuration. And for large-scale automation, the TPA is also created via PowerShell (New-CsAutoAttendant), with options that aren't available in the interface—for example, enhancing "dial-by-name" via -UserNameExtension.

The pitfalls that only an operator can foresee

• Your audio prompts will not be migrated. “Play an audio file,” “Announcement (audio/typed),” and “Force listen” are not supported in TPA mode. If your current AA relies on carefully produced recorded messages, you’ll need to redesign everything using TTS.
• A disclaimer is required. After your greeting, the TPA always plays a message stating that it is a virtual assistant, in the default language only. You have no control over this—be sure to incorporate it into your design and compliance statement.
• The person in the organization must be voice-enabled. A transfer to a user without a voice license will fail.
• The "Operator" is optional but highly recommended —and if you do not map any keys or the "Operator" command, output to a human is simply disabled.
• The GUIDs ( Entra ID ) stored in the configuration do not synchronize with the users' lifecycle. When an authorized user, an operator, or a transfer point leaves the organization, manual cleanup is required—a real issue regarding governance and personal data.

Key Takeaways

For a customer who is already using auto attendant, the right message isn’t “you need to adopt a new technology.” It is: “Your auto attendant can now speak, understand, and trigger workflows—it’s the same thing, with an AI layer and two new menu options.” This continuity is a selling point for deployment, not a limitation: the resource account, call flows, transfers, diagnostics—everything you’re already familiar with remains valid.

Expertise, in this context, isn’t about describing the agent. It’s about knowing exactly where it fits into a real-time voice architecture and anticipating the five pitfalls that turn a smooth pilot into a migration a painful experience. That’s what your audience expects from you.