GCC High is a separate cloud. Decide who moves before you buy.
- We read your contracts and tell you plainly whether you need Microsoft 365 GCC High, GCC or neither.
- Where an enclave for the people who touch CUI is enough, we say so.
- We build the tenant, move mail and files, and write the SSP and evidence with your IT team or MSP.
200+ Microsoft 365 and Azure tenants. 100+ engagements. 20+ years in regulated technology.
Last checked
What the rules ask of the cloud that holds CUI
Neither DFARS nor CMMC names a Microsoft product. They set a floor for any cloud, and a reporting duty that stays with you.
Clause dated
In force
Your cloud must meet the FedRAMP Moderate floor
If a cloud service stores, processes or transmits covered defense information, DFARS 252.204-7012 requires the provider to meet security requirements equivalent to the FedRAMP Moderate baseline. The provider must also follow the clause’s terms for incident reporting, malicious software, media preservation, forensic access and damage assessment.
Clause dated
Your duty
You report incidents within 72 hours
Cyber incidents go to DoD at dibnet.dod.mil within 72 hours of discovery, using a DoD approved medium assurance certificate. Images of affected systems are kept for at least 90 days after the report. This stays with you in any cloud.
In force
CMMC Level 2 sets the same floor
Under 32 CFR 170.16 and 170.17, a cloud service that holds CUI must be FedRAMP Authorized at Moderate or higher, or meet equivalent requirements. CMMC Phase 2 is suspended, and the DoD CIO notes that DFARS 252.204-7012 still applies.
Read more: CMMC readiness and where CMMC stands, NIST SP 800-171 Rev 3 versus Rev 2.
Commercial, GCC or GCC High
GCC and GCC High both carry FedRAMP High, so the authorization alone does not decide it. The data your contracts name does.
| Cloud | Meant for | CUI and export controlled data | Identity |
|---|---|---|---|
| Microsoft 365 commercial | The standard Microsoft 365 most companies already use | Microsoft lists it for CMMC Level 1, where contracts involve FCI only | Entra ID in Microsoft’s commercial cloud |
| GCCGovernment Community Cloud | US federal, state, local and tribal government, and contractors holding or processing data for them. Microsoft validates eligibility first. | FedRAMP High and DFARS are listed. Microsoft calls GCC the offering for customers that do not hold DoD CUI, and says it is not suitable for CUI Specified, such as export controlled data. | Entra ID in Microsoft’s commercial cloud, the same as commercial tenants |
| GCC High | Defense contractors and agencies that hold DoD CUI or export controlled data. Microsoft validates eligibility first, and licenses come only through partners it authorizes. | FedRAMP High, DFARS and DoD SRG Impact Level 4 controls. Microsoft lists it for CMMC Level 2, when configured appropriately. | Entra ID in Azure Government, a separate cloud with its own sign in and admin addresses |
Buying GCC High does not make a tenant compliant. Microsoft says CMMC compliance depends on your configuration, implementation and operational controls, which is the work further down this page.
An enclave for the people who touch CUI, or everyone
Microsoft describes both approaches. Which one fits depends on how far CUI travels inside your company.
An enclave
Only the people who touch CUI get GCC High accounts. Everyone else stays in your current tenant.
- Fits when
- A defined group handles CUI, and it reaches you through a few known routes, such as one prime and a handful of mailboxes.
- Saves
- Fewer GCC High licenses. The rest of the company keeps its current tools.
- Costs
- Two tenants to run, and two accounts for the people inside. They have to reply where the CUI lives, because email is where spills most often happen.
- Sharing
- Your two tenants do not trust each other by default. Guest access between them needs cross cloud settings in Entra ID on both sides.
- Scope
- Systems that cannot reach CUI and are kept separate from it can stay out of your Level 2 assessment scope.
- Email domain
- Usually its own, because a domain can be verified in only one tenant.
Everyone
The whole company moves to GCC High, and the commercial tenant is retired.
- Fits when
- CUI runs through engineering, programs, contracts and email across the company, or business units cannot be split cleanly.
- Saves
- One tenant and one account per person, with no line to police between two clouds.
- Costs
- More licenses, a larger migration, and some commercial features and integrations that GCC High does not offer.
- Sharing
- Partners on commercial Microsoft 365 cannot simply be invited as guests. Both sides set up cross cloud settings in Entra ID first.
- Scope
- Every person and device that can reach CUI is in scope, which is most of the company.
- Email domain
- Moves to the new tenant at cutover.
Microsoft’s own guidance weighs the same trade: an enclave can help manage cost, and email is the most common route for spills.
How we build it, step by step
The same six steps in every GCC High engagement. How long each takes depends on your contracts, your data and how many people move, so each step says what sets the time instead of a length.
-
Scope CUI and who touches it
What sets the time How many contracts name CUI, and how many places it already lives
We read the contracts and DFARS clauses, then trace where CUI arrives and where it goes: mail from primes, drawings, shared folders and laptops. Each role is marked as touching CUI or not, and that list decides between an enclave and moving everyone.
You get A CUI scope map, a list of who moves and a written cloud decision
-
Validation and licenses
What sets the time Microsoft’s eligibility check, and your reseller’s ordering
Microsoft validates your eligibility before the tenant exists. Licenses come only through a partner Microsoft authorizes to sell GCC High, so we size the order by role with that reseller: the people who touch CUI, and the admins who run the tenant.
You get A license list by role, ready for your reseller
-
Build the tenant
What sets the time How many devices, apps and policies have to be rebuilt in the new cloud
Entra ID with MFA and Conditional Access. Intune for every laptop that will touch CUI, built with Autopilot device preparation, because classic Windows Autopilot is not offered in GCC High. Defender for endpoints, mail and identity. Purview sensitivity labels and data loss prevention for CUI.
You get A build record of every setting, with the reason for each
-
Move mail and files
What sets the time How much mail and data moves, and how many people work with outside companies
Microsoft’s cross tenant mailbox and OneDrive moves do not run from a commercial tenant into GCC High, so we use a migration tool that supports it and move people in planned batches. A domain can be verified in only one tenant, so your email domain moves at cutover, or the enclave gets its own.
You get A cutover plan, and a record of what moved and what was removed from the old tenant
-
SSP and evidence
What sets the time How much is already documented, and who owns the requirements met outside the tenant
The SSP is written from what is built. It shows what Microsoft covers in GCC High, what you cover, and what is met outside the tenant, such as physical access and personnel screening. Each of the 110 NIST SP 800-171 requirements gets its evidence and an owner.
You get An SSP and an evidence map an assessor can follow
-
Handover
What sets the time Who will run the tenant, and how familiar they are with GCC High
Admin roles, the build record and the evidence schedule go to your IT team or MSP. GCC High has its own sign in and admin addresses, such as portal.office365.us and security.microsoft.us, so we walk them through each one.
You get A tenant your team can run, and evidence that stays current
What we need from your side
The contracts that name CUI, an admin for your current tenant, a person who can approve who moves, someone who can sign the license order, and time from the people who own physical security, HR and policies.
Read more: the CMMC Level 2 gap assessment, a defensible SPRS score.
What you get shows who moved, what was built and why
Three formats from a GCC High engagement. Each one is a sample format with illustrative content, not a client’s document.
Who moves
Every role, how CUI reaches it and where it lands. The enclave decision comes from this list.
Who moves to GCC High
Sample format, illustrative content
| Role | CUI reaches them through | Moves to | Note |
|---|---|---|---|
| Program managers | Email and drawings from the prime | GCC High | Keep a commercial account for other work |
| Design engineers | Drawings and models marked CUI | GCC High | Laptops enroll in Intune in GCC High |
| Contracts lead | Contract documents marked CUI | GCC High | Reviews CUI only in GCC High |
| Sales | None found | Commercial | No change |
| Finance | None found | Commercial | No change |
| IT admins | Run both tenants | Both | Separate admin accounts in each tenant |
Tenant build record
Every setting in the new tenant and why it is there, so your team can run it and an assessor can test it.
GCC High tenant build record
Sample format, illustrative content
- Identity
- MFA for every account. Conditional Access allows sign in only from compliant devices.
- Devices
- Intune compliance policies. Laptops built with Autopilot device preparation.
- Defender
- Endpoints, mail and identity covered. Alerts reach the IT lead.
- Purview
- A CUI label. Data loss prevention stops labeled files leaving for outside domains.
- Admins
- Admin accounts kept separate from daily accounts.
Cutover plan
Who moves when, and how CUI left behind in the old tenant is found and removed.
Cutover plan, enclave
Sample format, illustrative content
- Before
- Users and licenses created. Migration tool connected to both tenants.
- First batch
- Program managers: mail and OneDrive
- Second batch
- Engineering: SharePoint sites and file shares
- Cutover
- Mail flow switched, final sync, people sign in at the new addresses
- After
- CUI left in the commercial tenant found and removed
Work we have delivered
What we can say about past defense work without naming clients.
Defense contractor, CMMC Level 2
-
GCC High
We built its GCC High environment.
-
SSP
We wrote its System Security Plan.
-
Evidence
We ran its evidence program.
-
Result
It passed its CMMC Level 2 C3PAO assessment, with every requirement met.
How long a build takes depends on your contracts, your data and who moves, so we do not quote it before scoping.
-
Defense, plan of action
A Level 2 POA&M that an Air Force Research Laboratory program office accepted as the basis for releasing CUI.
Who this is for, and who it is not for
A good fit
- Defense contractors on Microsoft 365 with DFARS 252.204-7012 or CUI named in their contracts.
- Companies whose prime has asked where CUI is stored, or whether they are ready for CMMC Level 2.
- Organizations that already bought GCC High and need it built, documented and handed over.
- IT teams and MSPs that want a specialist beside them for the build.
Not a fit
- Your contracts involve FCI only. Microsoft lists commercial Microsoft 365 for CMMC Level 1, so you may not need GCC High.
- You need a ruling on whether your data is CUI or export controlled. Your contracting officer, prime or counsel makes that call, and we build from their answer.
- You need the assessment itself. We are not your assessor.
- You need help desk support.
- You want a guaranteed result. Nobody can honestly promise one.
Questions before you book
Do we need GCC High for CMMC Level 2?
Not by name: DFARS 252.204-7012 and CMMC require a cloud that meets FedRAMP Moderate or its equivalent, and you must make sure that cloud follows the clause’s reporting terms. For DoD CUI in Microsoft 365, Microsoft’s own guidance points to GCC High rather than commercial Microsoft 365 or GCC.
Can we keep CUI in GCC instead?
Microsoft lists FedRAMP High and DFARS for GCC, but describes it as the offering for customers that do not hold DoD CUI and says it is not suitable for CUI Specified, such as export controlled data. If your contracts name DoD CUI, we plan around GCC High and record the reasoning in your SSP.
Does the whole company have to move?
No. When a defined group handles CUI, an enclave in GCC High for those people can be enough, as long as they work on CUI only there and keep that email inside the boundary.
Can Microsoft’s own tools move our mail and files?
Not across clouds: Microsoft’s cross tenant mailbox and OneDrive moves do not run from a commercial tenant into GCC High. We use a migration tool that supports GCC High and move people in planned batches, with a final sync at cutover.
Who reports an incident, Microsoft or us?
You do, within 72 hours of discovery, to DoD at dibnet.dod.mil with a DoD approved medium assurance certificate. You must also make sure your cloud provider follows the clause’s reporting terms, and we set up the logging and alerts you will need to report.
Do you replace our IT provider or MSP?
No. We build the tenant and move the data with your IT team or MSP, then hand over the admin roles, the build record and the evidence so they can run it day to day.
What happens after you book
- Pick a 30 minute time that suits you.
- We talk through your contracts, who touches CUI and your current tenant.
- You leave knowing which cloud fits and whether an enclave would do.
Bring the clause and a list of who touches CUI to a 30 minute call.
You leave knowing whether you need GCC High, who should move and what comes first. If you have an active incident, call (786) 577-9743 now rather than booking.