Practical guide · Teams Phone
Teams Phone: turning on business calling without improvising
Making Teams the company’s phone system is not just a feature to switch on. The calling plan you choose, porting an existing number, and who owns the auto-attendant are decisions to make beforehand, not settings you discover after the fact.
The decision to make
This guide helps an organization see what needs deciding before turning on Teams Phone, and what belongs in the recurring cadence versus a one-time project.
Three ways to get a dial tone into Teams
A Microsoft calling plan, a connection through an Operator Connect partner, or a direct link to your own telephony provider all lead to a working number inside Teams, but with different cost and different responsibility for the underlying carrier relationship. The right choice depends on existing contracts, not an isolated technical preference.
Number porting runs on its own timeline
Moving an existing business number over to Teams requires coordination with the old provider and a transition window planned well ahead of time. It is a one-time event with its own delay risk, not a change that slots into a routine monthly cycle.
The auto-attendant needs a named owner
Someone has to decide the greeting, the menu options, and the queue routing - and, more importantly, who updates it when hours or staff change. An auto-attendant left to itself ages badly, exactly like a SharePoint site or a team with no active owner.
- A named business person owns the message content
- A known process exists for updating hours and options
- A check happens after every schedule or staffing change
What follows the usual lifecycle, and what stays a project
Adding or removing a calling licence for someone joining or leaving can follow the same checklist as the rest of the lifecycle already covered by monthly management. Initial number porting, auto-attendant design, and choosing a carrier remain a separate one-time setup project.
What this guide does not cover
Negotiating a carrier or phone-line contract, buying physical desk phones, and configuring regulatory emergency-calling compliance need direct attention with your chosen telephony provider. None of that is assumed to be included in this guide or in the monthly cadence.
A simple matrix for assigning the work.
| Situation | Owner | Cadence | Useful evidence |
|---|---|---|---|
| Adding or removing a calling licence | M365 owner | Follows the lifecycle | Licence assigned or removed |
| Porting an existing number | Leadership + provider | One-time project | Transfer date confirmed |
| Auto-attendant or call queue | Named business owner | Agreed review | Menu and routing current |
Decision checklist
What should be true before considering this area under control.
- The choice between calling plan, Operator Connect, or direct carrier link is documented
- Porting an existing number is planned with a confirmed date
- The auto-attendant has a named owner, not just a technician
- Adding and removing calling licences follows the existing lifecycle process
- Carrier contracts and physical phones stay outside this guide
Next step
Connect Teams Phone to the rest of licence hygiene.
Licence hygiene details how every add-on keeps a justified owner. Then see the monthly scope to see where telephony fits inside the service.