Microsoft Teams Shared Space for Government — Pricing, Plans & What's Included

Microsoft Teams Shared Space is a Microsoft Teams Shared Space catalog subscription with Government pricing options, because the source catalog lists this product under the Government segment. It should be treated as a Government catalog offer until Microsoft’s current entitlement, assignment, and service-availability guidance is confirmed for your tenant.

The source catalog confirms a Government subscription listing for Microsoft Teams Shared Space, because it shows Government SKUs for the main offer and for Microsoft Teams Shared Space – Single Space. The catalog does not provide a full entitlement matrix, so included services, assignment rules, and exclusions should be confirmed with IT Partner before deployment.

Microsoft 365 desktop apps, mailbox rights, user-suite rights, Teams Phone capabilities, PSTN connectivity, and shared-device licensing rights are not confirmed by the source catalog, because the catalog only identifies the subscription listings and terms. Government buyers should not assume this offer replaces Microsoft 365, Teams Rooms, Teams Phone, common-area phone, or device licensing without current Microsoft confirmation.

The Government catalog includes both the main Microsoft Teams Shared Space SKU and a Microsoft Teams Shared Space – Single Space SKU, because both appear as Government pricing options in the source catalog. The source does not define how the Single Space SKU is assigned or whether it is paired with, replaces, or differs from the main SKU, so IT Partner should validate the correct SKU for your tenant and use case before ordering.

The assignment model is not confirmed in the source catalog, because the catalog lists the subscription but does not state whether it is assigned to a named user, device, resource account, room, workspace, or another object. Before purchase, confirm Microsoft’s current assignment guidance for the applicable Government cloud.

No replacement should be assumed, because the source catalog does not state that Microsoft Teams Shared Space includes standard Microsoft 365 user-suite rights. If staff need email, Office apps, OneDrive, Teams user rights, compliance features, or other Microsoft 365 workloads, those requirements should be licensed separately according to Microsoft’s current Government licensing rules.

Teams Phone and PSTN connectivity are not confirmed as included, because the source catalog does not list calling entitlements or telecom services for this offer. If your shared space needs inbound or outbound calling, emergency calling, resource accounts, calling plans, Operator Connect, Direct Routing, or related configuration, IT Partner should validate the required add-ons and Government cloud availability.

Microsoft Copilot is not confirmed as included, because the source catalog does not list Copilot entitlements for Microsoft Teams Shared Space. If your agency wants Copilot in Teams or Microsoft 365, confirm separate Copilot eligibility, identity prerequisites, data boundary requirements, and Government cloud availability before purchase.

Do not assume it covers Teams Rooms, panels, common-area phones, or shared devices, because the source catalog does not map Microsoft Teams Shared Space to those Microsoft licensing categories. Government buyers should confirm whether the intended device or workspace requires Teams Rooms, Teams Shared Devices, Teams Phone, Intune, Entra ID, or another prerequisite license.

No trial is listed, because the source catalog marks the Government options as non-trial offers. Government buyers should plan around paid monthly or annual commitment options and confirm the current catalog availability before ordering.

The source catalog lists monthly and annual commitment options for Government, because it shows a monthly term and annual terms with different billing choices. The monthly commitment generally provides more flexibility, while an annual commitment may fit agencies that want a longer planned term; confirm the exact CSP catalog option before placing the order.

Quantity changes depend on the selected Microsoft CSP term and current commerce rules, because monthly and annual commitments can have different change, cancellation, and reduction limits. Before ordering, IT Partner should confirm whether the subscription can be increased midterm, reduced at renewal only, or changed within any applicable cancellation window.

Renewal and cancellation behavior depends on the chosen CSP term, because monthly and annual commitments are governed by Microsoft’s current commerce policies and the subscription settings selected at purchase. Government buyers should confirm auto-renewal status, cancellation windows, reduction rules, and renewal-date alignment with IT Partner before committing.

Government pricing is listed in the catalog, but GCC service availability still must be confirmed, because the source catalog does not specify the exact Government cloud environment or service boundary. IT Partner should validate whether the offer is available and appropriate for your GCC tenant before purchase.

GCC High or DoD availability should not be assumed, because the source catalog does not explicitly confirm GCC High or DoD support for Microsoft Teams Shared Space. If your agency or contractor requires GCC High, controlled unclassified information handling, or a specific government cloud boundary, confirm Microsoft’s current availability and compliance documentation before ordering.

The source catalog confirms a Government pricing listing but does not provide data residency, compliance, or certification details, because it is a commerce listing rather than a service-compliance matrix. Government buyers should validate the applicable Microsoft cloud boundary, data location, audit requirements, and agency-specific compliance obligations before deployment.

You should confirm the entitlement matrix, assignment model, target Government cloud, related device requirements, and any calling or identity prerequisites, because the source catalog does not define the full deployment architecture. IT Partner can help determine whether the main SKU or Single Space SKU fits the workspace scenario and whether additional Microsoft 365, Teams, Phone, Intune, or Entra ID licensing is needed.

Migration may be possible only after the licensing and technical mapping is validated, because the source catalog does not state that this offer replaces existing Teams Rooms, common-area phone, shared-device, or resource-account configurations. A safe migration plan should inventory current licenses, devices, resource accounts, Teams policies, calling dependencies, and Government cloud constraints before changes are made.

A CSP partner transfer typically changes the partner relationship rather than moving tenant data, because Microsoft 365 services remain in the customer tenant. IT Partner should coordinate the transfer so subscriptions, renewal dates, delegated admin permissions, and support responsibilities are validated, with no planned service interruption when the transfer is handled correctly.

Switching CSP management should not require a tenant rebuild or workload migration, because the Microsoft tenant and service data remain in place. Pricing should be quoted from the current Microsoft/CSP catalog for the same Government offer, term, and billing option, but IT Partner should confirm the active subscription terms and any Microsoft price changes before transfer.