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

Microsoft Teams Domestic Calling Plan for Government is an add-on that lets eligible government users make and receive domestic PSTN phone calls in Microsoft Teams, because it adds Microsoft-provided calling-plan connectivity to a Teams Phone environment. It is intended for agencies that want Microsoft to be the PSTN carrier instead of using Operator Connect, Direct Routing, or another carrier model.

Microsoft Teams Domestic Calling Plan for Government includes domestic calling-plan capability for each assigned user where Microsoft Calling Plans are available, because the license is a per-user PSTN calling add-on for Teams Phone. The Government catalog includes Governmental Community Cloud pricing variants, including GCC-labeled options, but the correct SKU must be validated against the tenant before ordering.

Microsoft Teams Domestic Calling Plan for Government does not include the base Teams Phone or Phone System entitlement, because it is only the PSTN calling-plan add-on. It also does not include a Microsoft Teams or Microsoft 365 user license, international calling coverage, contact center software, compliance recording, desk phones, SBCs, network remediation, or deployment services.

Yes, users need the required Teams Phone or Phone System entitlement before a Domestic Calling Plan can be used, because the Calling Plan supplies PSTN connectivity but not the core phone-system capability. Government buyers should confirm whether Teams Phone is already included in the user’s Microsoft 365 plan or must be purchased separately.

No, Microsoft Teams Domestic Calling Plan for Government does not include Microsoft Teams or a Microsoft 365 user license, because it is an add-on license for users who already have the required Teams environment and phone entitlement. Each assigned user must be properly licensed for Teams and Teams Phone before the Calling Plan can deliver calling functionality.

No, Microsoft Copilot is neither required nor included, because Domestic Calling Plan is a Teams Phone PSTN calling add-on rather than an AI productivity license. Copilot licensing, if needed, should be evaluated separately from Teams Phone and Calling Plan licensing.

No trial is listed for Microsoft Teams Domestic Calling Plan in the source Government catalog, because the catalog entries identify paid monthly and annual commitment options only. Agencies should validate licensing and prerequisites before purchase rather than assuming a trial is available.

Government catalog offers include monthly commitment and annual commitment options, because the source catalog lists both month-to-month and annual-term purchasing paths with different billing choices. Annual commitment billed annually is listed as the lowest unit-price option in the catalog, while other options provide different payment flexibility; the exact Government SKU and payment configuration should be confirmed before checkout.

Microsoft Teams Domestic Calling Plan is licensed per assigned user calling-plan license, because the PSTN calling capability is granted to individual users in Teams. Agencies should buy enough licenses for the users who need domestic PSTN calling and should not assign the add-on to users who lack the required Teams Phone prerequisites.

Do not assume one Government Calling Plan SKU works across GCC, GCC High, and DoD, because the source catalog identifies Government and GCC-labeled variants but does not prove eligibility for every government cloud environment. The tenant cloud, country or region, number type, and Microsoft Calling Plan availability should be validated before purchase.

Microsoft Teams Domestic Calling Plan for Government may fit some government tenant requirements, but it should not be treated as a universal compliance guarantee, because PSTN calling depends on tenant cloud, Microsoft carrier availability, country or region, emergency calling rules, and agency-specific requirements. Agencies should confirm data residency, records, clearance, and PSTN carrier obligations before standardizing on Microsoft Calling Plans.

Usually you would not buy this add-on for users whose PSTN connectivity will come from Operator Connect or Direct Routing, because Domestic Calling Plan is the Microsoft Calling Plan carrier model. Some organizations mix PSTN models by site or user, but each user’s voice configuration should be intentionally designed and licensed to avoid overlapping or unused services.

No, this product is the domestic calling plan, because it is intended for domestic PSTN calling by assigned users in eligible regions. International Calling Plan coverage, international pay-as-you-go behavior, overages, and country-specific rules must be evaluated separately before users place international calls.

No, agencies should not assume the same minute allowance or usage behavior applies everywhere, because domestic calling rules can vary by selected offer, country or region, tenant type, and Microsoft policy. Confirm the selected Government offer’s domestic minute allowances, fair-use rules, emergency calling requirements, overage behavior, and international calling behavior before deployment.

Often phone numbers can be ported to Microsoft Calling Plans where supported, but availability and timing must be validated, because number portability depends on country or region, number type, current carrier, tenant cloud, and Microsoft provisioning rules. Agencies should confirm porting eligibility and plan a migration window before cancelling existing carrier service.

The recommended approach is to validate eligibility, license prerequisites, number inventory, emergency locations, porting timelines, and user assignments before cutover, because Calling Plan migration affects both Microsoft licensing and public telephone service. Agencies commonly pilot a small group first, then port numbers and assign policies in phases to reduce service risk.

Emergency calling must be configured before production use, because PSTN voice service requires accurate emergency locations, calling policies, and compliance with applicable local emergency-calling regulations. Government agencies should validate E911 or local emergency requirements for each site, remote-work scenario, and tenant cloud before users rely on Teams as their primary phone service.

Yes, IT Partner can help validate the applicable Government Calling Plan SKU, because the catalog includes Governmental Community Cloud and GCC-labeled variants and the right choice depends on the tenant’s government cloud and Teams Phone prerequisites. This validation should happen before purchase to avoid assigning a Calling Plan that does not match the tenant or intended PSTN model.

A CSP partner change does not require moving the Microsoft tenant, because the tenant, users, and Teams configuration remain in Microsoft 365. License transition should still be planned carefully, often with overlapping subscriptions or coordinated renewal timing, to avoid gaps in assigned Calling Plan service; final pricing follows the selected Microsoft CSP Government offer and should be confirmed at checkout.

Cancellation, renewal, and seat changes follow the selected Microsoft CSP commitment terms, because monthly and annual commitments have different flexibility. Under typical Microsoft CSP new commerce rules, seats can generally be added during the term, while reductions or cancellations are limited to the allowed cancellation window or renewal; agencies should confirm the exact terms before ordering.