Microsoft Teams Domestic and International Calling Plan — Pricing, Plans & What’s Included

Microsoft Teams Domestic and International Calling Plan adds Microsoft-managed PSTN calling to Teams for assigned users, because Microsoft acts as the calling provider in supported Calling Plan countries or regions. Licensed users can place and receive business calls from Teams clients or compatible Teams Phone devices, including domestic and international calling subject to Microsoft’s supported destinations and plan rules.

Microsoft Teams Domestic and International Calling Plan does not include the base Teams Phone entitlement, because it is a calling plan add-on rather than the phone system license itself. It also does not include Microsoft 365 apps, Teams licensing, Operator Connect, Direct Routing, third-party carrier service, contact center features, or specialized compliance recording solutions unless those are purchased and configured separately.

Yes, each user needs Teams Phone capability before Microsoft Teams Domestic and International Calling Plan can be assigned, because the Calling Plan provides PSTN connectivity but not the core phone system entitlement. Some Microsoft 365 or Office 365 suites may include Teams Phone, while others require a separate Teams Phone add-on, so eligibility should be confirmed before purchase.

No, Microsoft Teams Domestic and International Calling Plan does not include Microsoft Teams or Microsoft 365 productivity apps, because it is a telephony add-on for users who already have the required Teams and Teams Phone licensing. Commercial buyers should confirm their existing Microsoft 365 or Office 365 licenses support Teams Phone, or add the missing prerequisite before assigning the Calling Plan.

No, Microsoft Teams Domestic and International Calling Plan is only usable where Microsoft offers Calling Plans, because PSTN service availability is country- and region-specific. Before buying, confirm availability for each user’s assigned usage location and verify the current domestic and international calling rules for those locations.

No, domestic minute allocations, international minute allocations, fair use rules, and included destinations can vary by Microsoft rules, tenant location, and user location. Because these details can change and are not safely assumed from the product name alone, confirm the current entitlements at checkout or with IT Partner before deployment.

Yes, Microsoft Teams Domestic and International Calling Plan supports Microsoft-managed phone number assignment in supported markets, because Microsoft provides the PSTN calling service for the assigned users. Number availability, number types, porting options, and emergency address requirements should be validated for each user country or region before rollout.

Yes, assigned users can use Microsoft Teams Domestic and International Calling Plan with Teams clients and compatible Teams Phone devices, because the plan enables PSTN calling through Teams Phone. Device compatibility, firmware support, and user sign-in requirements should be checked when planning desk phone deployments.

No, Microsoft 365 Copilot does not include or replace Microsoft Teams Domestic and International Calling Plan, because Copilot is an AI productivity add-on and this product is a PSTN calling add-on for Teams Phone. Organizations that need external phone calling from Teams still need the correct Teams Phone prerequisite and a calling approach such as Microsoft Calling Plans, Operator Connect, or Direct Routing.

No, Microsoft Teams Domestic and International Calling Plan is not a full contact center or advanced voice application, because it provides user-based PSTN calling rather than specialized routing, workforce management, supervisor, or omnichannel functions. If you need contact center, compliance recording, complex call flows, or carrier-specific services, compare Teams Phone integrations such as certified contact center solutions, Operator Connect, or Direct Routing.

Microsoft Teams Domestic and International Calling Plan runs through Microsoft Teams Phone and Microsoft-managed PSTN services, so it benefits from the Microsoft cloud controls that apply to Teams and the customer’s Microsoft 365 tenant. However, the Calling Plan itself is not a substitute for every compliance requirement, because regulated recording, retention, eDiscovery, data residency, and supervision needs may require separate Microsoft 365 configuration or third-party solutions.

Microsoft Teams Domestic and International Calling Plan can support emergency calling where Microsoft Calling Plans are available, because Microsoft provides the PSTN service for assigned users in supported regions. Emergency calling behavior, emergency addresses, dynamic location support, and local regulatory obligations vary by country or region, so these settings should be reviewed before users go live.

A migration typically starts by validating Teams Phone prerequisites, user locations, number availability or porting eligibility, and emergency address requirements, because the Calling Plan must be assignable before numbers and calling policies are activated. Businesses should pilot with a small user group, schedule number ports carefully, and keep the existing carrier active until call flows and inbound numbers are confirmed in Teams.

To start with Microsoft Teams Domestic and International Calling Plan, confirm each user has a qualifying Teams and Teams Phone license, verify Microsoft Calling Plan availability for the user’s country or region, purchase the appropriate subscriptions, assign licenses, configure phone numbers, emergency locations, and calling policies. This sequence matters because buying the add-on alone does not make PSTN calling work unless the Teams Phone prerequisite and location-specific voice setup are complete.

Microsoft Teams Domestic and International Calling Plan is often best when a business wants Microsoft-managed PSTN service and simpler administration, because Microsoft is the calling provider in supported markets. Operator Connect or Direct Routing may be better when the organization needs a specific carrier, broader country coverage, existing telecom contracts, analog integrations, complex routing, or specialized compliance and contact center requirements.

Yes, a CSP relationship or subscription transfer can usually be handled without a Teams tenant migration or user downtime, because the Microsoft 365 tenant and assigned services remain in place while the reseller relationship is updated. The exact process depends on the current licensing channel and subscription state, so IT Partner should validate transfer eligibility, renewal dates, and any change limitations before the move.

No, transferring CSP management to IT Partner should not change the Microsoft Teams Domestic and International Calling Plan service itself, because the licensing remains tied to the same Microsoft tenant and users. Calling policies, phone numbers, Teams settings, and user assignments should remain intact, but IT Partner should review the tenant before transfer to avoid billing or renewal surprises.

Commercial customers can choose month-to-month flexibility, an annual commitment paid monthly, or an annual commitment paid upfront, because the plan is sold as a per-user subscription with different commitment and payment options. Seat increases are generally easier than seat reductions during a term, while cancellations and reductions are governed by Microsoft CSP subscription rules and renewal timing, so confirm the current terms before purchase or renewal.

No, a Commercial Microsoft Teams Domestic and International Calling Plan should not be assumed to fit GCC, GCC High, or other government cloud tenants, because government environments have separate eligibility, cloud boundary, compliance, and availability requirements. Government buyers should use the appropriate government licensing path and confirm Calling Plan availability, residency expectations, and Teams Phone support for their specific cloud.

Nonprofit and education organizations should not assume the Commercial offer is the best or eligible option, because Microsoft has separate programs, eligibility rules, and licensing constructs for charity and education customers. Nonprofits should confirm nonprofit eligibility and any grant context, while schools should distinguish student licensing from faculty or staff licensing and verify whether Teams Phone and Calling Plans are available for the intended users.