What we do
Tools
Industries
Department
How we workLet's talk →
Home/MS Teams/Teams Phone
Microsoft Teams

Microsoft Teams Phone: Getting Real Calls In, and Call Records Out

Teams can replace a desk phone system, with real phone numbers, menus that answer the main line, and queues that share calls across a team. Getting there means a license, a route to the phone network and a number for each person. Getting a record of those calls into anything other than Teams is a separate job.

Before anyone can dial out

A Teams Phone license for each person who makes or takes outside calls, on top of their Microsoft 365 plan with Teams. Chat and Teams-to-Teams calls don't need it.

A route to the public phone network: a Microsoft Calling Plan, a carrier through Operator Connect, or your own carrier through Direct Routing.

A phone number assigned to the user, plus an emergency address on file, set up in the Teams admin center.

Teams admin center Voice Phone numbers

Which route to the phone network fits your company

All three give users the same Teams calling experience. What changes is who you pay for minutes, who supports the line, and how much telephony know-how you need in house.

Your situation Usually fits Ask before you sign
Small office, one country, nobody who manages phone systems Microsoft Calling Plan Is a Calling Plan sold in every country you have staff? Coverage is limited, and minute bundles can cost more than a carrier's.
You like your current carrier, or want to keep your numbers and rates with it Operator Connect, if your carrier is a certified operator Is your carrier on Microsoft's Operator Connect list, and how long does it take them to move your numbers across?
Several countries, an existing SIP trunk, or kit like door phones and paging that must keep working Direct Routing through a certified session border controller Who looks after the border controller at 2am when inbound calls stop? Direct Routing gives you control, and also the pager.
A mix: head office on one route, a branch abroad on another Combine routes. Teams lets different users sit on different ones Whether your reporting can still see every call once records come from two sources.

Switching it on, in the order that avoids rework

Each step depends on the one before it. Most stalled rollouts skipped the emergency address or the resource accounts.

  1. 1

    Assign the licenses

    Give each calling user a Teams Phone license alongside their Microsoft 365 license, and a Calling Plan license too if that's your route. Licenses can take a while to show up in the Teams admin center after you assign them.

  2. 2

    Get the numbers

    Voice Phone numbers

    With a Calling Plan you request new numbers here, or start a port of your existing ones. With Operator Connect the carrier supplies them. With Direct Routing they come from your own trunk and get assigned with PowerShell or the admin center.

    Watch for: porting your main number. Book it for a quiet day and keep the old system answering until the port completes.

  3. 3

    Add emergency addresses

    Each office needs an emergency address on file before Calling Plan numbers can be assigned to the people in it. Do this before assigning numbers, not after.

  4. 4

    Give each user a number

    Assign the number on the user's page in the admin center. They'll see a dial pad in the Teams Calls app once it's active.

  5. 5

    Build call queues, then the auto attendant

    Voice Call queues

    A call queue rings a group of people in turn or all at once. An auto attendant is the "press 1 for sales" menu on your main number, and it hands callers to those queues. Build queues first so the menu has somewhere to send people. Each one needs a resource account of its own.

  6. 6

    Point the main number at the auto attendant

    Voice Auto attendants

    Assign your main number to the auto attendant's resource account, set business hours and holidays, then ring it from a mobile to hear what a customer hears.

Calls work. The records go nowhere.

This is where most Teams Phone rollouts get their second ticket, usually from finance or the sales manager.

The usage report only answers some questions

How you'll know: Someone wants call counts per rep or per customer, and the only source is an Excel export from the admin center.

Fix: The PSTN and SMS usage report (Analytics & reports, Usage reports) exports outside calls to Excel. It leaves out Teams-to-Teams calls, and Calling Plan and Direct Routing records come in separate files. Fine for a monthly look, not for a live dashboard.

History runs out before anyone looks

How you'll know: An audit or a dispute needs last year's calls, and they're gone.

Fix: Microsoft keeps Calling Plan records for up to 12 months and Direct Routing records for 150 days. If you need longer, copy the records somewhere you own on a schedule.

The CRM never hears about the call

How you'll know: A rep clicks a number in Teams, talks for twenty minutes, and the customer's record still shows no contact since March.

Fix: Pull each call from Microsoft Graph's callRecords API as it ends and log it on the right contact by phone number. That needs an app registration and the CallRecords.Read.All permission, granted by an admin.

Missed queue calls just disappear

How you'll know: A caller hangs up after waiting in a queue and nobody knows to call back.

Fix: Turn on the call queue's callback option first, so callers can ask for a call back instead of holding. For callers who hang up before they're offered it, the same call records show which calls were never answered, and those can become a callback task for whoever owns the queue.

What Teams tells you about calls, and what has to be built

In Teams already

Built-in views

  • Each user's own call history in the Calls app.
  • The PSTN and SMS usage report, exportable to Excel.
  • Call quality data for troubleshooting a bad line.
  • Voicemail delivered to the user's inbox.
Needs the Graph API

Calls in your other systems

  • A logged call on the customer record in your CRM or help desk.
  • Call volume per queue in the same dashboard as your sales numbers.
  • Callback tasks for missed calls.
  • Records kept past Microsoft's retention window.

Some CRMs ship their own Teams calling add-on, so check yours first. Dynamics 365 Sales has a Teams dialer, for example. If yours doesn't, or you need the records in more than one place, it's a Graph integration.

Questions people ask

What's the difference between Calling Plans, Operator Connect, and Direct Routing?

They're three ways to connect Teams to the public phone network. With Calling Plans you buy numbers and minutes from Microsoft, which is the simplest setup. Operator Connect lets a certified carrier supply the numbers and minutes, managed from the Teams admin center. Direct Routing links your own carrier through a session border controller, which gives the most control and needs someone who can run that hardware.

Do I need a separate license to make phone calls in Microsoft Teams?

Yes. Chat, meetings and Teams-to-Teams calls work on a standard Microsoft 365 plan with Teams. Calling outside numbers needs a Teams Phone license per user, plus either a Microsoft Calling Plan or an agreement with a carrier through Operator Connect or Direct Routing.

Can I export my Teams Phone call history?

Partly. Admins can export the PSTN and SMS usage report to Excel from Analytics & reports in the Teams admin center, which covers calls to and from outside numbers. For a steady feed into another system, or for Teams-to-Teams calls, use Microsoft Graph's callRecords API.

What is an auto attendant in Microsoft Teams Phone?

The automated menu that answers a number and sends callers to a person, a call queue or voicemail based on what they press or say. It's the "press 1 for sales" part of a phone system, set up under Voice in the Teams admin center with its own business hours and holiday schedule.

Does a Teams Phone call automatically log into my CRM?

Not by itself. Some CRMs have their own Teams calling integration that logs calls, so check yours. Otherwise the call has to be picked up from Microsoft Graph when it ends and written to the right customer record, and that's an integration n-frames builds.

Can I keep my existing phone numbers when moving to Teams Phone?

Usually, yes. With a Calling Plan you port them to Microsoft from the admin center. With Operator Connect or Direct Routing they stay with, or move to, the carrier you connect. Plan the port for a quiet day and keep the old system live until it finishes.

Let's talk

Tell us the one thing your team does manually that eats up time. We read every message and reply within a day.