SharePoint (Plan 2) Government — Pricing, Plans & What's Included

SharePoint (Plan 2) for Government is a standalone per-user SharePoint license offered under Governmental Community Cloud Pricing, because it is intended for eligible government tenants that need SharePoint service access without buying a broader Microsoft 365 suite. It is commonly evaluated for intranets, portals, document management, content collaboration, and SharePoint planning scenarios.

SharePoint (Plan 2) Government includes standalone SharePoint licensing for assigned users, because the SKU is positioned as SharePoint Plan 2 rather than a full Microsoft 365 bundle. Exact SharePoint capabilities, storage entitlements, and any government-cloud variations should be confirmed against the current Microsoft service description and the customer’s tenant before purchase.

SharePoint (Plan 2) Government is not a full Microsoft 365 suite, because the SKU information identifies it as standalone SharePoint licensing. Microsoft 365 desktop apps, Exchange Online, Microsoft Teams, Teams Phone, Audio Conferencing, Windows, Power BI, and broader security or compliance suites may require separate licenses if the agency needs those capabilities.

Eligible government customers can buy SharePoint (Plan 2) under Governmental Community Cloud Pricing, because Microsoft restricts government cloud offerings to qualified organizations and approved tenant environments. Agencies should confirm eligibility, tenant type, and ordering path with IT Partner before placing the order.

Do not assume the same ordering path applies to GCC and GCC High, because Microsoft government cloud availability can vary by environment, reseller authorization, and tenant configuration. Before purchase, confirm whether the customer’s tenant is GCC, GCC High, or another government environment and verify that this exact SharePoint (Plan 2) SKU is available for that tenant.

SharePoint (Plan 2) Government may support government-cloud residency requirements when deployed in an eligible government tenant, because Microsoft government cloud environments are designed for government-sector compliance needs. The exact residency, boundary, and compliance commitments depend on the tenant environment, so agencies should verify current Microsoft documentation for GCC or GCC High before ordering.

Yes, SharePoint (Plan 2) Government is available as a monthly term billed monthly, because the Government pricing options include a monthly commitment option. This gives the most flexibility, while annual commitment options are better when the agency wants a longer commitment structure.

SharePoint (Plan 2) Government can be purchased as a monthly term billed monthly, an annual term paid upfront, or an annual term paid monthly, because all three Government purchasing options are listed for this SKU. Annual upfront has the lowest per-seat run rate among the listed options, annual paid monthly has a higher run rate, and monthly term provides the most flexibility.

No trial is listed for SharePoint (Plan 2) Government in the provided SKU information, because the Government entries are paid purchasing options rather than trial offers. If an agency wants to test functionality first, it should confirm available evaluation paths with IT Partner before procurement.

Users who need licensed SharePoint service access should be assigned an appropriate license, because SharePoint (Plan 2) Government is sold per user. Licensing needs can differ for administrators, internal collaborators, external users, and users already covered by another Microsoft 365 plan, so the agency should review assignments before purchase.

No, Microsoft Teams is not identified as included in this standalone SharePoint SKU, because SharePoint (Plan 2) is not a Microsoft 365 suite license. SharePoint can work alongside separately licensed Microsoft services in the same tenant, but Teams licensing and government-cloud availability should be verified separately.

No, the standalone SharePoint (Plan 2) Government SKU should not be treated as including Microsoft 365 desktop apps or Exchange Online, because those workloads are not identified as part of this SKU. If the agency needs Office apps, email, calendars, or Outlook-based workflows, it should verify and license those services separately.

Do not assume SharePoint (Plan 2) Government by itself satisfies Microsoft 365 Copilot prerequisites, because Copilot eligibility depends on the customer’s tenant, cloud environment, base licenses, identity configuration, and Microsoft’s current government availability rules. Agencies evaluating Copilot should confirm prerequisite licenses, data access controls, and government-cloud support with IT Partner before buying.

Some SharePoint capabilities may support content governance, but agencies should not assume all compliance requirements are included, because advanced retention, eDiscovery, records, DLP, audit, or information protection scenarios may require Microsoft Purview, Microsoft 365 E5, or other add-ons. The safe approach is to map each compliance requirement to the current Microsoft service description for the agency’s government tenant.

SharePoint (Plan 2) Government can be part of a secure document management design, because SharePoint supports permissions, site governance, document libraries, and administrative controls when configured correctly. Security outcomes depend on tenant settings, identity controls, sharing policies, compliance licensing, and user administration, so agencies should validate the full security design before deployment.

External collaboration may be possible, but it should be verified before rollout, because sharing behavior depends on the government cloud environment, tenant settings, administrator policies, and agency restrictions. IT Partner can help confirm whether guest access, external sharing, or contractor collaboration is allowed for the specific tenant and use case.

Yes, many agencies migrate content into SharePoint, because SharePoint is commonly used for document libraries, sites, and portals. The license purchase alone does not perform the migration, so the agency should plan identity, permissions, metadata, retention, link remediation, user training, and any government-cloud migration tooling constraints before starting.

The agency should confirm government eligibility, tenant environment, required SharePoint features, storage expectations, collaboration policies, and adjacent workload needs, because SharePoint (Plan 2) is a standalone SharePoint SKU rather than a complete Microsoft 365 solution. It should also verify whether requirements for Teams, Office apps, Exchange, Purview, identity, endpoint management, or Power BI require separate licensing.

Yes, a CSP billing transfer can typically be handled without SharePoint service downtime, because the Microsoft tenant and SharePoint data do not need to be migrated just to change the CSP purchasing relationship. IT Partner can help align the subscription to the correct Government SKU and the same Microsoft-published pricing option for the selected term and billing model, but the final invoice terms should be confirmed before transfer.

Rules depend on the selected commitment, because monthly terms are designed for flexibility while annual terms create a longer subscription commitment. Seat increases are generally easier during a term than reductions or cancellations, which may be limited to renewal or the applicable cancellation window, so agencies should confirm the exact CSP terms with IT Partner before ordering.