A CUI enclave that keeps your scope small.
Put CUI in one tightly controlled place instead of protecting it everywhere. We build an enclave on Microsoft 365 GCC High with Azure Virtual Desktop in Azure Government, so only the enclave and the people who use it are in scope for CMMC Level 2.
CUI lives in the enclave. Endpoints only see the screen.
Your people connect to a virtual desktop inside the boundary. Their laptop sends keystrokes and receives pixels, and the CUI never lands on it.
- GCC High for the people who handle CUIEmail, Teams, SharePoint and OneDrive in the Microsoft cloud built for CUI and ITAR.
- Azure Virtual Desktop in Azure GovernmentSession hosts, user profiles and storage all inside the same sovereign boundary.
- Locked-down connectionsClipboard, drive and printer redirection off, and access only through Conditional Access with strong MFA.
- Security inside the boundaryDefender, Purview and Sentinel deployed in the enclave, so monitoring and evidence stay in scope with the data.
Protect less, prove more
A smaller assessment
Fewer assets, users and locations in scope means less to implement, less to document and less for an assessor to test.
The rest of the business stays put
People who never touch CUI keep working in commercial Microsoft 365, with no migration and no new restrictions.
Work from anywhere, safely
Remote staff and subcontractors reach CUI from a controlled desktop instead of storing it on devices you have to bring into scope.
From scoping to assessment-ready
Scope
Find where CUI comes from, who needs it and which apps touch it, then draw the boundary.
Build
GCC High tenant, Azure Government subscription and Azure Virtual Desktop, deployed as code with a hardened baseline.
Secure
Conditional Access, Intune, Defender, Purview labels and DLP, and Sentinel, all inside the enclave.
Move in
Migrate CUI and onboard users with approved workflows for printing and file transfer.
Document
Boundary diagrams and SSP content that match what was actually built, with evidence from your own tenant.
What to plan for
- GCC High eligibilityMicrosoft validates eligibility before you can buy GCC High licenses. We help with the paperwork.
- An Azure Government subscriptionThe virtual desktops run in Azure Government and are billed for what they use.
- New habits for enclave usersCUI work happens in the virtual desktop. We plan training and workflows so it feels routine.
Why does a virtual desktop shrink the scope?
Under the CMMC rule (32 CFR 170.19), an endpoint running a virtual desktop client that is configured so no CUI is processed, stored or transmitted beyond keyboard, video and mouse is an out-of-scope asset. CUI work happens on session hosts inside the enclave, so the laptops people connect from stay out of the assessment.
Does the whole company have to move to GCC High?
No. Only the people who handle CUI get GCC High accounts and enclave access. Everyone else, and everyone's day-to-day email and files that are not CUI, can stay in commercial Microsoft 365.
What stays in scope?
The enclave itself: the GCC High tenant, the Azure Virtual Desktop session hosts and storage in Azure Government, and the security tools that protect them. The people with access are in scope too, and the boundary has to be documented in your SSP.
What about printing and moving files in and out?
Clipboard, drive and printer redirection are turned off to keep endpoints out of scope, so printing and file transfer are designed on purpose: approved workflows inside the enclave, not workarounds. We plan these with you before go-live.
Can we use Windows 365 instead of Azure Virtual Desktop?
Sometimes. Windows 365 Cloud PCs in GCC High can fit small teams that want a simpler, per-user model. We recommend whichever fits your users, apps and budget.
Keep your CMMC scope small
Tell us who handles CUI and where it comes from. We'll sketch the boundary and what the enclave would take.
