Skip to main content

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

Blog

CMMC for virtual desktop environments: what defense contractors need to know about AVD

See how Azure Virtual Desktop shrinks assessment scope and what controls you still own inside the enclave.

The Cybersecurity Maturity Model Certification (CMMC) is in flux. On July 13, 2026, the Department of Defense suspended Phase 2 of the CMMC rollout, the milestone that would have made third-party Level 2 certification a condition of contract award starting November 10, 2026. That mandate remains on hold until further notice. A task force ran a 60-day review that closed in September 2026, and no replacement date has been announced.

Your compliance obligations continue through the pause. Self-assessment against NIST SP 800-171 Rev 2 still applies, DFARS reporting still applies, and if you handle Controlled Unclassified Information (CUI), the architecture you choose for your desktop estate still drives your cost, your assessment scope, and how quickly you can certify once the mandate returns.

This guide is for defense contractor IT and compliance leaders, the end-user computing (EUC) business owners, and governance, risk and compliance (GRC) gatekeepers deciding how Azure Virtual Desktop fits a CMMC strategy.

Azure Virtual Desktop changes your CMMC assessment boundary by moving CUI work into a controlled enclave, but the session hosts and workload controls remain your responsibility.

Why the CMMC clock drives the decision

The certification deadline is paused but the architecture decision still drives your cost, your assessment scope, and your readiness for the day the mandate returns.

CMMC requirements began appearing in DoD solicitations on November 10, 2025, when the revised CMMC acquisition rule became effective. The Defense Federal Acquisition Regulation Supplement (DFARS) clause DFARS 252.204-7021 defines the contractor CMMC status requirement, and that clause remains in force.

Phase 1 is still active. Contracts can require Level 1 or Level 2 self-assessments as a condition of award, and contractors still post scores and annual affirmations in the Supplier Performance Risk System.

Phase 2 is the piece now on hold. It would have required third-party certification from a Third-Party Assessment Organization (C3PAO) at Level 2 starting November 10, 2026. The July 2026 memo directs contracting officers to leave that requirement out of new solicitations and to remove it from existing contracts, and it pauses the later Level 3 milestones as well. No replacement date has been set.

The Cybersecurity Maturity Model Certification verifies that contractors have implemented the security measures required to safeguard Federal Contract Information (FCI) and CUI. It pulls requirements from three sources, including FAR 52.204-21 for 15 basic safeguarding requirements, NIST SP 800-171 Rev 2 for 110 security requirements, and a subset of 24 requirements from NIST SP 800-172 for advanced persistent threat (APT) protection.

The three levels map to data sensitivity:

Level

Data type

Security basis

Assessment

Level 1 (Foundational)

FCI

15 practices from FAR 52.204-21

Annual self-assessment

Level 2 (Advanced)

CUI

110 requirements from NIST SP 800-171 Rev 2

Self-assessment or C3PAO triennial

Level 3 (Expert)

CUI + APT risk

NIST SP 800-171 + 24 requirements from 800-172

DCMA DIBCAC government-led

Many defense contractors handling CUI land at Level 2. DoD estimates roughly 135 C3PAO-led assessments in Year 1, climbing to 673 in Year 2. That thin assessor capacity is one of the reasons the department paused Phase 2, and it is the same reason the certification queue will be a constraint whenever the mandate returns.

The faster you can shrink what an assessor has to look at, the faster you get through certification whenever it becomes mandatory, which is exactly where a virtual desktop enclave changes the math.

How a virtual desktop enclave shrinks your assessment scope

A correctly configured virtual desktop deployment moves CUI off the local endpoint and into a controlled cloud enclave. User endpoints fall out of CMMC assessment scope entirely. The session hosts stay in, but the population of assets an assessor has to review drops sharply, and so does the assessment cost.

The DoD scoping rule that makes it work

The Level 2 Scoping Guide (Version 2.13, September 2024) says:

"An endpoint hosting a VDI client configured to not allow any processing, storage, or transmission of CUI beyond the Keyboard/Video/Mouse sent to the VDI client is considered an Out-of-Scope Asset."

Virtual Desktop Infrastructure (VDI) centralizes user sessions away from the local endpoint. When the session runs in a controlled cloud enclave and the user is "simply viewing pixels, hearing audio, and sending keystrokes," CUI never lands on the local device, and that device falls out of scope.

NIST SP 800-171 still applies to virtual machines, workstations, servers, and applications, so virtual desktops shift where the controls live rather than removing the standard.

The math changes anyway.

What scope reduction looks like in practice

Take a contractor with 175 employees where only 10 actually touch CUI. Without an enclave, all 175 endpoints, their hardware, and their physical locations land inside assessment scope by default. Route those 10 CUI handlers through a segmented cloud enclave and the other 165 endpoints stay out. Assessment cost, duration, and ongoing compliance burden drop with them.

What stays in scope inside the enclave

The session host virtual machines (VMs) in Azure Government remain in scope as CUI Assets. A session host is the VM hosting user sessions in Azure Virtual Desktop, and scope reduction applies to user endpoints rather than the cloud infrastructure hosting CUI. You are trading a large, scattered endpoint perimeter for a small, centralized, hardened one.

What you must enforce for endpoints to stay out of scope

The DoD FAQ specifies that the endpoint only stays out of scope if it meets every one of these conditions:

  • Copy-paste, file transfers, screenshots, saving, or printing of CUI are blocked
  • All CUI is handled entirely within the VDI session
  • Only video, keyboard, and mouse data is transmitted to the endpoint
  • Multifactor authentication (MFA) is implemented to the VDI server, separate from the endpoint (hardware tokens or PKI with PIN)

Microsoft documents Azure Virtual Desktop native controls that enforce these restrictions. You can enable screen capture protection to prevent sensitive screen information from being captured on client endpoints, disable clipboard redirection so remote content cannot be copied to the endpoint, hide local and remote drive mappings in Windows Explorer, and control device redirection to block local hard drive access, USB ports, camera redirection, and remote printing.

If one of these controls is wrong, the endpoint snaps back into scope as a CUI Asset. Improper VDI configuration is a common scoping failure flagged in the ND-ISAC VDI white paper, which is why the enclave's value depends entirely on the controls inside it being correct.

The endpoints come out of scope, the session hosts stay in scope, and those hosts inherit a set of controls you are now responsible for proving.

The controls you still own inside the Azure Virtual Desktop enclave

Azure Government or GCC High reduces your platform burden, but it does not eliminate your workload responsibilities. The controls below are yours to configure, document, and prove. Microsoft's own CMMC guidance puts it plainly: "CMMC Compliance can't be 100% inherited. Even in the cloud, you must own your responsibilities." Microsoft manages the platform layer. The workload layer is yours.

For Azure Virtual Desktop specifically, Microsoft manages most components, while session hosts and some supporting services stay customer-managed or partner-managed. These control families are where VDI changes enforcement.

Identity, access, and authentication

Azure Virtual Desktop uses Azure role-based access control to separate management roles across host pools, application groups, and workspaces. Teams can grant user access through the Desktop Virtualization User built-in role assigned to security groups, segregate session host VMs into separate organizational units per host pool, and use Local Administrator Password Solution to rotate local admin passwords.

For multifactor authentication, teams typically establish Microsoft Entra Conditional Access policies requiring MFA. Per-user MFA does not work here; Conditional Access is the mechanism, and users need Microsoft Entra ID P1 or P2 licenses. NIST SP 800-171 R2 control 3.1.5 (least privilege) maps directly to the Azure Policy "Audit usage of custom RBAC roles" control.

Audit logging and continuous monitoring

Audit log collection lets teams view user and admin activity across the environment. DFARS 252.204-7021 (cited previously) requires an annual affirmation of continuous compliance posted in the Supplier Performance Risk System (SPRS), so teams need a monitoring process and evidence trail that can support that affirmation.

For audit evidence, NIST assessment methods include examining configuration settings, audit records, lists of audited events, and the System Security Plan. The Content Hub includes a Microsoft Sentinel CMMC 2.0 solution. Depending on the initiative version, Azure Policy CMMC and NIST 800-171 built-in initiatives include 202 to 435 policies and enable automated policy drift detection.

Configuration baselines and session host hardening

Every session host inside the enclave has to be hardened, and starting from a known-good baseline is the path of least resistance. A golden image is the master virtual machine image from which sessions deploy, so the hardening work happens once at the image and propagates to every host built from it.

Start with CIS Hardened Images:
CIS Hardened Images are virtual machine images configured to CIS Benchmark recommendations, available through Microsoft Marketplace (including Azure Government). Two details matter for teams running Azure Virtual Desktop:

Then layer on three controls:

  • Application control - WDAC or AppLocker block unsigned scripts and MSIs, and restrict PowerShell to Constrained Language Mode.
  • RemoteApps - Limit users to specific applications rather than a full desktop, which shrinks the attack surface further.
  • Threat detection - Microsoft Defender for Cloud, Microsoft Sentinel, and Microsoft Intune feed events from the session hosts into a single response workflow.

Standing up these layers is one job. Keeping them consistent across every session host, version after version, is the harder one. Nerdio Manager for Enterprise deploys into your Azure environment and manages Windows 365, Microsoft Intune, and Azure Virtual Desktop from one console, with granular RBAC, audit logging, policy automation, and CIS Hardened Image workflows.

It gives teams a repeatable way to configure and maintain RBAC, hardened images, and golden image consistency across session hosts without hand-built PowerShell, while certification, audit, and compliance responsibility remain with your organization.

Owning these controls is hard enough when the environment is correct from day one. The bigger exposure is choosing the wrong cloud foundation underneath them, because that is a one-time architectural decision with expensive consequences.

Choosing your cloud foundation: GCC High, Azure Government, and the CUI line

The cloud environment you select is the most consequential decision in the entire project, and reversing it later is slow and costly. Azure Virtual Desktop is generally available across Azure Government. Azure Virtual Desktop session hosts run in Azure Government, while Microsoft 365 GCC High serves as the companion productivity layer for organizations that require that government cloud pairing.

Your data type drives the tier.

If you handle

Use

Why

Non-sensitive, public data

GCC or Commercial

Lower data sensitivity

CUI (standard), DFARS-regulated data

GCC High

DFARS 7012, ITAR/EAR, DoD IL4

DoD mission-critical CUI (NSS)

GCC High + DoD regions

DoD SRG IL5

Microsoft's GCC High guidance draws the distinction that contractors most often miscalculate: "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." For multi-business-unit organizations, Microsoft advises putting everything in GCC High to apply the high security bar uniformly rather than mapping each unit separately.

Platform owners should keep the Azure Virtual Desktop estate in one cloud. Azure Virtual Desktop VMs in Azure Government with host pools in Azure Commercial is not a supported configuration. Microsoft recommends a one-cloud approach. Whichever environment you choose, the whole estate lives there.

Getting the foundation right protects the controls you build on top of it. Getting the budget and timeline right is what determines whether you are ready when third-party certification becomes a condition of award again.

What the real costs and timelines look like

CMMC Level 2 can become a six-figure, year-plus effort, and the numbers that matter most are the ones tied to your own scope. The University of Pittsburgh's documented Azure GCC High enclave reported in COGR meeting materials in October 2025 is a useful real-world anchor:

Cost category

Amount

CMMC Level 2 certification costs

$320,185

Creating/maintaining the 800-171 environment

$478,000

Total estimated first-year cost

$798,185

Estimated five-year cost

$3,287,000

GCC High licensing, add-ons, and operating model choices should be budgeted before the architecture is locked. Your scope model determines the license line item and the number of users, devices, applications, and session hosts inside the CUI boundary.

Three cost traps show up early.

  • License overspend
    License confusion and overly broad scope can cause contractors to pay more than necessary. Right-sizing your CUI exposure (the enclave model) is the lever here.
  • GCC High operational planning
    Application readiness, data-sharing boundaries, and licensing channels belong in design work, not afterthoughts.
  • Internal staffing
    Implementation, documentation, monitoring, and evidence gathering require dedicated ownership, not spare-cycle administration.

On timeline, CMMC works better as a phased program than as a procurement task. The University of Pittsburgh example reported roughly 12 months from the decision to launch a CUI-compliant environment to the start of certification activity. A 12-month build is long enough that the review window becomes useful preparation time. Teams that keep building during the pause will be ready to certify quickly once the queue reopens.

Right-sizing and automation directly affect the budget. A smaller in-scope footprint means fewer session hosts to harden, document, and monitor, which compresses both the implementation and the evidence-gathering work. Nerdio Manager surfaces right-sizing recommendations so you are not overprovisioning compute inside an expensive GCC High environment, and its patented auto-scaling deallocates session host VMs when they are not in use so you stop paying for idle compute.

Nerdio enterprise customers have reported up to 55% savings on Azure compute through auto-scaling. Inside a GCC High enclave where every in-scope workload adds cost and evidence work, that control matters more, not less.

Where Azure Virtual Desktop sits against Citrix and Omnissa Horizon for CMMC

Azure Virtual Desktop, Citrix, and Omnissa Horizon (formerly VMware Horizon) all remain viable VDI options for CMMC, per the ND-ISAC white paper cited earlier. The three-way comparison comes down to the cloud foundation, the control model, and how much customer-owned evidence your team has to create and maintain.

For a defense contractor optimizing for CMMC scope reduction and a Microsoft-native operating model, the Azure Government foundation gives teams one centralized platform for the in-scope virtual desktop estate. Many teams evaluating Citrix alternatives for regulated workloads are already running this comparison.

Migration is the other half of the decision. Microsoft's GCC High guidance advises allocating at least three months for the migration phase when moving from commercial cloud to government cloud, and there is no one-click tool from Citrix to Azure Virtual Desktop. That three-month figure assumes an unassisted move without migration tooling.

With Nerdio's guided migration workflows, the picture can compress. Felleskjøpet Agri SA left legacy VDI behind and saves nearly 4 million NOK annually, and Carvana completed a 14-day migration and cut IT costs in half. Migration timelines need not be the blocker pessimistic baselines suggest.

How Nerdio Manager supports a CMMC-ready desktop estate

Once the architecture and cloud foundation are set, the day-to-day work shifts to keeping the in-scope environment configured correctly and producing the evidence an assessor will ask for. That work is operational and repetitive, and it breaks down when it depends on manual PowerShell and console-hopping across the Azure Portal, Entra ID, and Intune. Nerdio Manager handles that work across both Windows 365 and Azure Virtual Desktop from a single console.

Evidence and policy artifacts for assessors

Granular RBAC, audit logging, policy automation, and feature rollback produce the evidence trail assessors look for. Nerdio Manager can also create, back up, and restore Intune policies, a capability native Intune doesn't offer, which matters when your SSP claims a configuration policy is enforced and an assessor asks how changes are tracked and recoverable.

Session host operations at scale

Centralized golden image creation, versioning, and distribution with CIS Hardened Images gives teams one controlled baseline for session hosts instead of one-off host builds. An independent benchmark test by Dr. Benny Tritsch found updating a custom image dropped from 146 clicks to 13 with Nerdio Manager. Fewer clicks means fewer manual steps, which means fewer configuration errors in an environment where a misconfigured host is an audit finding.

Unified application management deploys applications in roughly 30 seconds versus native Intune delivery that can take up to three hours. For teams managing Cloud PCs through Microsoft Intune and session hosts through Azure Virtual Desktop, that keeps application changes from turning into another evidence and operations bottleneck.

Auto-Heal detects and repairs broken session hosts automatically. Agentless monitoring gives near real-time visibility into performance and logon health with a polling interval configurable down to one minute, default every five minutes, and no proprietary agent expanding the attack surface on hardened hosts.

Cost control inside a GCC High tenant

Nerdio Manager combines Azure Virtual Desktop right-sizing and auto-scaling with Windows 365 license optimization. Nerdio Advisor flags underutilized Cloud PC licenses for reclamation and recommends Flex (formerly Frontline) conversion where users never overlap, which keeps spend honest inside a premium GCC High tenant.

A virtual desktop enclave shrinks what an assessor has to look at. Keeping the controls inside it right is the work that determines whether the scope reduction holds. 

Get a demo to see how Nerdio Manager works across your Windows 365 and Azure Virtual Desktop environment, or try it free in your Azure tenant.

Frequently asked questions about CMMC for virtual desktop environments

Ready to get started?