Teams Phone has been around long enough that most organizations have already formed an opinion about it, and a good number of those opinions are now out of date. The version people evaluated in 2021 was a competent cloud phone system. The version sitting in your tenant in 2026 answers calls on its own, warns you when somebody is impersonating your bank, and lets one person hold numbers in two countries.
This is a look at what actually changed, what it costs once you include the parts that are not in the licence, and which organizations should move now rather than at the next contract renewal.
What Teams Phone is, in one paragraph
Teams Phone turns Microsoft Teams into your phone system. Your desk extension becomes your Teams account, so the same app you already use for meetings and chat also rings when somebody calls your number, on your computer, your mobile or a desk handset. Behind it sit the things a phone system has always needed: auto attendants that answer and offer options, call queues that ring a group in order, transfers, voicemail, call recording and reporting. The difference is that none of it lives in a box in a cupboard, and none of it needs a separate vendor, a separate login or a separate support number.
What is actually new in 2026
The theme this year is straightforward: the phone system started answering the phone. Everything else is a consequence of that.
Teams Phone Agent, which answers calls for you
The most significant change is that an AI agent can now pick up a service line directly. It answers, handles the questions it can, books appointments where that is appropriate, and routes the caller to the right person or department when it cannot help. For the kind of line that currently rings out to whoever is nearest, or sends people to voicemail after five rings, that is a meaningful shift.
Beyond the built in agent, custom voice agents built in Copilot Studio now integrate with Teams Phone, which means a process specific to your organization, such as letting a customer pay a bill or check an order, can be handled by the same phone number people already call. The Copilot Studio side is where this gets genuinely interesting and also where it stops being a switch you flick, since a voice agent is only as good as the process and content behind it.
The Queues app grew up
If you run any kind of shared line, reception, dispatch, service desk or an ordering line, this is the set of changes that will matter most day to day.
- The Queues app now works on mobile. Agents and supervisors can take queue calls and see what is happening from the Teams app on iOS and Android, which removes the assumption that whoever is covering the queue is sitting at a desk.
- Call queue recording became automatic and central. Recording is no longer tied to whichever agent remembered to start it, and recordings and transcripts land in SharePoint instead of scattering across individual OneDrive accounts. Anybody who has tried to find a call from three months ago will understand why that matters.
- Copilot recaps arrived for recorded queue calls. Rather than listening back to a call to find out what was agreed, you get a summary. Useful for supervisors, genuinely useful for training.
Multi line calling
One account can now hold multiple phone numbers from different countries. This sounds narrow until you are the person who has a Canadian number for clients, a US number because half your customers will not dial internationally, and a mobile you actually answer. It also removes a class of awkward workaround for organizations operating across a border, which in British Columbia is more common than it sounds.
Warnings when a caller is pretending to be someone
Teams now flags calls where the caller appears to be impersonating a trusted brand, such as your IT help desk or your bank, with a signal during the call so the person can hang up before engaging. Voice phishing is one of the harder attacks to train people out of, precisely because it arrives in the one channel where everybody still assumes good faith. A warning at the moment it matters is worth more than another awareness email.
What it costs, and the part that catches people out
Here is the thing that surprises organizations on the first invoice: a Teams Phone licence is not phone service. It turns Teams into a phone system. It does not give you a phone number and it does not include a minute of calling. Those are a separate decision.
The licence makes Teams a phone system. Connecting it to the outside world is a second, separate decision.
Microsoft lists Teams Phone Standard at ten US dollars per user per month, and five dollars for the frontline worker version, which is aimed at staff who need a phone but not a full desk based setup. Canadian pricing differs and your agreement may differ again, so treat those as the shape of the thing rather than your quote.
The second decision is how calls reach the outside world, and there are three routes.
| Route | How it works | Who it suits |
|---|---|---|
| Microsoft Calling Plans | Microsoft is your phone company. One vendor, one invoice, set minutes. | Smaller organizations that value simplicity over the last dollar, and anyone who wants one throat to choke. |
| Operator Connect | A certified carrier provides the service, managed from inside the Teams admin centre. | Most small and mid sized organizations. Better rates than Calling Plans without the complexity of running your own. |
| Direct Routing | Your own carrier connects through a session border controller you run. | Larger organizations, unusual requirements, or existing carrier contracts worth keeping. |
Direct Routing looks cheapest on a per minute basis and often is. What the per minute figure leaves out is the session border controller, which runs into thousands of dollars before maintenance, and the specialist knowledge to operate it. It earns its place at scale or where requirements are genuinely unusual. Below that, the saving is theoretical and the complexity is not.
Who should switch now
The honest answer is that Teams Phone is right for most organizations already on Microsoft 365, and the question is usually timing rather than suitability. Four situations make the case to move now rather than later.
Your phone contract is up, or nearly up. This is the single biggest factor. The economics of switching are dominated by whether you are paying to leave something early. If your renewal is within six months, start the conversation now, because a phone migration planned calmly over a few weeks is a different experience from one done in a fortnight because the contract ran out.
Your phone system lives in a cupboard. If there is physical hardware on your premises running your phones, it has a failure date whether or not anybody has thought about it. Replacing it means buying a box and starting the clock again. This is the natural moment to stop doing that.
Your people are not where the phones are. Hybrid work made desk extensions much less useful. If the standing joke is that nobody answers the desk phone because nobody is at the desk, you are already paying for a system that does not match how you work.
You run a shared line that is not working well. Reception, dispatch, a service desk, an ordering line. This is where the 2026 changes land hardest: mobile queue management, automatic recording, Copilot recaps, and the option of an agent answering routine calls. If your queue is currently a hunt group and a spreadsheet, the gap is large.
Who should wait
Three situations where waiting is the right call, and it is worth saying them plainly because the answer is not always move now.
You are locked into a contract with real penalties. Run the numbers. Paying to exit early rarely beats waiting for the renewal date, unless the current system is actively failing.
Your phone system is wired into something specialised. Clinical paging, hotel property management, a contact centre platform with deep integration, alarm and lift lines. None of these make Teams Phone impossible, but they all need checking before a decision rather than discovering afterwards.
The internet at a key site is unreliable. This is the one people skip. Traditional phone systems kept working during an internet outage because they did not need it. Teams Phone does. If a site already struggles, fix the connection first, or plan the fallback deliberately, which usually means a second connection or leaning on mobile. Moving voice onto a connection that already wobbles converts a background annoyance into a daily one.
What switching actually involves
A Teams Phone migration is mostly planning and very little drama, provided the planning happens. The technical work is rarely the hard part.
The discovery stage matters more than anything else: finding every number you own and what it is attached to. Organizations reliably find numbers nobody remembered, connected to a fax machine on old invoices, a lift phone, an alarm line, or a direct number printed on signage. Those are found in discovery or they are found on cutover day, and one of those is considerably better than the other.
After that it is call flow design, which is the genuinely valuable part and the one worth spending time on. Most organizations migrate their existing menus and queues out of habit, including the ones everybody complains about. The move is a rare opportunity to fix the auto attendant that has annoyed callers for a decade, rather than faithfully reproducing it in new software.
Number porting is coordinated with your current carrier and scheduled, usually outside business hours. Then it is handsets where they are genuinely needed, a short piece of enablement so people know how to transfer a call and pick up a queue, and a period of running both systems in parallel where that makes sense.
We have been deploying Teams Phone since before it was called that, for organizations across BC and beyond. A short conversation is usually enough to tell you whether to move now or wait for your renewal, and we will tell you plainly if the answer is wait.
Book a conversationThe short version
Teams Phone in 2026 is a different product from the one many organizations assessed a few years ago, and the difference is not cosmetic. An AI agent can answer a service line, call queues finally work properly on mobile with recording and recaps handled centrally, one person can hold numbers in more than one country, and Teams will warn somebody when a caller is pretending to be their bank.
The cost question is simpler than it looks once you accept that there are two costs rather than one: the licence that makes Teams a phone system, and the connectivity that gives it a number and minutes. For most small and mid sized organizations, Operator Connect is the sensible middle of the three routes.
And the timing question usually answers itself. If your contract is nearly up, or there is a box in a cupboard running your phones, this is the moment. If you are locked in for another two years, note the date and get on with something else.
Frequently asked questions
Does a Teams Phone licence give us phone numbers and calling minutes?
No, and this is the single most common surprise on the first invoice. Teams Phone Standard turns Teams into a phone system: call control, transfers, voicemail, auto attendants, call queues and desk phone support. It does not include a phone number and it does not include a single minute of calling. Connecting to the public telephone network is a separate decision and a separate cost, whether that is a Microsoft Calling Plan, a carrier through Operator Connect, or your own carrier through Direct Routing. Budget for the licence and the connectivity together or the numbers will not add up.
What is actually new in Teams Phone in 2026?
The theme of the year is that the phone system started answering the phone. Teams Phone Agent can pick up a service line, handle common questions, book appointments and hand off to a person when it cannot help, and organizations can build their own voice agents in Copilot Studio for processes specific to them. Alongside that, the Queues app came to mobile so supervisors are no longer tied to a desk, call queue recording became automatic and centralised rather than scattered across individual agents, Copilot recaps arrived for recorded queue calls, and multi line calling finally shipped so one person can hold numbers from more than one country.
Should we choose Calling Plans, Operator Connect or Direct Routing?
For most small and mid sized organizations, Operator Connect is the sensible middle. Calling Plans are the simplest thing to buy because everything comes from Microsoft on one invoice, and they are usually the most expensive per user. Direct Routing gives the best per minute economics and the most control, but it needs a session border controller costing thousands of dollars plus somebody who genuinely knows how to run it, so it only pays off at scale or where you have unusual requirements. Operator Connect keeps management inside the Teams admin centre while letting you use a carrier with better rates, which is the balance most organizations actually want.
Can we keep our existing phone numbers?
Almost always, yes. Number porting is routine and it is the part of the project most worth planning carefully rather than the part to worry about. What matters is timing: porting is coordinated with your current carrier and cannot be rushed on the day, so it is scheduled in advance and usually done outside business hours. The failure mode is not losing numbers, it is discovering late that a number you assumed was yours is actually tied to a service you forgot about, such as an alarm line, a lift phone or a fax number on your invoices.
Do we still need desk phones?
Far fewer than you think, and that is usually where the savings come from. Most people do perfectly well with a headset and the Teams app on their computer and phone. Desk phones still make sense in specific places: a reception desk, a warehouse, a shared area, a boardroom, or anywhere somebody needs a handset without a computer in front of them. Buy them for those roles and skip them everywhere else, rather than replacing every desk phone one for one, which is how organizations accidentally spend more moving to Teams Phone than they were spending before.
Is Teams Phone reliable enough to be our only phone system?
For most organizations, yes, with one honest caveat: it depends entirely on your internet connection. A traditional phone system kept working when the internet went down because it did not use it. Teams Phone does. That is a real change in risk and it deserves a real answer rather than reassurance, which usually means a second internet connection at your main site, or mobile as the fallback, since the Teams app on a phone keeps working on cellular data when the office connection fails. If you run a site where losing phones for an hour is genuinely unacceptable, that conversation happens before the migration, not after.
Who should not move to Teams Phone yet?
Organizations still inside a contract with meaningful penalties, since waiting for the renewal date usually costs less than breaking the agreement. Organizations whose existing system is deeply tied to something specialised, such as a clinical paging system, a hotel property management system or a contact centre platform with heavy integration, since those need checking before anything is decided. And organizations where the internet connection at a key site is genuinely unreliable, because moving voice onto a connection that already struggles turns a background frustration into a daily one.
If you want the deployment side rather than the decision, our Teams Phone service page covers how we run these projects. If you would rather just ask somebody, get in touch.
Author: Elian Figueiredo