The hidden costs of Microsoft Teams as a phone system

When IT teams compare Microsoft Teams Calling against other cloud PBXs, the sticker price wins easily. $14/user/month seems cheap. Then the bill arrives and looks different.

The visible cost

• Teams Phone Standard - ~AUD $14/user/month - adds calling to Teams; you bring the calling plan separately (Operator Connect, Direct Routing, or Microsoft Calling Plans).
• Teams Phone with Calling Plan (Australian) - ~AUD $24/user/month - bundles a Microsoft-managed Australian calling plan.

For 50 users on Teams Phone with Calling Plan: ~$14,400/year. Looks reasonable.

The hidden costs

1. Per-minute charges on Calling Plans

Microsoft Calling Plans for Australia carry per-minute rates that are often higher than competitive Australian SIP provider rates. For high-call-volume businesses (contact centres, sales teams), the per-minute overage adds up quickly.

2. Tier creep for advanced features

Standard Teams Calling has basic queues only. To get:

• Advanced contact-centre features - Microsoft Dynamics 365 Contact Center, $20–110/user/month extra depending on tier.
• Real-time wallboards - third-party tool ($10–30/user/month) or Power BI custom build.
• Compliance-grade recording with retention rules - third-party recording solutions ($5–15/user/month) or Premium licence upgrade.
• AI Receptionist functionality - limited Copilot features included; full AI Receptionist requires custom development or external integration.
• AI sentiment tracking - on Microsoft’s roadmap; typically requires Dynamics 365 Contact Center premium tiers.

For a 50-user business with light contact-centre needs, the realistic all-in cost adds $10–20/user/month on top of the base licence.

3. Microsoft 365 licence dependency

Teams Calling requires Microsoft 365 E1 ($13/user/month) at minimum, and most customers want E3 or E5 ($30–55/user/month) for the broader productivity features. Strictly, Teams Calling assumes a base M365 spend.

4. Limited CRM integration beyond Microsoft

Tight Dynamics 365 integration. Limited HubSpot, Salesforce, Zoho, Pipedrive integration without third-party connectors. For businesses on non-Microsoft CRM stacks, this is a friction point.

5. Australian support is offshore

Microsoft’s enterprise support is global. Australian customers wanting Australian time-zone support either escalate via partners (which adds another cost layer) or live with US/Asia-Pacific support hours.

6. Lock-in to Microsoft Calling Plans or partner Direct Routing

Teams Calling tightly controls how calling reaches the public network. Operator Connect, Microsoft Calling Plans, or specific Direct Routing carrier partners - your choice is constrained.

The all-in cost - worked example

50-user professional services firm, light contact-centre handling:

The bigger the business, the wider the gap.

The smart alternative: Direct Routing with 3CX

Keep Microsoft Teams as the user experience. Move the PBX backend to 3CX via Direct Routing.

Result:

• Users still call from Teams (no change to their experience).
• You drop the per-user Teams Calling licence.
• You bring your own SIP trunk (we bundle Australian calling).
• You add proper PBX features: skills-based queues, wallboards, supervisor tools, scheduled reports, AI Receptionist, AI sentiment, compliance-grade recording.
• Australian support is Australian-based.

Migration guide: Microsoft Teams Calling → 3CX Direct Routing →

When Teams Calling is still the right choice

Three scenarios where Teams Calling is fine:

• Under-5-user team - small enough that per-user pricing doesn’t sting.
• No PBX requirements - no queues, no contact-centre, no AI, no non-Microsoft CRM.
• Heavy Microsoft-only stack - committed to Microsoft for all infrastructure regardless of cost.

For everyone else, the smarter long-term play is Teams as client + 3CX as PBX behind it.

Common questions