Teams Voice Licensing Simplified

February 18, 2022
Connect with us

If you are interested in VoIP for Teams but are confused by the licensing requirements- we've broken down the licensing and costs for you. 

 

PROMO FROM MICROSOFT: Unlimited domestic minutes 

 

Phone System ($8/user/month) 

Phone System licenses provide the ability for a user to receive and transfer calls. Users can make online, peer-to-peer calls using Teams, but they will need an additional Calling Plan add-on to be able to make outbound calls using Microsoft as the PSTN calling provider. 

  

Calling Plan ($12/user/month Domestic, $24/user/month Domestic + International) 

Calling Plan licenses provide users the ability to make outbound calls using Microsoft as the voice provider. 

These can be purchased as domestic per user (3,000 minutes/user/month pooled) or domestic AND international per user (3,000 minutes/user/month pooled domestic, 600 minutes/user/month pooled international). 

  

Audio Conferencing ($4/user/month) 

Audio Conferencing provides the ability to create a Teams meeting that contains a PSTN dial-in number for users to call into. This can be added to basically all Office 365 subscriptions (including Business Premium or Skype for Business Online Plan 2 Standalone) but is also included within the Enterprise E5 plan 

  

Overview cost 

  • Office 365 Enterprise E3 Plan: $20/user/month (contains the following subscription)
  • Exchange Online (Plan 2)
  • Phone System Add-on: $8/user/month
  • Calling Plan Add-on
  • Domestic: $12/user/month
  • Domestic: International @ $24/user/month
  • Audio Conferencing: $4/user/month (Optional) 

  

Total Cost per user = $52/user/month with the international domestic Calling Plan 

   

NOTE: Audio Conferencing and phone system are included in the Office 365 E5 licensing plans (O365 E5 is $35 per user) 


Contact us and we can help you get started
By Shawn Akins October 20, 2025
October 20, 2025 — Early today, Amazon Web Services experienced a major incident centered in its US‑EAST‑1 (N. Virginia) region. AWS reports the event began around 12:11 a.m. PT and tied back to DNS resolution affecting DynamoDB , with mitigation within a couple of hours and recovery continuing thereafter. As the outage rippled, popular services like Snapchat, Venmo, Ring, Roblox, Fortnite , and even some Amazon properties saw disruptions before recovering. If your apps or data are anchored to a single cloud, a morning like this can turn into a help‑desk fire drill. A multi‑cloud or cloud‑smart approach helps you ride through these moments with minimal end‑user impact. What happened (and why it matters) Single‑region fragility: US‑EAST‑1 is massive—and when it sneezes, the internet catches a cold. Incidents here have a history of wide blast radius. Shared dependencies: DNS issues to core services (like DynamoDB endpoints) can cascade across workloads that never directly “touch” that service. Multi‑cloud: practical resilience, not buzzwords For mid‑sized orgs, schools, and local government, multi‑cloud doesn’t have to mean “every app in every cloud.” It means thoughtful redundancy where it counts : Multi‑region or multi‑provider failover for critical apps Run active/standby across AWS and Azure (or another provider), or at least across two AWS regions with automated failover. Start with citizen‑facing portals, SIS/LMS access, emergency comms, and payment gateways. Portable platforms Use Kubernetes and containers, keep state externalized, and standardize infra with Terraform/Ansible so you can redeploy fast when a region (or a provider) wobbles. (Today’s DNS hiccup is exactly the kind of scenario this protects against.) Resilient data layers Replicate data asynchronously across clouds/regions; choose databases with cross‑region failover and test RPO/RTO quarterly. If you rely on a managed database tied to one region, design an escape hatch. Traffic and identity that float Use global traffic managers/DNS to shift users automatically; keep identity (MFA/SSO) highly available and not hard‑wired to a single provider’s control plane. Run the playbook Document health checks, automated cutover, and comms templates. Then practice —tabletops and live failovers. Many services today recovered within hours, but only teams with rehearsed playbooks avoided user‑visible downtime. The bottom line Cloud concentration risk is real. Outages will happen—what matters is whether your constituents, students, and staff feel it. A pragmatic multi‑cloud stance limits the blast radius and keeps your mission‑critical services online when one provider has a bad day. Need a resilience check? Akins IT can help you prioritize which systems should be multi‑cloud, design the right level of redundancy, and validate your failover plan—without overspending. Let’s start with a quick, 30‑minute review of your most critical services and RPO/RTO targets. (No slideware, just actionable next steps.)
By Shawn Akins October 13, 2025
How a Zero-Day in GoAnywhere MFT Sparked a Ransomware Wave—and What Mid-Sized IT Leaders Must Do Now
By Shawn Akins October 13, 2025
The clock is ticking: Learn your options for Windows 11 migration, Extended Security Updates, and cost‑smart strategies before support ends.
More Posts