Skip to main content

Nerdio is Microsoft’s 2026 Americas ISV Partner of the Year Get the story

Blog

Microsoft 365 GCC vs GCC High for MSPs

Compare Microsoft 365 GCC vs GCC High for data classification, licensing, feature gaps, migration, and multi-tenant MSP management.

A 60-seat defense subcontractor asks you to quote "government Microsoft 365." Discovery turns up two problems.

First, the subcontractor's contracts involve Controlled Unclassified Information (CUI), the federal category for sensitive, unclassified data that still requires formal protection. CUI Basic can live in Government Community Cloud (GCC). CUI Specified, a tighter subset that covers DoD CUI and data governed by the International Traffic in Arms Regulations (ITAR), requires GCC High.

Secondly, your Cloud Solution Provider (CSP) agreement doesn't cover GCC High, and the tenant decision has to happen before provisioning.

This guide is for managed service provider (MSP) owners, practice leaders, and technical teams comparing Microsoft 365 GCC vs GCC High for regulated clients.

Microsoft 365 GCC and GCC High hold different data on different clouds

GCC and GCC High serve different customer sets, run on different Azure environments, and use different identity endpoints. An MSP should classify the customer's organization and regulated workload before selecting licenses or building the tenant, because that sovereignty line decides which regulated data each cloud may hold.

Who each cloud serves

Per Microsoft, GCC exists for "the United States Federal, State, Local, and Tribal governments, as well as contractors holding or processing data on behalf of the US Government."

GCC High exists for "the United States Department of Defense, as well as contractors holding or processing DoD controlled unclassified information (CUI) or subject to International Traffic in Arms Regulations (ITAR)."

Where the data lives

Both clouds store customer content at rest in US datacenters. GCC is a logically segregated partition of commercial Azure. GCC High runs on Azure US Government, Microsoft's sovereign cloud. Microsoft "will only agree to ITAR contract language for the GCC High environment."

For an MSP, the hosting-region difference establishes a contractual boundary.

How identity differs across the two clouds

Identity follows this split:

  • GCC tenants use public Microsoft Entra ID, with .onmicrosoft.com domains and sign-in at login.microsoftonline.com.
  • GCC High tenants use Microsoft Entra Government, with .onmicrosoft.us domains and sign-in at login.microsoftonline.us.

Every client-facing tool, including PowerShell and your management console, has to respect that .com/.us split, which is why Nerdio Manager for MSP ships a separate Gov Edition.

The data type decides the cloud, and CMMC by itself does not

When scoping a Cybersecurity Maturity Model Certification (CMMC) engagement for a client, MSPs typically encounter two kinds of CUI. CUI Basic can live in GCC, while CUI Specified, which includes ITAR-controlled and nuclear data, cannot. Microsoft publishes explicit data routing for the common data types MSPs run into when classifying a client's workloads, summarized in the table below.

Data type

Cloud

Microsoft's language

CUI Basic under DFARS 252.204-7012

GCC or GCC High

Microsoft's DFARS compliance page lists its Office 365 U.S. Government environments as adequate for DFARS

CUI Specified (ITAR, Nuclear)

GCC High

"GCC isn't suitable to hold CUI Specified (for example, ITAR, Nuclear, and so on). This type of data requires US sovereignty, which only GCC High offers."

Criminal justice (CJIS) and federal tax information (IRS 1075)

GCC

Microsoft names Office 365 GCC among the services that accommodate CJIS Security Policy customers and lists IRS 1075 among the requirements GCC addresses

DoD IL4/IL5, DFARS 7012, NIST 800-171, and ITAR together

GCC High or DoD

"The Office 365 GCC High and DoD environments support customers who need combined compliance support for DoD IL4/5, DFARS 7012, NIST 800-171, and ITAR."

 

The contract's data requirements determine the cloud even when CMMC applies. GCC satisfies the DFARS cloud requirement. Most Defense Industrial Base (DIB) contractors handling CUI are best served by Azure Government and Microsoft 365 GCC High, the US sovereign cloud pairing.

On July 13, 2026, the Department of War (formerly DoD) suspended Phase 2 requirements scheduled for November 10, 2026. For current pipeline planning, MSPs should keep Phase 1 and DFARS work on the schedule while Phase 2 remains paused. Phase 1 self-assessments remain active, and DFARS 252.204-7012 stays in force under the same suspension notice. Washington Technology reports that a September 3, 2026 acquisition memo made the pause binding regulation.

For MSP capacity planning, the pause changes the Phase 2 date, not the active Phase 1 and DFARS workload. Nerdio's CMMC FAQ provides additional framework context for client discovery.

GCC High gets the same products as GCC, but collaboration limits remain

GCC High used to lag commercial Microsoft 365 by a year or more on major product releases, which pushed some defense contractors to run a second commercial tenant for day-to-day productivity. That gap has mostly closed. The two flagship AI and data products Microsoft has shipped in the past two years both reached GCC High within a reasonable window of their commercial release.

Microsoft 365 Copilot, the generative AI assistant embedded in Word, Outlook, Teams, and Excel, reached general availability in GCC on December 13, 2024 and in GCC High on December 1, 2025. Microsoft Fabric, Microsoft's unified analytics and data warehousing platform, hit GCC High general availability on October 1, 2026.

Product parity has closed, but the sovereign-cloud boundary still narrows the collaboration surface in GCC High across four areas MSPs should set client expectations around:

  • Teams apps: Microsoft turns third-party apps off by default in GCC, but admins can enable them. GCC High has no third-party apps and no public Teams App Store, only tenant app sideloading.
  • Calling: GCC has native public switched telephone network (PSTN) calling and audio conferencing. GCC High supports Direct Routing only, which means clients bring their own Session Initiation Protocol (SIP) trunk and session border controller instead of buying calling plans from Microsoft.
  • Guests: GCC High allows Microsoft Entra B2B only between organizations inside Azure US Government, and Microsoft 365 Groups do not support B2B guests. Inviting a commercial-tenant contractor to a Teams channel or a SharePoint site is not supported.
  • Other gaps: Viva Engage (enterprise), Office Scripts, and the Power Platform connectors for Viva Engage and Business Central are unavailable. Internet calendar sharing is inbound only. Copilot web grounding, the feature that lets Copilot pull live information from the public web into its responses, ships off by default.

These collaboration limits are either tickets you will field or expectations you write into the SOW.

GCC and GCC High use different buying channels and admin tooling

GCC flows through the Cloud Solution Provider (CSP) channel most MSPs already use. GCC High does not. The downstream effects show up across several operational areas MSPs touch on every government deal:

 

GCC

GCC High

Buying channel

CSP; partner and customer both complete GCC qualification; New Commerce availability since March 1, 2024

Enterprise Agreement at 500+ seats; under 500, AOS-G (Agreement for Online Services for Government) through authorized government partners

Provisioning

No trial available

No trial available

Partner admin

GDAP works once Partner Center GCC qualification is complete

Needs a separate Azure Government footprint; Microsoft does not document Lighthouse support for GCC High tenants

Graph endpoint

graph.microsoft.com

Government Graph endpoint: graph.microsoft.us (Graph Explorer unsupported)

 

Microsoft raised government pricing for Microsoft 365 G3 by 8% and G5 by 5% across all government clouds on July 1, 2026. It published only the percentages. Microsoft does not publish binding absolute GCC High per-user prices, so quotes must come from an authorized AOS-G partner using current Partner Center pricing.

Admin tooling has to be rebuilt around that same .com/.us split:

  • Azure Lighthouse delegation stops at the cloud boundary:
    Lighthouse documentation states that "delegation of subscriptions across a national cloud and the Azure public cloud, or across two separate national clouds, isn't supported." A GCC High client tenant cannot be managed from your commercial Lighthouse delegation.
  • PowerShell needs government-specific connect commands:
    The US Government Graph requires Connect-MgGraph -Environment USGov, and GCC High Exchange requires Connect-ExchangeOnline -ExchangeEnvironmentName O365USGovGCCHigh. Default parameters hit the wrong cloud.
  • Scripts and apps written for commercial fail against GCC High:
    Anything still pointed at microsoftonline.com for a GCC High tenant returns the AADSTS900439 endpoint error. Every automation your team wrote for commercial Microsoft 365 has to be reviewed before it runs against a GCC High tenant.
  • Third-party management platforms need a government-cloud build:
    Nerdio Manager runs into the same split, which is why its Gov Edition installs from the Microsoft Marketplace in Azure Government rather than as an add-on to a commercial installation.

These separate endpoints and administrative contexts have to be built into the migration plan before any workload moves.

Changing clouds later requires a full tenant migration

Picking the wrong cloud at the start is expensive to undo. Moving a client from GCC to GCC High (or from commercial to either government cloud) requires standing up a new tenant and migrating data across cloud boundaries, and native Microsoft migration tooling doesn't cover the path.

The initial cloud recommendation carries cutover and schedule consequences the MSP will own. A low-risk migration blueprint structures that planning before the tenant mechanics begin.

Tenants cannot be converted between clouds

One Microsoft Q&A answer says you "need to create a new GCC authorized tenant and migrate your data." Another says "you cannot have both GCC High and Office 365 Business subscriptions on the same tenant."

A move from a commercial tenant to GCC therefore requires a new tenant and data migration, while GCC High and Office 365 Business subscriptions require separate tenants.

Native cross-cloud migration tooling doesn't exist

Cross-tenant OneDrive migration is not supported for users of the Government Cloud, including GCC, Consumer, GCC High, or DoD, and cross-tenant mailbox migration does not run cross-cloud.

Those native limitations make workload scoping and migration planning necessary before cutover. Nerdio Manager does not move mailbox or OneDrive data between GCC and GCC High. Once the MSP has scoped the cross-cloud data move and chosen a migration tool for the data itself, Nerdio Manager speeds up the work that comes after: standing up the GCC High enclave and managing it from there.

Enclaves are the alternative to full-tenant migration

When only part of the workforce handles CUI, scoping a GCC High enclave instead of migrating the whole organization is often the shorter path. Following its CMMC cloud guidance, Microsoft advises organizations with multiple business units to put them in one cloud environment with GCC High when they need the higher security bar and make that placement from the start.

A smaller migration can place only CUI-handling users and workloads in a GCC High enclave on Azure Virtual Desktop in Azure Government.

The DoD's CMMC FAQ describes conditions under which endpoints used only to access a virtual desktop (and that don't process, store, or transmit CUI themselves) can be treated as out-of-scope assets for the assessment. That carveout is what makes an enclave strategy viable, because it keeps the end-user devices outside the CUI boundary and limits the assessment surface to the Azure Virtual Desktop environment itself.

The DoD's CMMC Level 2 Assessment Guide similarly permits a certification assessment scoped to a specific enclave rather than the entire organization. On the Microsoft side, Azure Virtual Desktop supports multi-session hosts in Azure Government, which lets the enclave serve multiple CUI users from shared infrastructure instead of a dedicated VM per user.

Microsoft still cautions that "the most common spillage happens through personal storage, especially in email," meaning the enclave's assessment boundary breaks the moment a user forwards CUI to a commercial mailbox or saves it to personal OneDrive. The enclave architecture has to pair with user access controls that keep CUI inside it.

Operationally, enclave builds move faster than full-tenant migrations. C3 Integrated Solutions reports up to 80% faster onboarding with Nerdio Manager on CMMC enclave deployments. The tradeoff is scale. An enclave per client keeps each migration small but adds another Azure Government environment, with its own sessions, PowerShell context, and policy administration to maintain alongside the MSP's commercial estate.

Where Nerdio Manager fits in a GCC High practice

Nerdio Manager for MSP ships a separate Gov Edition built for this estate. It lets MSPs manage GCC High and Azure Government tenants from a single interface without switching tools or re-authenticating, deploys inside the MSP's Azure Government tenant, and runs under deployment, licensing, and pricing requirements that differ from the commercial product. Note that Gov Edition does not support DoD.

Scope posture and the SSP boundary

The DoD Level 2 Scoping Guide places an external service provider inside the client's assessment scope whenever CUI or Security Protection Data resides on the provider's assets.

Gov Edition deploys entirely inside the MSP's Azure Government tenant with no external control plane, and Nerdio does not store, transmit, process, or host federal data. The assessor still sets scope in the client's System Security Plan (SSP). Nerdio Manager is the management layer and does not determine or certify scope itself.

Deployment, licensing, and pricing requirements

The operating requirements for standing up Gov Edition are as follows:

  • The deployment requires two instances. You can reuse an existing instance in your Azure Commercial tenant and install the other from the Microsoft Marketplace in your Azure Government tenant. Gov Edition sends usage data to Nerdio for invoicing through the commercial installation.
  • Your MSP needs its Azure Government subscription from a reseller on Microsoft's  authorized government reseller list. Authorized AOS-G partners can provide Microsoft 365 GCC High licenses, but some distributors do not provide Azure Government.
  • Console Connect and Partner Center integration are unavailable in Gov Edition.
  • Nerdio Manager for MSP offers both per-user and per-tenant pricing, and Gov Edition for Azure Government and GCC High has its own monthly minimum. Current pricing and volume discounts are available through Sales.

MSPs should weigh that minimum against technician time spent on separate portal.azure.us sessions, separate PowerShell environments, and policy work repeated per tenant.

Proof point from a CMMC-specialist MSP

C3 Integrated Solutions built Creation Tech's CMMC environment on Azure Virtual Desktop in Azure Government with Nerdio Manager. Creation Tech achieved CMMC Level 2 certification in June 2025. "C3 directly addressed roughly 80 of the 110 CMMC controls," said Raegan Gibb, Creation Tech's Director of Business Systems & IT Operations. The Creation Tech case study highlights Nerdio Manager automation, including patented auto-scaling. In a C3 team member's words, "we'll be able to deploy one set of policies for all our compliance customers and know it's deployed 100%."

That architecture lives on Azure Government and Azure Virtual Desktop, with Nerdio Manager as the management layer, and which clients need it traces back to the data classification you ran in discovery.

What this means for your government practice

Back to the 60-seat subcontractor. If the contract data is CUI Basic with nothing ITAR-controlled, GCC through your existing CSP relationship is the shorter path. If the contract carries ITAR clauses or CUI Specified, or plausibly will within the term, evaluate GCC High from day one, buy through an AOS-G partner, allow for the longer provisioning runway, and write the Teams and calling limits into the SOW. A handful of CUI users inside a larger commercial workforce fits the enclave case on Azure Virtual Desktop in Azure Government.

Either path grows the tenant count across two clouds with two identity boundaries, and repeated per-tenant policy administration becomes a scaling constraint as the client count grows. Nerdio's multi-tenant operations guide covers the broader operating model.

To manage Microsoft 365 GCC High and Azure Government across client tenants from a single console, get a demo of Nerdio Manager or walk through the self-guided MSP demo first.

Frequently asked questions about Microsoft 365 GCC vs GCC High

Ready to get started?