Microsoft Teams Phone & SIP Trunking: Operator Connect Explained

If your business runs on Microsoft 365 and everyone already lives in Teams, there's an obvious question: why are we paying for a separate phone system? You can turn Teams itself into your phone, it rings, it dials out, it takes voicemails, it handles call queues and auto-attendants. For Microsoft-heavy organisations, it's often the cleanest answer.

The trick is the licensing and the way you connect Teams to the actual phone network. This guide walks through both.

What Teams Phone is

Microsoft Teams Phone is a cloud-based PBX built into Microsoft Teams. Instead of a separate app or a desk phone system, calls happen in the same Teams client you already use for chat and meetings.

What you get:

• Each user gets a direct dial number
• Calls into and out of the public phone network (PSTN)
• Voicemail to email with transcription
• Shared line appearance / delegation
• Call queues and auto-attendants
• Call park, transfer, hold, conference
• Call recording (with Teams Premium or a third-party add-on)
• Mobile app calling, your work number rings on your phone
• Integration with Microsoft 365, contacts, presence, calendar all linked

What it isn't: a full contact-centre platform. If you need skill-based routing, wallboards, agent whisper, and heavy call-centre features, you're looking at Teams Phone plus a CCaaS overlay (Microsoft's own Dynamics 365 Contact Center, or third-party like Enghouse / ComputerTalk / Landis).

Licensing, three moving parts

Getting Teams Phone working is three licence decisions, not one.

1. Base Microsoft 365 licence

You need a Teams-enabled Microsoft 365 or Office 365 licence as the foundation, Business Basic, Standard, Premium, or an Enterprise E1/E3/E5. You already have this if you're using Teams.

2. Teams Phone licence

The phone system itself:

• Teams Phone Standard, add-on to Business Premium or E3. Per user per month.
• Teams Phone with Calling Plan, as above, plus inclusive PSTN minutes from Microsoft (more on Calling Plans below).
• Included in E5, Teams Phone Standard comes bundled with Microsoft 365 E5.

3. How you connect to the phone network

This is the one that trips people up. Having a Teams Phone licence doesn't give you dial tone, you still need a way to reach the PSTN. Three options:

• Microsoft Calling Plans, buy minutes directly from Microsoft. Simplest to set up, most expensive per minute, limited country coverage.
• Operator Connect, use a partner telco that integrates directly with Microsoft. Usually cheaper, better support, often with inclusive-minute bundles.
• Direct Routing, you (or a partner) run a Session Border Controller (SBC) and bring your own SIP trunk. Most flexible, most work to set up and maintain.

For most SMEs, Operator Connect is the sweet spot.

Operator Connect, explained properly

Operator Connect is Microsoft's programme where approved telecom operators can connect their SIP trunks directly to Microsoft's cloud, with the provisioning, porting, and management handled from the Teams Admin Center.

What that means in practice:

• You choose an Operator Connect provider (Gamma, BT, Vodafone, Colt, and many others are approved)
• The provider manages the SIP trunk, the connection to Microsoft, and the phone number inventory
• You see the provider inside the Teams Admin Center, assigning a number to a user is a couple of clicks
• The provider bills you separately (usually a per-user bundle with inclusive UK/international minutes)
• Microsoft handles the Teams licensing; the provider handles the dial tone

Contrast with the old way (Direct Routing):

• You run a virtual Session Border Controller in Azure
• You configure PowerShell voice routing policies
• You monitor the SBC uptime
• Any change to numbers is a PowerShell script

Operator Connect eliminates all of that. The tradeoff is you're tied to providers who've joined the programme, but every major UK telco of note has.

Why Operator Connect beats Microsoft Calling Plans

For UK businesses specifically:

• Inclusive minutes, Operator Connect providers typically bundle thousands of UK landline and mobile minutes per user per month. Microsoft Calling Plans charge per-minute or require separate top-up bundles.
• Lower per-user cost, Operator Connect bundles usually come in around £3–£8 per user per month depending on the provider and inclusive minutes. Microsoft Calling Plans are comparable or higher.
• UK support, you get a UK telco account manager, not a Microsoft chatbot.
• Easier porting, porting numbers from your existing UK provider is what UK telcos do for a living; Microsoft's porting process is known to be slower.

Teams Phone vs 3CX vs PhoneLine+

Quick decision tree:

If you're…	Consider
Sub-10 users, just replacing a landline	PhoneLine+
10–200 users, already heavily in Microsoft 365, want one-app simplicity	Teams Phone + Operator Connect
10–200 users, need advanced queuing / CRM integration, less Microsoft-dependent	3CX
Heavy contact-centre operation	Teams Phone + CCaaS overlay, or dedicated CCaaS

Teams Phone wins when:

• All your staff already live in Teams
• You want one app (and one headset) for chat, meetings, and calls
• You have E5 or Business Premium users who already include or nearly-include Teams Phone
• Mobile-as-extension through the Teams mobile app works for your users

It's less strong when:

• Your staff don't use Teams for chat / meetings (why force it just for calls?)
• You need deep CRM call-pop integrations that Teams doesn't cover
• You need heavy call-centre features without paying for the CCaaS overlay
• You want vendor-neutral SIP you can switch providers on without changing the phone system

Call queues, auto-attendants, voicemail

All included in Teams Phone Standard. Configuration is through the Teams Admin Center (or PowerShell for scale). A simple call flow looks like:

1. Inbound call hits the auto-attendant
2. IVR greeting plays, "Press 1 for sales, 2 for support, 3 for accounts"
3. Caller is routed to a call queue
4. Call queue rings through a group of agents, serial, longest idle, round-robin, or in parallel
5. If no answer, overflow to voicemail or another queue
6. Voicemail transcription is delivered to a shared mailbox

Resource accounts (the Teams objects that represent auto-attendants and call queues) need their own service-plan licences, but these are free, just assign them from your pool of "Microsoft Teams Phone Resource Account" licences.

What a rollout looks like

For a 30-user Microsoft 365 Business Premium firm moving to Teams Phone with Operator Connect:

1. Week 0, design call flows, select Operator Connect provider, audit numbers
2. Week 1, licence Teams Phone add-on for each user (or upgrade to E5 if making sense)
3. Week 1, Operator Connect provider onboards, connects to your tenant
4. Week 1–2, port existing numbers from your old provider
5. Week 2, assign direct dial numbers, configure call queues and auto-attendants
6. Week 2, staff get their numbers, Teams clients start ringing
7. Week 2–3, desk phones (Poly, Yealink) if wanted, Teams-certified models only
8. Week 3, old system decommissioned once port is confirmed stable

Typical end-to-end: two to three weeks. Zero-downtime cutover because numbers port cleanly on a scheduled day.

Headsets and desk phones, quick note

Teams Phone works with:

• Software client, Teams on Windows, Mac, iOS, Android, web
• Teams-certified headsets, Poly, Jabra, Logitech, EPOS. Avoid non-certified, audio quality is noticeably worse and Microsoft support will refuse to troubleshoot.
• Teams-certified desk phones, Yealink MP series, Poly CCX series, AudioCodes C series. These log into Teams directly, no middleware.

Most users end up with a headset and the Teams client. Desk phones are a minority choice except for receptionists and common areas.

Compliance and recording

• Call recording, needs Teams Premium (per-user add-on) or a third-party compliance recording provider. Don't just enable the "meeting record" button; that's for meetings, not calls.
• MiFID II / FCA compliance, use a dedicated compliance recording partner (Verint, Red Box, ASC). They integrate via Graph API and capture everything.
• GDPR, data stays in the tenant's region. UK customers can generally keep all call data in the UK or EU region.

How we deploy it

We're Microsoft Partner-accredited for Teams Phone deployments and resell Operator Connect via Gamma. A typical engagement:

1. Licence audit, work out whether to add Teams Phone Standard to Business Premium, upgrade to E5, or stay where you are
2. Telco selection, Operator Connect bundle sized to your call volume, inclusive minute allocation matched to usage
3. Call flow design, auto-attendants, queues, overflow logic documented
4. Number porting, coordinated with your existing provider so numbers move cleanly
5. Hardware deployment, headsets / desk phones as needed, configured centrally
6. Training, 20-minute sessions for general users, hands-on for reception and queue owners
7. Handover, admin access stays with you, we're on hand for changes

If you want a quote or help deciding between Teams Phone, 3CX, and PhoneLine+, get in touch.