Microsoft Teams Calling Licensing: How It Actually Works
The tool above handles the decision logic. This reference covers why the profiles exist — the mechanics behind Teams Phone licensing, the three PSTN connectivity methods, and the mistakes that inflate costs or create compliance gaps on deployment day.
Two Things Every Teams Calling Deployment Needs
Teams Calling requires two distinct components: a Teams Phone license that unlocks the PSTN calling feature inside Microsoft 365, and a connectivity method that routes calls to and from the public telephone network. Getting the second part wrong is the most common and most expensive licensing mistake in Teams deployments — organizations either over-license, choose the wrong method for their call volume, or apply full user licensing to phones that only need a fraction of it.
The Teams Phone license itself is straightforward — included in E5, A5, and G5, or purchased as Teams Phone Standard for E1/E3/Business plans. Where organizations diverge is the connectivity method: Microsoft Calling Plans, Operator Connect, or Direct Routing. Each represents a different tradeoff between simplicity, cost at scale, and infrastructure control.
Carrier, numbers, and billing in one subscription. Number management in Teams Admin Center. Best fit for small to mid-size orgs with moderate call volume and no existing carrier contracts. Per-user minute bundles become expensive at scale.
A Microsoft-certified carrier connects to Microsoft's network on your behalf. Number management still flows through Teams Admin Center — no SBC to deploy or manage. Right move when call volume makes Calling Plan per-minute costs prohibitive.
Your organization runs a Session Border Controller bridging your carrier SIP trunks to Microsoft Phone System. Maximum flexibility — custom dial plans, complex routing, geographic redundancy — but requires infrastructure and dedicated management.
Key License SKUs at a Glance
Common Licensing Mistakes to Avoid
Teams Phone Standard is already included in E5, A5, and G5. Adding it as a separate add-on is pure waste — budget impact is immediate and ongoing.
Conference room phones and lobby phones don't need a full M365 user license. The Shared Device License exists for this at significantly lower cost.
Auto attendants and call queues that need a DID require a Teams Phone Resource Account license. It's free, but it must be explicitly assigned — forgetting it breaks inbound routing on go-live day.
SBC sizing depends on concurrent call volume, not seat count. Under-sizing at procurement creates a performance ceiling that is expensive to correct post-deployment. Get the concurrency numbers before speccing hardware.
Microsoft Calling Plans are priced per user per month with capped minute buckets. Contact centers and high-outbound teams will consistently overage — Operator Connect with negotiated volume pricing almost always wins at scale.
Dynamic emergency calling requires additional configuration and often a third-party E911 provider when running Direct Routing. This is a compliance obligation, not optional.
If you're working on a complex deployment — multi-site Direct Routing, Teams Calling + Webex coexistence, or tenant architecture decisions — the consulting page covers what that engagement looks like.