Microsoft Teams Domestic and International Calling Plan for Government — Pricing, Plans & What's Included

Microsoft Teams Domestic and International Calling Plan for Government includes a per-user Microsoft cloud PSTN calling plan for eligible Government tenants, because it is designed to let assigned users place and receive domestic and international phone calls from Microsoft Teams where Microsoft Calling Plans are supported. It must be paired with the required Teams Phone capability for each assigned user.

The Government Domestic and International Calling Plan does not include the base Microsoft 365 or Office 365 license, because it is an add-on calling plan rather than a full productivity suite. It also does not include a standalone Teams Phone license if the user’s suite lacks Teams Phone, desk phones, headsets, contact center software, third-party carrier services, or unlimited global calling in every country or region.

A Government buyer should choose the Domestic and International Calling Plan for users who regularly need both domestic and international PSTN calling from Teams, because the plan is intended for users with international calling needs as well as domestic calling. Users who only call within supported domestic destinations may be better matched to a domestic-only plan after validating calling patterns and country availability.

Yes, each target user needs Teams Phone capability before this calling plan can be useful, because the calling plan supplies Microsoft PSTN calling while Teams Phone supplies the cloud PBX/phone-system features in Teams. Some Microsoft 365 or Office 365 suites may already include Teams Phone, while others require a separate Teams Phone add-on.

No, this plan does not include the Teams app or a base Microsoft 365 Government suite, because it is sold as a calling plan add-on for assigned users. The user must already have, or be assigned, the appropriate Microsoft 365 or Office 365 licensing and Teams Phone capabilities needed for calling in Teams.

No trial is listed for this Government offer, because the current catalog entry identifies only paid commitment options. Government buyers should validate tenant eligibility, Teams Phone prerequisites, location support, and porting requirements before assigning the add-on.

Government purchasing options include monthly commitment billed monthly, annual commitment billed annually, and annual commitment billed monthly, because the catalog lists those commitment and billing combinations for this offer. Annual commitment billed annually is the lowest current listed per-seat rate, annual commitment with monthly billing has a higher overall total, and monthly commitment is the most flexible.

Seat reductions and cancellations are constrained by the Microsoft CSP subscription term, because annual commitments generally lock in the committed quantity except during the allowed cancellation window or at renewal. Monthly commitment is typically the better fit when a Government agency expects frequent user changes, while annual commitment is better for stable user populations.

Yes, additional seats can generally be added during the subscription term, because Microsoft cloud subscriptions support increasing assigned quantities as users are onboarded. The added seats should still be checked for Teams Phone prerequisites, Calling Plan availability, emergency calling requirements, and the correct Government tenant eligibility before assignment.

This offer is listed with Governmental Community Cloud pricing, but the exact tenant cloud eligibility must be confirmed before ordering, because Government cloud environments such as GCC, GCC High, and DoD can have different service availability and SKU rules. IT Partner should validate whether this specific SKU is valid for the customer tenant before any license assignment or migration plan is finalized.

No, the calling plan by itself does not guarantee that every compliance or residency requirement is satisfied, because PSTN calling involves Microsoft cloud services, telecom connectivity, location-specific emergency calling rules, and regulatory obligations that vary by environment. Government buyers should review the Microsoft service documentation for their cloud, confirm whether the tenant is GCC or another Government cloud, and validate agency-specific compliance requirements before purchase.

No, Microsoft Calling Plan availability is not universal, because phone number availability, calling destinations, emergency calling requirements, and porting support vary by country or region. A Government buyer should confirm service availability for each user location and calling destination before selecting this Microsoft Calling Plan.

No, buyers should not assume unlimited global calling, because the plan provides domestic and international calling where Microsoft Calling Plans are supported but the exact minute allowances and destination rules depend on the agency’s country or region. IT Partner should validate the current domestic and international allowance details for the tenant location before purchase.

Possibly, because many Microsoft Calling Plan deployments support number porting, but porting eligibility, timing, required documentation, and supported number types vary by location and carrier. Government agencies should confirm number availability and porting requirements before ordering licenses or scheduling cutover.

A Government agency should start with a voice readiness review, because Teams Phone prerequisites, user locations, phone numbers, emergency calling, devices, call queues, auto attendants, and porting must be planned before assigning calling plans. A phased migration usually reduces risk by piloting a small user group, validating call flows, and then scheduling number ports in controlled batches.

Downtime can usually be minimized but should not be assumed to be zero, because number porting depends on carrier processes, cutover timing, and readiness of Teams Phone configuration. The safest approach is to configure licenses, emergency locations, call routing, and test users in advance, then schedule porting windows with a rollback plan.

Emergency calling support must be validated by location, because emergency calling rules, address requirements, and supported capabilities vary by country, region, and Government tenant configuration. Before assigning the plan, the agency should confirm emergency addresses, location policies, compliance obligations, and any site-specific requirements.

No, this calling plan does not include Microsoft Copilot, because it is a Teams PSTN calling add-on rather than an AI or productivity add-on. Copilot licensing, eligibility, data controls, and Government cloud availability must be evaluated separately from Teams Phone and Calling Plan licensing.

A Government tenant can have different Teams voice approaches in the same broader environment, but each user should be assigned a coherent voice configuration, because Microsoft Calling Plan, Operator Connect, and Direct Routing are different PSTN connectivity models. This Domestic and International Calling Plan is appropriate when the agency wants Microsoft to provide the cloud PSTN calling plan for supported users and locations.

Yes, a CSP partner change can typically be handled without moving the Microsoft tenant or user data, because the tenant, users, phone numbers, and Teams configuration remain in Microsoft 365 while the partner relationship and subscription management are updated. IT Partner should review the current subscriptions, renewal dates, and voice dependencies first so the transfer is coordinated without avoidable calling disruption and with the same Microsoft catalog pricing basis for the SKU.