3CX and Microsoft Teams Integration: Calling via Your PBX from Teams
In short: 3CX Teams integration works at two levels. The Microsoft 365 integration syncs users, single sign-on and presence. Calling out through the phone system from the Teams dial pad requires Direct Routing: a Teams Phone license for every user who will call from Teams, and a 3CX edition you should confirm in writing with 3CX.
What is 3CX Teams integration, and what are the two ways to set it up?
3CX Teams integration is the shared name for two separate features that connect the 3CX IP PBX with Microsoft Teams: the Microsoft 365 integration and the Teams Direct Routing integration. The first syncs the directory and presence; the second lets Teams users talk to 3CX extensions and reach external numbers over the 3CX SIP trunk.
According to the 3CX Microsoft 365 guide, the first level does not require Teams Phone; presence sync only needs a Teams-enabled license such as Business Basic, Standard or Premium.
| Criterion | Microsoft 365 integration | Teams Direct Routing integration |
|---|---|---|
| What it does | User sync, single sign-on (SSO), phonebook, presence, sending email via Microsoft 365 | Calls from the Teams dial pad to 3CX extensions and external numbers; inbound calls ring in Teams |
| Where people take calls | 3CX apps and desk phones | Teams client alongside 3CX apps |
| 3CX edition | Full integration in Pro and AI; user sync only also in Basic | AI (16SC and above) per the guide and feature list; the PRO edition page also lists it, so confirm with 3CX |
| Microsoft license | A plan with Exchange (e.g. Business Basic, Standard, Premium); no Teams Phone | Teams + Teams Phone (Teams Phone Standard add-on, or E5 which includes it) |
| Extra infrastructure | Admin consent for the app on behalf of the organization | Verified domain, static public IP, public certificate, firewall rules, PowerShell scripts |
The key question: do people want to call from the Teams window, or is it enough to see in Teams who is on a call? If the latter, you do not need Direct Routing or its licensing.
Which 3CX edition and which Microsoft license do you need?
On the Microsoft side, Direct Routing needs Teams Phone for each user who will call from Teams; on the 3CX side, 3CX's own pages disagree on the edition. The 3CX Teams Direct Routing guide (16 September 2026) and the 3CX feature list show Direct Routing in the AI edition (16 or more simultaneous calls), while the PRO edition page lists it among the integrations included in the PRO license. Confirm in writing with 3CX which edition you need at the quotation stage.
Microsoft Learn's Direct Routing planning page states that Direct Routing users require Microsoft Teams and Teams Phone. The Teams Phone licensing page lists Business Basic, Standard and Premium as prerequisites for the Teams Phone Standard add-on, so Teams Phone is not included in those plans. Microsoft 365 E5, by contrast, includes the Phone System app. For the other plan differences, see our comparison of Microsoft 365 Business Basic, Standard and Premium.
The 3CX product page sums up the approach as adding Teams licenses only for key users: the saving comes from not buying Teams Phone for everyone. Compare costs with this formula rather than with list prices:
- With 3CX: (users calling from Teams × Teams Phone Standard) + 3CX annual system license (an edition and capacity that cover Direct Routing) + SIP trunk tariff + certificate + hosting and setup effort.
- Teams Phone only: (all users who need a phone × Teams Phone Standard) + Microsoft-certified SBC + SIP trunk tariff + setup effort.
3CX is licensed per system, not per user, priced annually by the number of simultaneous calls; commercial licenses start at 8SC. If the AI 16SC requirement in the guide applies, even an office that manages with 8 simultaneous calls may have to move to a larger license for Teams Direct Routing, so get the edition confirmed before costing. For the Microsoft side, see our Microsoft Teams Phone page.
Teams Phone or 3CX: which fits businesses in Türkiye?
The right choice depends on how many people will call from Teams and how much you rely on contact center features. According to Microsoft's availability page for Türkiye, Teams Calling Plans cannot be purchased there, which leaves Direct Routing, or Operator Connect if a participating operator is available, for external calls from Teams.
| Situation | Suitable path | Watch out for |
|---|---|---|
| Everyone calls from 3CX apps or desk phones; Teams is for chat and meetings | 3CX + Microsoft 365 integration | No Teams Phone needed; presence sync needs a Teams-enabled license |
| One group (management, sales) wants to call from Teams; queues and IVR stay in 3CX | Direct Routing via 3CX (confirm the edition with 3CX) | Teams Phone only for that group; support goes to 3CX first |
| All staff will call only from Teams | Teams Phone with a certified SBC (Direct Routing) or Operator Connect | Teams Phone for everyone; confirm your operator in Microsoft's directory |
| Teams is not used, or only by a few people | 3CX only | Deployment model (cloud or on-premises) is a separate decision |
Whether to run 3CX in the cloud or on-premises, and which SIP trunk to use, comes before this decision; we compare the options in our guide to 3CX deployment options. The 3CX Teams page stresses that 3CX is not a back-end add-on for Teams: telephony features run in 3CX, and Teams stays the interface. For the full product family, see our 3CX phone system solutions.
Support boundary: Microsoft says it supports Direct Routing only with certified SBCs and reserves the right to reject cases involving non-certified devices. As of 19 October 2026, 3CX does not appear on Microsoft's certified SBC list, so troubleshooting runs through 3CX documentation and support channels.
If you want to settle which users will call from Teams and what 3CX capacity you need, we can draw up the setup plan with you. Get a Quote
Which prerequisites should be ready before installation?
If one prerequisite is missing, the scripts may run and calls still fail. This checklist draws on the 3CX guide, the 3CX Teams FAQ and Microsoft Learn.
- Domain: the Teams FQDN (e.g. teams.yourcompany.com) must sit under a domain verified in your tenant; *.onmicrosoft.com is not accepted.
- DNS: create an A record for that FQDN pointing to the static public IPv4 address of 3CX.
- Certificate: from a Microsoft-trusted authority, covering exactly that FQDN and including the intermediate certificates. 3CX does not accept wildcard certificates for this integration.
- Numbers: each user's "Office phone" field in Microsoft 365 must be in E.164 format (for Türkiye, starting with +90).
- Licensing: Teams Phone assigned and shown as on in the "Phone System" column of the Teams admin center; provisioning can take up to a day. Remove any assigned Calling Plan.
- Firewall: allow SIP/TLS (on 3CX usually 5061 or 5062) and media (UDP 3478–3481 and 49152–53247 on the Teams side, 9000–10999 by default on 3CX) between 3CX and Microsoft's 52.112.0.0/14 and 52.120.0.0/14 ranges.
- Tooling: the scripts run in an elevated PowerShell; version 2.3.1 or later of the MicrosoftTeams module is expected.
To plan the network layers together, see our SMB office IT infrastructure guide, and for rule management our firewall maintenance and management service. Protect the admin account that runs the scripts with MFA; see also our Microsoft 365 security settings checklist.
How do you set up 3CX Teams Direct Routing step by step?
Setup runs through the Teams page in the 3CX admin console and the two PowerShell scripts it generates. The first eight steps follow the 3CX guide; the last follows Microsoft's validation advice.
- Microsoft 365 integration: connect via Admin > Integrations > M365, grant consent on behalf of the organization and enable user sync. Sync is one-way, runs nightly and covers up to 650 users.
- Teams FQDN: under Admin > Integrations > Teams, tick "Enable Microsoft Teams Direct Routing", enter the FQDN and create the DNS A record.
- CSR: generate the private key and certificate request with the 3CX CSR tool (OpenSSL required).
- Certificate: obtain a file with intermediate certificates from an approved authority; 3CX has documented its tests with SSL.com.
- Upload: upload the certificate and private key as .pem files on the Teams page.
- Port: if the Teams FQDN differs from the 3CX FQDN, open port 5062.
- Dial plan script: select country and area code, generate teams_dial_plan.ps1, set the execution policy to Bypass in an elevated PowerShell and run it.
- User script: enable the Teams integration under Admin > Users > Options > M365, then generate and run map_users.ps1. Repeat for every new Teams Phone user.
- Validation: watch the SBC status in the Teams admin center, restart the Teams client and place internal, national and international test calls.
Start with a pilot of two or three users. So that unanswered calls do not drop into Teams voicemail and break the 3CX call flow, 3CX recommends setting "If unanswered" to "Do nothing" in Teams. If you prefer to hand over the setup, our 3CX Microsoft Teams integration page describes the scope.
What issues commonly appear after installation?
Symptoms from the 3CX Teams FAQ (10 September 2026) and the first thing to check.
| Symptom | Likely cause | First check |
|---|---|---|
| SBC shows "Trunk Down" or a warning | Expected right after the first script; if it persists, port, DNS or certificate | Wait about 15 minutes; then SIP port, A record, certificate chain |
| User script produces an empty list | No license, user not yet provisioned, or number not in E.164 | License assignment, "Phone System" column, number format |
| "OnPremLineURI" error | No license, or a Calling Plan enabled | Phone System add-on; with Business Voice, the domestic Calling Plan box |
| Calls from Teams fail | Number changed and not yet synced, or a calling policy blocks it | Mapping error in the 3CX log; "3CX Calling Policy" and "Any destination" settings |
| Only one app rings on iPhone | iOS cannot show two calls from the same caller ID in CallKit | 3CX recommends using the 3CX app for calls |
FAQ
Is a Teams Phone license required for 3CX Teams integration?
Yes, for users who will call through the phone system from the Teams dial pad. Microsoft requires Teams and Teams Phone for Direct Routing users, and 3CX asks for a Phone System license per user. The Microsoft 365 integration, which provides user sync, single sign-on and presence, works without Teams Phone.
Does Microsoft 365 Business Premium include Teams Phone?
No. Microsoft lists Business Basic, Standard and Premium as prerequisite licenses for the Teams Phone Standard add-on, which is bought separately. The plan that includes the Phone System app is Microsoft 365 E5. Business plans are sold both with and without Teams, so also check that your plan includes Teams.
Which 3CX edition supports Teams Direct Routing?
3CX's own sources differ. The Teams guide (16 September 2026) and the feature list show Direct Routing in the AI edition with licenses of 16 or more simultaneous calls, while the PRO edition page lists Direct Routing among the integrations included in the PRO license. Confirm in writing with 3CX which edition you need at the quotation stage. 3CX is licensed per system and per year, not per user.
Can you buy a Teams Calling Plan in Türkiye?
No. Microsoft's availability page for Türkiye (26 August 2026) shows Calling Plans as not available for purchase. For external calls from Teams, choose Direct Routing, or Operator Connect if a participating operator is available. Audio Conferencing, which lets people join meetings by phone, can be purchased in Türkiye.
Can I use a wildcard certificate?
Not with 3CX, according to its Teams FAQ: wildcard certificates cannot be used for secure SIP, and the certificate must cover exactly the Teams FQDN. Microsoft's general Direct Routing rules accept wildcard certificates that comply with RFC 2818, but here the 3CX rule decides. The certificate must come from an authority in Microsoft's trusted root program.
Can Teams users and 3CX users call each other?
Yes. According to the 3CX guide, the Direct Routing integration lets Teams users call and be called by 3CX users, while external lines run over the 3CX SIP trunks. One team can stay in Teams and another in the 3CX app. To plan a mixed setup, contact us.
Conclusion
- For presence, phonebook and single sign-on, the Microsoft 365 integration is enough; no Teams Phone is needed.
- Calling through the phone system from Teams needs Teams Phone for each calling user; confirm the 3CX edition (AI 16SC+ or PRO) in writing with 3CX.
- Calling Plans are not sold in Türkiye; the choice is between Direct Routing (3CX or a certified SBC) and Operator Connect.
- Certificates, E.164 numbers and license provisioning are the usual blockers; start with a small pilot.
Sora Yazılım Teknolojileri can support you with license selection, procurement, setup and support on both the 3CX and Microsoft 365 sides; the scope of service is set out in the contract.
Free discovery call · WhatsApp: WhatsApp Support · Phone: +90 544 785 21 87 · Email: talep@sorayazilim.com
Sources
- Configuring Microsoft Teams Direct Routing — 3CX, 16 September 2026. 3cx.com (accessed 19 October 2026)
- Microsoft 3CX Teams Integration Configuration Troubleshooting — 3CX, 10 September 2026. 3cx.com (accessed 19 October 2026)
- Microsoft 365 Integration — 3CX, 8 September 2026. 3cx.com (accessed 19 October 2026)
- Full Feature List — 3CX, 28 August 2026. 3cx.com (accessed 19 October 2026)
- 3CX PRO Edition — 3CX, 2026. 3cx.com (accessed 19 October 2026)
- Microsoft Teams Direct Routing Integration — 3CX. 3cx.com (accessed 19 October 2026)
- Plan Direct Routing — Microsoft Learn, September 2026. learn.microsoft.com (accessed 19 October 2026)
- Session Border Controllers certified for Direct Routing — Microsoft Learn, October 2026. learn.microsoft.com (accessed 19 October 2026)
- Teams Phone licensing — Microsoft Learn, July 2026. learn.microsoft.com (accessed 19 October 2026)
- Microsoft Teams add-on licenses — Microsoft Learn, April 2026. learn.microsoft.com (accessed 19 October 2026)
- Availability in Turkey — Microsoft Learn, August 2026. learn.microsoft.com (accessed 19 October 2026)
- PSTN connectivity options — Microsoft Learn, August 2026. learn.microsoft.com (accessed 19 October 2026)
How this article was prepared
Prepared by: Sora Yazılım Team. This article was prepared with AI assistance; the technical details were checked against the vendor and official sources linked in the text as of 19 October 2026.
Related articles
- SMB Office IT Infrastructure Guide — Network, telephony, email and endpoints in one plan.
- 3CX Deployment Options — Cloud, on-premises and SIP trunk compared.
- Microsoft 365 Business Basic vs Standard vs Premium — Which plan suits which team.
- Exchange Server 2016/2019 End of Support — Exchange Online or Exchange SE.
- Microsoft 365 Security Settings Checklist — Tenant hardening step by step.
- Bitdefender GravityZone Plans Compared — Business Security, Premium and Enterprise.
- Reducing the Endpoint Attack Surface — Hardening with GravityZone.
- Ruijie Reyee or RG Enterprise Series? — Choosing office network products.
- Wi-Fi 7 Migration Guide for Businesses — When moving to Wi-Fi 7 makes sense.