Blog
Zero trust endpoint security: the frameworks, controls, and deployment sequence
Apply zero trust endpoint security across laptops, Cloud PCs, and session hosts with continuous posture checks using Intune, Conditional Access, and Defender.
Nerdio is Microsoft’s 2026 Americas ISV Partner of the Year Get the story
Blog
Apply zero trust endpoint security across laptops, Cloud PCs, and session hosts with continuous posture checks using Intune, Conditional Access, and Defender.
Table of Contents
A laptop that passed its Intune compliance check in March can be three cumulative updates behind by September and still hold a valid finance-app token. Perimeter models can confer implicit trust after posture goes stale. Zero trust endpoint security makes current device posture an access condition for every request.
This guide is for governance, risk, and compliance (GRC) leads and platform owners responsible for endpoint management across Windows 365, Microsoft Intune, and Azure Virtual Desktop. It walks through continuous posture checks across laptops, Cloud PCs, and session hosts without policy drift or lockouts.
Zero trust endpoint security ties every access decision to current device identity and posture rather than network location. Breach data supports the shift, and Microsoft's guidance translates the principles into controls that teams can enforce.
Under this model, a device whose posture has gone stale loses resource access even when it connects from a corporate network. Zero trust endpoint security grants a device access to a resource only after the policy enforcement point verifies its identity and posture for that session, whatever network it connects from.
NIST SP 800-207 requires enterprises to evaluate trust continually instead of granting it implicitly, and to authenticate and authorize "both subject and device" before establishing a session.
The perimeter model is failing in the data. Verizon's 2025 Data Breach Investigations Report found that 22% of breaches targeted edge devices and VPNs, up from 3% the prior year, and recorded full remediation for only 54% of those exposures, at a median of 32 days.
The same exposure pattern appears at endpoints. In TechTarget's 2025 endpoint security survey, 54% of respondents reported attacks traced to unknown, unmanaged, or poorly managed endpoints.
Microsoft's guidance for Azure Virtual Desktop maps "verify explicitly" to verifying identities and endpoints, and "use least privileged access" to confining access to session hosts with role-based access control (RBAC) and just-in-time administration.
Operationally, this mapping turns broad principles into checks and restrictions that teams can enforce. NIST and CISA set the bar for which signals count as posture and how often they get re-evaluated.
NIST SP 800-207 and CISA's Zero Trust Maturity Model treat device posture as a signal that must be evaluated continuously and paired with identity in every authorization decision. Federal guidance from OMB and NSA extends the requirement into specific device signals that a Microsoft estate can supply through Intune and Defender for Endpoint.
NIST SP 800-207 (previously cited) requires that "every asset must have its security posture evaluated via a policy enforcement point (PEP) before a request is granted to an enterprise-owned resource." The same tenet adds that this evaluation "should be continual for as long as the session" continues. Tenet 3 grants access per session, and Tenet 6 expects multifactor authentication (MFA) plus continual monitoring with reauthentication where needed.
The scope includes devices the enterprise neither owns nor configures. Together, these tenets link device assessment with authentication and subsequent reauthentication in one enforcement cycle.
CISA's Zero Trust Maturity Model version 2.0 makes Devices one of five pillars and defines a device as any asset "that can connect to a network." The definition covers hardware, software, and firmware.
Its four maturity stages run from Traditional, where organizations set least privilege once at provisioning and respond manually, to Optimal. At the Optimal stage, assets self-report and least privilege becomes dynamic enterprise-wide.
Continuous monitoring also feeds centralized visibility. The maturity path therefore shifts operations from manual response toward centralized, telemetry-driven enforcement.
Version 2.0 of the ZTMM added deprovisioning, offboarding, and remediation for devices that fail posture requirements. For federal agencies, OMB M-22-09 requires at least one device-level signal alongside identity in authorization decisions. The NSA's January 2026 zero trust guideline counts operating-system and patch status together with antivirus signals. It also counts application-inventory signals.
In a Microsoft estate, Conditional Access can serve as a policy enforcement point for covered Microsoft cloud access decisions using posture data supplied through Intune and Defender for Endpoint.
Intune measures device state, and Conditional Access enforces it. Together they cover physical laptops, Cloud PCs, and Azure Virtual Desktop session hosts, with hardware-backed attestation and Defender risk scores feeding the same compliance signal.
Microsoft's seven-layer Intune framework covers app protection policies, device enrollment, compliance policies, Conditional Access requiring healthy and compliant devices, configuration profiles, Defender for Endpoint integration, and Endpoint Data Loss Prevention (DLP).
Compliance policies assess device state, while Conditional Access enforces blocking through a policy you build in Entra ID. A policy can therefore report device state correctly in Intune without protecting a resource until the corresponding grant control applies in Entra ID.
The "Require device to be marked as compliant" grant control denies access if the isCompliant attribute is null or missing. Two Microsoft settings reinforce that default:
Nerdio Manager for Enterprise extends Microsoft's device-management tooling with cross-endpoint tracking of which policies apply to physical laptops and the Windows Cloud estate (Windows 365 and Azure Virtual Desktop together), including Cloud PCs and session hosts.
Two independent signals populate the compliance state Conditional Access reads:
Cloud PCs enroll in Intune and take compliance policies. Provisioning onboards them to Defender, and they have a dedicated Windows 365 Cloud PC security baseline (version 24H1).
For Azure Virtual Desktop, Microsoft's zero trust article puts endpoints at step 2. The Cloud Adoption Framework recommends Intune with compliance policy and Conditional Access for personal session hosts. It also recommends Trusted launch (Secure Boot plus vTPM) for the VMs themselves and the security baselines Microsoft publishes for Windows Enterprise multi-session.
This division separates controls on the connecting endpoint from controls on the virtual infrastructure hosting the session. Initial access enforcement verifies the device before granting access, and assume-breach controls contain a device that becomes hostile mid-session.
Assume-breach controls limit what a hostile device can reach once posture verification has already granted access. Managed endpoints rely on the Defender-to-Intune-to-Conditional-Access chain, while session hosts need a separate infrastructure layer because they're shared.
Unmanaged devices are a prominent factor in ransomware risk. Microsoft's Digital Defense Report found that over 90% of ransomware attacks that progressed to the ransom stage used unmanaged devices as the initial access point or for remote encryption.
For managed devices, when teams configure the Defender-to-Intune integration, a machine-risk compliance threshold, and Conditional Access grant controls, Defender can flag high risk, Intune can mark the device noncompliant, and Conditional Access can cut off covered access, subject to applicable session behavior.
Your session hosts need a containment layer because they're shared infrastructure. Apply Microsoft's Cloud Adoption Framework guidance for Azure Virtual Desktop to session hosts through the following controls:
Administrators should grant access to Entra groups rather than individual users through the Desktop Virtualization User built-in role.
Since July 2025, Microsoft disables clipboard, drive, opaque low-level USB, and printer redirections by default for new Azure Virtual Desktop host pools. Windows 365 applies the same defaults to newly provisioned and reprovisioned Cloud PCs.
Teams manage Azure Virtual Desktop through the Azure Portal, PowerShell, and Microsoft Intune. You configure these controls in several consoles, so their deployment order matters as much as the settings.
Microsoft's Rapid Modernization Plan (RaMP) sequences the work of validating trust on every access request into five steps:
Teams should apply Conditional Access enforcement only after they establish reliable inventory and compliance data. Turning on the grant control before devices are enrolled and reporting produces the lockouts covered in the next section.
Licensing shapes what's available at each step. As of July 1, 2026, Intune Suite capabilities are included in Microsoft 365 E5, while Endpoint Privilege Management, Microsoft Cloud PKI, and Enterprise Application Management remain E5-only. Microsoft names Endpoint Security Manager as the least-privileged built-in Intune role that holds every permission the Defender integration requires, which keeps step 3 within a bounded delegation model.
This sequence holds for physical laptops and the Windows Cloud estate. Cloud PCs and session hosts add platform-specific failure modes that broad roadmaps rarely cover.
The RaMP sequence assumes a physical laptop estate. Cloud PCs and multi-session hosts introduce platform-specific failure modes that turn correct-looking compliance policies into production lockouts.
The most common example involves BitLocker. Cloud PCs don't support BitLocker, which means a Windows compliance policy carrying "Require BitLocker" marks every Cloud PC noncompliant and locks users out under the failure-closed model. The fix is to exclude that setting from your Cloud PC compliance policies while your physical Windows 11 policies keep it.
That mis-scoping pattern repeats across other controls, and the table below covers the failure modes teams hit most often when they extend a single policy set across mixed device types.
| Failure mode | What breaks | Documentation |
| Enabling "Require compliant device" before break-glass accounts exist | Administrators lock themselves out of the tenant | Nerdio's Conditional Access guide for Windows 365 and Azure Virtual Desktop |
| Device-compliance Conditional Access policy scoped to all cloud apps with bring-your-own-device (BYOD) users | BYOD devices cannot launch Cloud PCs because Conditional Access does not let administrators exclude the Windows 365 Client app ID (4fb5cc57-dbbc-4cdc-9595-748adff5f414) in the standard way | |
| Conditional Access policy blocking the Windows 365 app (0af06dc6-e4b5-4f28-818e-e78e62d137a5) | Azure Virtual Desktop sign-in fails because Windows App authenticates to both apps | Microsoft Learn, set up MFA for Azure Virtual Desktop |
| Autopilot-based enrollment for pooled multi-session hosts | Windows Enterprise multi-session does not support Autopilot-based enrollment, out-of-box experience (OOBE) enrollment, or the enrollment status page | Microsoft Learn, Azure Virtual Desktop multi-session |
| Surface Hub accounts in scope of compliant-device or hybrid-join controls | These controls do not support device accounts, and administrators must exclude them | Microsoft Learn, Surface Hub Conditional Access |
Microsoft describes two compliance layers for Cloud PCs, a tenant-wide default every device receives and platform-specific rules deployed to groups. A Tech Community thread on Windows 365 warns that performance-heavy settings such as Defender scan schedules need Cloud PC-specific values because the VMs share infrastructure.
Once baselines differ by platform, proving they still match the approved standard means correlating Entra ID evidence with records from Intune and Defender. For a GRC lead, that correlation is what satisfies NIST CSF 2.0 PR.PS-01 on hardened baselines and CIS Control 4.
An orchestration layer over Intune can correlate records across those three systems and compare differentiated baselines with approved standards. Microsoft's stack supplies the underlying controls.
The previous section ended on a correlation problem. Compliance evidence for a mixed estate lives across Intune, Entra ID, and Defender, and proving that differentiated baselines still match the approved standard means pulling records from all three. That correlation problem is what Nerdio Manager addresses.
Nerdio Manager is an orchestration layer across Windows Cloud and Microsoft Intune. It centralizes Intune data for Windows 365 and Azure Virtual Desktop in one console, and it extends Microsoft's device management tooling as a management platform. Intune and Entra ID continue to enforce the controls, and Defender continues to enforce its own controls. Nerdio Manager sits above them and makes the evidence traceable across the endpoint estate.
For Windows 365 specifically, the strongest value is Intune management because the operational surface for a Cloud PC is Intune. Policy backup and restore, Unified Application Management, and Advisor recommendations for Cloud PCs all sit on that same Intune foundation.
The Nerdio workflows below map to the failure modes and drift patterns covered earlier:
These workflows align with the CIS Controls and NIST expectations we referenced in this guide, but they do not certify or guarantee compliance with any framework.
TechTarget's Enterprise Strategy Group found a 50% reduction in IT admin hours needed to manage Azure Virtual Desktop with Nerdio Manager. Syneos Health, a clinical research organization, reported 70% faster configuration changes.
The City of Corona shows what the consolidated model looks like in practice. The team brought Windows 365 and Azure Virtual Desktop under Nerdio Manager and moved Intune into the same operating model after legacy RMM tooling left security enforcement inconsistent across its estate.
Get a demo to see how Nerdio Manager surfaces policy drift and compliance history across your endpoint estate, or try it free in your Azure tenant.
Zero trust endpoint security uses current device identity, compliance, and risk signals to decide whether a device can access each resource. Enrollment and location provide context for a continuing evaluation of compliance and risk. In Microsoft environments, Intune compliance policies feed Entra ID Conditional Access, and Defender for Endpoint supplies risk signals.
Traditional endpoint security establishes trust at provisioning and assumes the device stays trustworthy, which CISA's maturity model calls the Traditional stage. Zero trust treats provisioning as the start of an ongoing evaluation process and automatically revokes access when device risk changes.
Deployment timelines vary. The Cloud Security Alliance's program management guidance describes a phased approach spanning 20 months, and Forrester treats zero trust as a continuing operating practice. A September 2026 public sector survey found lack of skilled staff and deployment complexity each accounting for 40% of the biggest barriers.
Zero trust is an architecture and a set of design principles. Microsoft supplies the enforcement components: Intune, Entra ID Conditional Access, and Defender for Endpoint. Management platforms such as Nerdio Manager centralize policy assignments and compliance records across physical laptops, Cloud PCs, and session hosts.
Learn more about Nerdio Manager