In short: The 3CX Microsoft Teams integration connects Teams to 3CX through Microsoft's Direct Routing, so Teams users can call 3CX extensions and outside numbers through 3CX's SIP trunks. 3CX documents it on the AI edition at 16 simultaneous calls and above. Each Teams calling user needs Teams Phone. PRO can still sync users, contacts and presence with Microsoft 365.
What the integration does
Many organisations want the best of both worlds: staff who work in Microsoft Teams all day, and a phone system with deep call handling for reception, queues and reporting. The 3CX Microsoft Teams integration provides that by connecting Teams to 3CX with Direct Routing, Microsoft's method for linking Teams to a phone system or carrier through a session border controller. Here 3CX plays that role.
Once it is set up:
- Teams users can call, and be called by, 3CX users on desk phones, apps and the web client.
- Calls to and from outside numbers run through 3CX and its SIP trunk, so your numbers, menus, queues and call recording stay on 3CX.
- Each Teams calling user is a 3CX user synced from Microsoft 365, with their office phone number held in Microsoft 365 in international format.
- With 3CX's full Microsoft 365 integration (PRO and AI), presence can be synced from 3CX to Teams, from Teams to 3CX or both ways, so colleagues can see who is on a call on either side.
For background on Direct Routing itself, read Teams Direct Routing.
Which 3CX edition you need
3CX's Teams configuration guide (last updated 16 September 2026) states that Teams Direct Routing integration is offered on the 3CX AI edition for systems of 16 simultaneous calls and above. 3CX's published feature list (last updated 28 August 2026) agrees, showing it only on the AI edition. One 3CX PRO edition page does list Teams Direct Routing among PRO integrations, so because 3CX's own pages differ, we confirm the current position with 3CX before we quote.
| 3CX edition | Microsoft 365 | Teams Direct Routing integration |
|---|---|---|
| SMB Free | Not included | No |
| Basic | User sync and single sign-on only | No |
| PRO | Full integration: user sync, single sign-on, contacts and presence | No |
| AI, below 16 SC | Full integration | No |
| AI, 16 SC and above | Full integration | Yes |
Microsoft 365 integration on its own does not put calls into the Teams client; it syncs users, contacts and presence. If you are on PRO and want Teams calling, the options are to move to the AI edition at a suitable size, or use a separate connector service (see below). Our 3CX editions page has the full feature comparison and 3CX pricing explains SC sizing.
What users and admins need
On the Microsoft side, each Teams user who makes calls through 3CX needs a licence that includes Teams plus Teams Phone. Teams Phone Standard is an add-on for most Microsoft 365 plans and is included in Microsoft 365 E5; since 2024, new Enterprise customers buy Teams separately from their E-suite. Microsoft's licensing changes often, and 3CX's own guide says to check current rules with Microsoft, so see Teams Phone licensing for the up-to-date picture. Calling Plans are not needed, because 3CX provides the connection to the phone network.
On the 3CX side, the guide lists these requirements:
- Microsoft 365 integration configured in 3CX.
- An SSL certificate from a certificate authority that Microsoft accepts.
- A Teams FQDN on a domain registered in your Microsoft 365 tenant (an onmicrosoft.com name is not supported).
- A DNS record pointing that FQDN to the static public IP address of the 3CX system.
- Port 5062 (or 5061 in some set-ups) open on the firewall, which matters in particular where the Teams FQDN differs from the 3CX FQDN.
- Each user's office phone number held in Microsoft 365 in international (E.164) format.
Set-up overview
- Check licences and edition. Confirm the 3CX AI edition at 16 SC or above, and Teams Phone for every Teams calling user.
- Connect Microsoft 365. Enable 3CX's Microsoft 365 integration and choose which users and departments to sync.
- Domain and certificate. Choose the Teams FQDN, create the DNS record, obtain the certificate and upload it to 3CX.
- Firewall. Open the port Microsoft needs to reach 3CX.
- Dial plan. Generate 3CX's dial plan script for your country and run it in PowerShell against your tenant.
- Users. Enable the Teams integration on each 3CX user, then generate and run 3CX's user script. Repeat this whenever you add Teams calling users; Microsoft can take up to a day to apply changes.
- Test. Check calls in each direction, transfers, voicemail and queue membership before go-live.
We carry out this work as part of a hosted 3CX project, alongside number porting and user training.
When it beats native Teams Phone, and when it does not
| Choose 3CX with Teams when | Native Teams Phone may be simpler when |
|---|---|
| Reception and contact centre teams need 3CX queues, wallboards, switchboard and supervisor tools | Call handling needs are fairly standard: auto attendants, call queues and voicemail |
| Some staff need desk phones or DECT handsets on 3CX, and others work in Teams | Everyone works in Teams and you want one app and one admin centre |
| You want to keep your own SIP trunk and 3CX's annual system licensing | You prefer Microsoft or an operator as your carrier, through Calling Plans or Operator Connect |
| You need 3CX CRM integration, call recording and AI transcription across all calls | You are already licensed for Teams Phone through E5 and want the fewest moving parts |
Neither is better in general. Our 3CX vs Teams comparison covers the wider decision, and Microsoft Teams Phone explains the native route.
Alternatives if you are not on the AI edition
If the AI edition does not suit your size or budget, there are other ways to bring Teams and an existing phone system together:
- Call2Teams (from Dstny): a cloud Direct Routing service that connects an existing SIP-capable PBX to Microsoft Teams, so Teams users keep the PBX's call routing, hunt groups and IVR, with no hardware on site. Each user still needs Teams Phone Standard. We check compatibility with your 3CX version and edition first.
- Forever Teams: Forever Group's own Teams calling service over Direct Routing, if you would rather move calling into Teams entirely.
- Run both side by side: keep 3CX for reception and queues, and use Teams for meetings and chat, with presence synced through Microsoft 365 integration (PRO and AI).
Tell us how your teams work and we will recommend the simplest route. Pricing depends on licences and set-up, so ask us for a quote.
Why choose your cloud phone system with Forever Systems
We are vendor-neutral. Forever Group supplies and supports several cloud phone platforms, so we recommend the one that fits how your organisation works rather than the one we happen to sell.
- Side-by-side comparison of hosted 3CX, Microsoft Teams Phone, Forever UC, Forever Teams and Webex Calling for your users
- Contact centre and call recording options matched to your call volumes and CRM
- Number porting, handsets and set-up handled for you, including the move off analogue and ISDN lines
- Connectivity checked so call quality is right from day one
- UK support for moves, adds, changes and faults
- For BT Cloud Voice, see our BT Business Partner site cloudvoice.cloud
We work with businesses, schools, charities and public sector organisations. We do not sell consumer phone services.
Want a vendor-neutral cloud phone system comparison and quote?
Tell Forever Systems what you need and we will come back to you by email with options, not a hard sell.
Contact usFrequently asked questions
Does 3CX integrate with Microsoft Teams?
Yes. 3CX can sync users, contacts and presence with Microsoft 365, and the AI edition at 16 simultaneous calls and above offers Microsoft Teams Direct Routing integration, so Teams users can make and take calls through 3CX.
Do Teams users need a Teams Phone licence to use 3CX?
Yes. To make and take calls in the Teams client through Direct Routing, each user needs Teams Phone (included in Microsoft 365 E5, or added to other qualifying plans). A Microsoft Calling Plan is not needed because 3CX provides the phone network connection.
Can I use the 3CX Teams integration on 3CX PRO?
According to 3CX's Teams guide and feature list, no: the Teams Direct Routing integration is offered on the AI edition at 16 SC and above. One 3CX PRO page suggests otherwise, so we confirm with 3CX when we quote. PRO includes full Microsoft 365 integration, including presence sync, and a connector service such as Call2Teams is another option.
What do I need to set up the 3CX Teams integration?
3CX's guide lists the AI edition at 16 SC or above, 3CX's Microsoft 365 integration, a Teams FQDN on a domain registered in your Microsoft 365 tenant, an SSL certificate from a Microsoft-approved authority, a DNS record pointing to the system's static public IP, an open firewall port, and E.164 office numbers in Microsoft 365. We confirm the details for your deployment model, including Hosted by 3CX, before you commit.
Can 3CX show Teams presence?
Yes, on PRO and AI. 3CX's Microsoft 365 integration can sync presence from 3CX to Teams, from Teams to 3CX, or both ways, so a user on a 3CX call shows as in a call in Teams. Users must already be synced from Microsoft 365 and hold a Teams-enabled licence, and 3CX advises mapping statuses carefully to avoid two-way loops.