Teams Calling Licensing Templates by Customer Profile
If you’ve ever tried to figure out Microsoft Teams Calling licensing from scratch, you already know the documentation doesn’t make it easy. There are overlapping SKUs, add-ons that aren’t add-ons depending on what you already have, and a PSTN decision that changes the entire cost model. This guide cuts through that and gives you a practical licensing framework organized by real customer profiles — the ones you’ll actually encounter in the field.
The Licensing Foundation: What Every Teams Calling Deployment Needs
Before you think about customer size or use case, every Teams Calling deployment requires the same core components:
1. Microsoft 365 Suite The base M365 license for each user. Which tier (Business Basic, Business Standard, E1, E3, E5, etc.) depends on what the customer actually needs from the broader suite — not from a calling perspective.
2. Teams Phone Standard This is the add-on that unlocks the PBX features in Teams: voicemail, call queues, auto attendants, call transfer, hold, and the rest. It’s required for every user who needs to make or receive calls.
Important exception: If a user already has an M365 E5, A5, or G5 license, Teams Phone Standard is already included. Don’t add it on top — you’ll be paying twice.
3. A PSTN Connection Teams Phone Standard gives you the phone system software, but it doesn’t connect you to the public telephone network. You need one of three options to complete the stack (covered in the next section).
4. Shared Device and Resource Account Licensing This is where most deployments get over-licensed and overpay. More on this below.
- Teams Shared Device License — for any physical phone that isn’t assigned to a specific user (lobby phone, conference room, shop floor, etc.)
- Teams Phone Resource Account — free license, required to associate shared devices and call queues/auto attendants to your Azure tenant for billing
5. Azure Tenant and Billing This one trips people up. The Resource Account is free, but it needs somewhere to live for billing purposes. You have three scenarios:
- Existing Microsoft tenant — if the customer already has M365, they can use their existing Azure tenant. Phones and M365 billing are mixed together.
- New separate tenant — if the customer wants to separate phone billing from the rest of their M365 spend, you set up a dedicated tenant for the phone deployment. More admin overhead, but cleaner billing separation.
- Net new to Microsoft — if this customer has never had M365 at all, they’ll need a new Azure tenant from scratch. Factor this into your setup scope.
There’s no wrong answer here — it’s a billing preference decision. Just make sure it’s a conscious decision made upfront, not something you figure out halfway through deployment.
The Three PSTN Options
Once you have the phone system licensed, you need to connect it to the outside world. There are three paths:
Microsoft Calling Plans (Cloud PSTN)
Microsoft acts as your carrier. Phone numbers, calling capacity, and billing all live inside your M365 tenant. Easy to set up, no third-party contracts, and great for straightforward deployments. The trade-off is cost at scale — per-user per-month pricing adds up in high-volume environments, and you have less flexibility on number porting and international calling.
Operator Connect
Microsoft-certified carriers (companies like Calling Tower, Lumen, or Bandwidth) connect their PSTN infrastructure directly to your Teams tenant through a certified API integration. You manage numbers and assignments through the Teams Admin Center just like Calling Plans, but the carrier relationship, pricing, and calling plans are negotiated directly with the operator. This is the sweet spot for mid-to-large deployments that need more flexibility and volume pricing than Microsoft Calling Plans offer.
Direct Routing
You provide (or your customer provides) a Session Border Controller (SBC) that bridges their existing carrier or on-premises telephony to Teams. This is the most flexible option and the most complex — it gives you full control over call routing, carrier selection, and dial plan behavior, but it requires SBC infrastructure, configuration expertise, and ongoing management. More on this in the Direct Routing profile below.
Licensing by Customer Profile
Profile 1: Small Business (1–20 Employees)
The situation: A small office that needs phones and basic M365 productivity. Maybe they’re moving off a legacy phone system or setting up for the first time. Call volume is low, everyone needs a softphone, and they want simplicity.
The approach: Keep it simple. Give everyone the M365 tier that fits their productivity needs, add Teams Phone Standard on top (unless they somehow landed on E5, which is rare at this size), and connect them to Microsoft Calling Plans. No carrier contracts, no SBC, no complexity. This is your cleanest deployment.
Licensing stack:
| License | Quantity |
|---|---|
| M365 (Business Basic / Standard / E1 / E3) | Per user |
| Teams Phone Standard | Per user (skip if E5) |
| Microsoft Calling Plan (domestic or domestic + international) | Per user |
Notes:
- Domestic Calling Plan is usually sufficient. Add international only where actually needed.
- Microsoft Calling Plans include a pool of minutes — monitor usage and right-size after the first month or two.
- Pay-As-You-Go Calling Plan is an option if outbound call volume is very low.
Profile 2: Mid-Size Organization with Mixed Usage
The situation: The organization has a mix of desk workers and non-desk employees. Not everyone needs a full M365 account. This is where most deployments leave significant money on the table — someone builds the quote, licenses everyone the same way, and nobody catches it until the renewal.
The key distinction — Users vs. Spaces:
A User needs:
- A personal M365 account
- Voicemail
- Softphone capability (Teams app on desktop/mobile)
- Call history tied to them personally
A Space needs:
- One phone on one desk or in one room
- Calls in and out — nothing else
- No personal M365 account, no voicemail, no softphone
Spaces get a Teams Shared Device License instead of Teams Phone Standard. It’s significantly cheaper and purpose-built for exactly this scenario. Once you start applying this split consistently, the savings on a mid-size deployment are hard to ignore.
Real-world example — School ABC (50 employees):
- 15 office staff: need full M365, voicemail, softphone → Users
- 35 teachers: classroom phones assigned to the room, not the teacher → Spaces
| License | Quantity |
|---|---|
| M365 (appropriate tier) | 15 |
| Teams Phone Standard | 15 (skip if A5/E5) |
| Teams Shared Device License | 35 |
| Teams Phone Resource Account | 1 (free) |
| Azure tenant | Existing, new, or net new — decide upfront |
| Microsoft Calling Plan or Pay-As-You-Go | As needed |
You’ve potentially cut the per-phone licensing cost on those 35 classroom phones significantly compared to full per-user licensing. That’s real money at renewal time.
PSTN guidance for this profile: If outbound call volume is low — primarily inbound with occasional outbound — Pay-As-You-Go Calling Plan is often the right fit. You’re not paying for a block of minutes you won’t use.
Profile 3: High-Volume Calling Organization (Operator Connect)
The situation: The organization makes a lot of outbound calls. Sales teams, call centers, support organizations, or any environment where staff is on the phone constantly. Microsoft Calling Plans start to get expensive at volume, and you need more control over your carrier relationship.
The approach: Same licensing framework as the mid-size profile for users vs. spaces, but replace Microsoft Calling Plans with an Operator Connect carrier. You negotiate a calling plan directly with the operator that fits your volume and calling patterns.
Why Operator Connect over Microsoft Calling Plans at scale:
- Volume pricing — operators can offer better per-minute or per-seat rates than Microsoft’s standard plans
- More flexibility on international calling, toll-free numbers, and number management
- The carrier is accountable for call quality and SLA — you have a real support relationship
- Still fully managed inside Teams Admin Center — no SBC, no infrastructure to maintain
Operator Connect is not a compromise. Honestly, these integrations work really well. Operators go through a rigorous Microsoft certification process to connect directly into the Teams infrastructure, so the calling experience for end users is identical to Microsoft Calling Plans. You connect your account, the operator handles the PSTN setup, and you manage everything from the same Admin Center you’re already living in. You’re simply working with a better-priced carrier that’s built for your volume.
Licensing stack:
| License | Quantity |
|---|---|
| M365 (appropriate tier) | Per user |
| Teams Phone Standard | Per user (skip if E5) |
| Teams Shared Device License | Per space (where applicable) |
| Teams Phone Resource Account | As needed (free) |
| Azure tenant | Existing, new, or net new — decide upfront |
| Operator Connect calling plan | Negotiated with operator |
Profile 4: Enterprise / Complex Requirements (Direct Routing)
The situation: This customer has requirements that neither Microsoft Calling Plans nor Operator Connect can satisfy. They may have an existing carrier contract they need to honor, on-premises PBX infrastructure they’re not ready to fully replace, custom dial plan requirements, regulatory constraints that require routing control, multi-site deployments across multiple countries, or a dedicated telephony team to manage the infrastructure.
This is the outlier profile. You won’t see it as often as the others, but when you do, it’s important to go in with eyes open — for you and for the customer.
The approach: Direct Routing connects Teams to any SIP-compatible carrier or on-premises telephony system through a certified Session Border Controller (SBC). The SBC acts as the translator and security gateway between Teams and the PSTN (or legacy PBX).
What’s involved in a Direct Routing deployment:
Session Border Controller (SBC) Either a hardware appliance (AudioCodes, Ribbon) or a virtual/cloud-based SBC. It must be Microsoft-certified — there’s no flexibility here. The SBC is the most significant infrastructure cost in a Direct Routing deployment and the primary source of ongoing management overhead. Sizing is based on concurrent call capacity, so you need accurate call volume data before specifying hardware.
SIP Trunk from a Carrier The SBC connects to your carrier via SIP trunking. You own that relationship — provisioning, troubleshooting, and contract negotiations all sit with you or your customer’s team. This is a meaningful operational difference from Operator Connect, where the carrier relationship is managed cleanly through the Teams Admin Center.
Dial Plan and Normalization Rules Tenant-level and user-level dial plans map your organization’s dialing habits to E.164 format. This sounds straightforward until you’re dealing with a multi-site deployment where different sites dial extensions differently, have different local area codes, or need to reach on-premises PBX extensions alongside PSTN numbers. Poorly written normalization rules are one of the most common causes of silent call failures in Direct Routing — calls that appear to route correctly in the admin center but fail at the SBC level with no obvious error in Teams.
Voice Routing Policies PSTN usage records, voice routes, and voice routing policies control which users can reach which numbers through which trunk. A well-designed routing policy gives you granular control — local calls route through a local trunk, long-distance through a separate route, emergency calls through a dedicated path. It also enables least-cost routing if the customer has multiple carrier options. This layer of the configuration is where Direct Routing earns its “complex” label, and it’s also where the most mistakes get made during initial deployment.
Emergency Calling Compliance Direct Routing deployments must still meet Ray Baum’s Act requirements for dynamic emergency calling. For most deployments this means integrating with a third-party E911 provider (Bandwidth, Intrado, or similar) to handle dynamic location data — particularly critical for remote or hybrid workers whose physical location changes. This is a compliance requirement, not optional, and it adds both cost and integration complexity to the deployment.
Direct Routing licensing stack:
| License | Quantity |
|---|---|
| M365 (appropriate tier) | Per user |
| Teams Phone Standard | Per user (skip if E5) |
| Teams Shared Device License | Per space (where applicable) |
| Teams Phone Resource Account | As needed (free) |
| Azure tenant | Existing, new, or net new — decide upfront |
| SBC hardware/software/licensing | Sized by concurrent call capacity |
| SIP trunk from carrier | Sized by channel/usage needs |
| E911 provider (if required) | Per location or per user |
Be honest with customers about Direct Routing: This is not a cost-saving measure — it is a complexity trade-off. You gain control and carrier flexibility, but you’re taking on SBC management, dial plan maintenance, carrier troubleshooting, and a more involved change management process. If a customer is considering Direct Routing primarily to save money over Operator Connect, run the full numbers including SBC licensing, professional services, and ongoing management overhead before committing.
Direct Routing is the right call when the customer has an existing SIP carrier investment they’re extending, needs to maintain PSTN connectivity during a phased migration from on-premises PBX, has routing requirements that can’t be met by managed services, or is large enough to have a dedicated telephony engineering resource owning it long-term. This isn’t a one-person job.
Quick Reference: Licensing Decision Framework
| Customer Type | PSTN Option | Per-User License | Per-Space License |
|---|---|---|---|
| Small business, simple needs | Microsoft Calling Plans | M365 + Teams Phone Standard | Teams Shared Device |
| Mid-size, low outbound | Pay-As-You-Go Calling Plan | M365 + Teams Phone Standard | Teams Shared Device |
| High call volume | Operator Connect | M365 + Teams Phone Standard | Teams Shared Device |
| Complex / enterprise | Direct Routing + SBC | M365 + Teams Phone Standard | Teams Shared Device |
E5/A5/G5 users: Teams Phone Standard is already included — never add it as an additional license.
Final Thoughts
The biggest licensing mistakes in Teams Calling deployments come from two places: licensing every phone as a full user when Shared Device fits, and defaulting to Microsoft Calling Plans without evaluating call volume. Walk every customer through the user vs. space split before you build a quote, and evaluate PSTN options against actual calling patterns — not just what’s easiest to set up.
Get those two things right and you’ll consistently deliver a tighter, more defensible licensing recommendation than most of what’s out there.