How it works
Secureframe Virtual Desktops lets your organization provision CMMC-compliant virtual desktops so your team can securely view and process Controlled Unclassified Information (CUI). It is part of Secureframe's Defense product line. Instead of bringing every employee laptop into CMMC scope, your team does CUI work inside the virtual desktops, keeping your compliance boundary small and manageable.
Connect an Azure Government account to Secureframe.
Provision secure virtual desktops from the Secureframe platform.
Users access those desktops through standard remote desktop apps.
Start with Prerequisites to setting up your Virtual Desktops, then Provisioning Virtual Desktops, then Accessing Your Virtual Desktop.
Deployment model
Virtual desktops are always deployed into an Azure Government environment that your organization owns. Secureframe handles the provisioning and configuration; the underlying infrastructure lives in your tenant.
Defense enclave upgrades and deploys preserve customer resources by default, including customer subnets (for example site-to-site VPN network groups).
Control: Your CUI stays inside your own Azure Government environment. Secureframe never hosts your data in a Secureframe-owned tenant.
Cost: Because the resources run in your tenant, you are responsible for the Azure infrastructure costs of the resources you provision. Those charges appear on your Azure invoice, not your Secureframe invoice. When you provision a desktop, Secureframe shows estimated Azure costs in the product before you deploy.
Access: Secureframe manages Virtual Desktops through a customer-tenant App Registration. Standing design avoids read access to CUI and profile shares. See Secureframe access to your Virtual Desktops below for the full privilege model.
Secureframe access to your Virtual Desktops
Secureframe connects to your Azure Government tenant with an App Registration and service principal that you authorize during setup. That connection is how Secureframe creates, configures, updates, and monitors Virtual Desktops in a subscription you own.
What Secureframe can do by design
Subscription management: The connection has Owner on the dedicated Virtual Desktops subscription so Secureframe can deploy and maintain the enclave infrastructure.
Deploy-time host management: Owner includes Azure capabilities Secureframe uses on every deploy, including running commands on session hosts as the local SYSTEM account. Secureframe uses that path for provisioning and maintenance, not for browsing customer CUI.
Microsoft Entra permissions: The connection also holds privileged Entra directory permissions needed to operate the environment, including application management and directory role-management permissions. Those Entra permissions do not currently use the same anti-delegation condition applied on the subscription.
How Secureframe avoids standing access to CUI on shares
The standing service principal does not have permission to read your CUI file shares or user profile shares.
Storage account shared keys are turned off.
The only elevated share role used during deploy is assigned to a short-lived bootstrap virtual machine. Secureframe deletes that VM when the deploy finishes.
Important: Because the connection has subscription Owner, it could technically assign itself broader data-plane access. The standing design does not grant read access to CUI or profile shares. Prefer storing CUI on the shared Z: drive or other approved locations, not only on a local desktop disk.
CMMC documentation
For assessors, ask your CSM for Secureframe's external service provider (ESP) package for Virtual Desktops. It describes Secureframe's access, responsibilities, and justification. Contractual liability and shared responsibility are covered in your agreement with Secureframe and in that package, not by this Help Center article alone.
Supported operating system
Windows 11 is the operating system for Secureframe Virtual Desktops.
Prerequisites
Before you can provision desktops, you need:
An active Azure Government subscription that is visible to Secureframe
The required GCC High licensing (Microsoft 365 G5, G3, or Business Premium; Business Premium is limited to 300 users)
Verified custom domains in Microsoft Entra
See Prerequisites to setting up your Virtual Desktops for the full checklist.
Key features
Golden image
Every virtual desktop in your environment is built from a golden image: a Windows template that Secureframe builds, secures, and keeps up to date. It includes Windows 11 and Microsoft 365, with the security settings CMMC requires already in place.
This matters for CMMC in two ways:
Every desktop is secure from the start. The security settings are part of the image, so a new desktop is locked down the moment it's created. No desktop gets skipped.
Every desktop is the same. Your desktops are copies of one image, so what your assessor sees on one desktop is true for all of them.
Secureframe releases new versions of the golden image with Windows updates and security changes. Before a version is released, Secureframe starts a test desktop from it and checks that it starts up, has the right software, and has its security settings in place. New desktops are built from the newest version. A desktop you already have stays on its version until it's rebuilt.
See Golden Image for Virtual Desktops for what the image includes and how updates work.
Pooled multi-session desktops
When a user signs in, they get a ready-to-use desktop right away. Instead of paying for a dedicated virtual machine for every user (machines that sit idle whenever those users aren't working), your organization runs a smaller set of desktops that the whole team shares. Your team gets the same experience at a lower Azure cost.
Autoscaling
Autoscaling starts and stops your desktops around your team's working hours, so you pay for Azure compute when it's needed instead of around the clock. You choose those hours, called core hours, for each day when you create a pool, and you can update them anytime.
Desktops start about 30 minutes before core hours so they're ready when your team signs in, and they shut down after core hours once everyone has left. If someone is still working when core hours end, their desktop stays on until they're done. If someone needs to work outside core hours, signing in starts a desktop automatically.
Roaming profiles
Because desktops are shared and start and stop on a schedule, a user's settings and preferences belong to their profile, not to any one machine. Whichever desktop they sign in to, those follow them, so every desktop feels like their own.
The machines themselves are disposable. A desktop can be rebuilt, replaced, or upgraded without wiping profile settings. Files stored only on that desktop do not follow the profile. That includes items on the Desktop, in Downloads, and on local disks.
Shared drive
Every virtual desktop includes a shared drive (Z:) for files your team works on together. Save a file once and everyone with access to your Virtual Desktops can open it, with no copying or emailing files between people.
On V7+ enclaves with a CUI folder, Secureframe shows the Entra security group that controls CUI access in enclave settings next to the data share (name pattern Secureframe Enclave CUI - …). Manage members in Entra.
Shared with your whole team: Everyone with access to your Virtual Desktops can open, edit and delete files on the shared drive. Keep personal files in your own profile folders instead.
Separate from profiles: Files on the shared drive don't count against your profile storage, which keeps sign-ins fast.
Kept through rebuilds and upgrades: Files on the shared drive aren't affected when a desktop is rebuilt.
The shared drive uses its own storage account in your Azure Government environment, which appears as a separate line on your Azure bill.
Monitoring and audit records
Secureframe keeps track of two things in your Virtual Desktops: what people do in your environment, and any changes made to the setup Secureframe manages for you. Both are set up automatically, so there is nothing to turn on.
Activity logging
Secureframe keeps a record of what happens in your Virtual Desktops, such as who signed in, who connected to a desktop, which files on the shared drive were opened or changed, and what changed in your setup. Records are stored in a log workspace in your own Azure Government environment. Secureframe keeps them for a year, protects them from deletion, and emails you if logging stops. Ready-made searches answer the questions assessors ask most often. The log workspace appears as a separate line on your Azure bill.
See Activity Logging for Virtual Desktops for what is recorded and how to find your records.
Drift detection
Secureframe watches the infrastructure it manages for your Virtual Desktops and flags any change made directly in Azure, like a setting that was changed, a resource that was added, or one that was deleted. For each change, you see what changed, who made it and how much it matters, then choose to keep it or have Secureframe revert it. Every decision is recorded in the Drift log, giving you a reviewed record of changes to your CUI environment.
See Drift Detection for Virtual Desktops for how to review and manage changes.
CMMC compliance coverage
The Secureframe platform includes automated tests that make sure your virtual desktops stay CMMC compliant. As you deploy and use virtual desktops, the platform automatically checks the relevant controls and surfaces the results in your compliance dashboard.
Frequently Asked Questions (FAQ)
What access does Secureframe have to our Virtual Desktops?
Secureframe connects with a customer-tenant App Registration and service principal used to create and manage Virtual Desktop infrastructure.
The connection has Owner on the dedicated subscription, plus privileged Microsoft Entra directory permissions needed to operate the environment.
Owner includes deploy-time capabilities such as running commands on session hosts as SYSTEM. Secureframe uses that for provisioning and maintenance, not for browsing CUI.
See Secureframe access to your Virtual Desktops above for the full model.
Can Secureframe staff see CUI saved on a Virtual Desktop?
There is no standing permission for the Secureframe service principal to read CUI file shares or user profile shares. Storage shared keys are off, and elevated share access used at deploy time is limited to a bootstrap VM that is deleted afterward.
Privileged Azure roles that enable infrastructure management could, in theory, be used more broadly. Prefer storing CUI on the shared Z: drive or other approved locations rather than only on a local desktop disk.
What is the security liability, and how do we document this for CMMC?
Treat Secureframe as an external service provider for the managed Virtual Desktops / enclave scope.
Ask your CSM for Secureframe's ESP package. It describes Secureframe's access, responsibilities, and justification for assessors.
Contractual liability and shared responsibility are covered in your agreement with Secureframe and in that package. This article is not the compliance artifact.
Does deploying a virtual desktop make me CMMC compliant?
Not by itself. Virtual Desktops gives your team a secure, controlled environment for CUI, which is one piece of CMMC compliance. Full compliance also requires policies, controls, and processes across your organization. Secureframe Defense includes all of these components, so you can build and track your entire CMMC program in one place.
Who pays for the Azure infrastructure?
You do. The resources run in your Azure Government tenant, so infrastructure charges appear on your Azure invoice. Cost estimates shown in Secureframe are not an official Azure quote or invoice.
Why do we need to verify an adsf subdomain during license setup?
This only applies to Virtual Desktops on enclave version 5 or lower. On those enclaves, Microsoft Entra Domain Services limits the managed domain name to 15 characters, so a tenant name longer than that needs an adsf subdomain. Version 6 and later have no 15 character limit. If you’re on version 5 or lower and your tenant name is over 15 characters, see What to Do If Your Azure Government Tenant Name Is Over 15 Characters.
If I remove a user from a Virtual Desktop in Secureframe, do they lose access right away?
Yes. Removing an assigned user also revokes their Azure role assignments for that desktop. See Provisioning Virtual Desktops and Accessing Your Virtual Desktop for details.
Does Virtual Desktop / VDI Enclave setup include a CUI-compliant SharePoint?
No. Secureframe Virtual Desktops provision the Azure VDI environment used to view and process CUI. They do not create or configure a CUI-compliant SharePoint site. CUI-compliant SharePoint is part of automated Microsoft GCC High setup. See What Secureframe configures in your Microsoft GCC High tenant.
Will I lose data if my virtual desktop is rebuilt or migrated?
Yes, for files stored only on that desktop (Desktop, Downloads, local disks).
Before a rebuild or platform upgrade, move important files to OneDrive or the shared data drive (Z:).
Software installs and machine-specific configs usually cannot move to OneDrive. Plan to reinstall those after a rebuild.
Large datasets should live on the shared Z: drive, not on one desktop. See Provisioning Virtual Desktops for what the shared drive is for.
Can I install my own software on a Virtual Desktop?
Yes, but only a pool admin can run installers. Standard users cannot. Grant Pool admin under Virtual desktops → open the pool → Access list. See Provisioning Virtual Desktops.
Install to
C:\Program Files(orC:\Program Files (x86)for 32-bit apps). Do not install to the user profile (AppData, Downloads, Desktop) or to a custom folder likeC:\Apps. Details: Golden Image for Virtual Desktops.Virtual Desktops are full Windows 11 machines. You can install the line-of-business apps your team needs to work with CUI (for example estimating or project tools that do not have a CMMC-ready cloud version).
Secureframe does not maintain an allowlist of approved desktop applications. You choose what your organization needs. You are responsible for configuring and securing anything you install, and for keeping that software in line with your CMMC program. Secureframe hardens and monitors the desktop platform. It does not certify or manage third-party apps for you.
Software installs and machine-specific configs usually do not survive a desktop rebuild. Plan to reinstall those apps on each desktop in the pool after a rebuild, or place shared data on OneDrive or the shared drive (Z:).
If you need a shared backend that multiple desktops can reach (for example a file, terminal, licensing, or database server for an app like HeavyBid or SolidWorks), use a service machine in the enclave. See Virtual Desktop: Engineering Workloads & Infrastructure.
Do Defense enclave upgrades or deploys delete customer-created resources?
No. Upgrades and deploys preserve customer resources by default, including customer subnets (for example site-to-site VPN network groups).
Questions? Contact [email protected] or reach out to your CSM.
What is the difference between Restart and Force restart on a Virtual Desktop?
From the desktop menu: Restart drains the host and waits for users to sign out; Force restart reboots immediately and ends sessions.
See the how-to under Managing your desktops in Provisioning Virtual Desktops.
Can admins turn off Intune enrollment for Virtual Desktops?
Yes. Use Enroll desktops in Intune in Virtual Desktop / enclave settings, confirm the dialog, and wait for each desktop’s maintenance window to finish.
Where do I find the Entra group for CUI folder access?
In enclave settings, next to the data share details. Add users to that group in the Microsoft Entra admin center.


