Skip to main content

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

Blog

Unified endpoint management in a Microsoft-first estate: control depth by endpoint type

See how unified endpoint management control depth varies across physical Windows, Windows 365, and Azure Virtual Desktop endpoint types.

A Microsoft Intune compliance dashboard can read 98% compliant while the update ring assigned to 300 Azure Virtual Desktop multi-session hosts shows "Not applicable" on every one of them. That difference between what the portal reports and what the endpoints enforce is the operational reality of unified endpoint management in a Microsoft estate.

This guide is for enterprise endpoint and cloud desktop leaders evaluating Microsoft Intune controls across a Microsoft-first estate.

Intune reaches broadly across the estate. It enrolls Android, iOS/iPadOS, Linux, macOS, and Windows devices from one admin center. What Intune actually enforces once a device is enrolled changes by endpoint type. Physical Windows devices, Windows 365 Cloud PCs, and Azure Virtual Desktop session hosts each get a different subset of policies, remote actions, and update mechanisms, and the endpoints Intune cannot manage often show up in reports as "Not applicable" rather than as a visible gap.

What unified endpoint management means, and where Microsoft Intune fits

Intune is Microsoft's unified endpoint management platform for a Microsoft-first estate, and it manages physical devices, Cloud PCs, and Azure Virtual Desktop session hosts from one admin center.

Unified endpoint management (UEM) centralizes the management and security of endpoint devices across operating systems. It grew out of mobile device management and now covers employee laptops, mobile devices, and virtual endpoints under one policy set.

How the major analysts frame the UEM market

The major analysts track the same market under slightly different labels. Gartner published its 2026 Magic Quadrant under the title "Endpoint Management Tools," a rename from "Unified Endpoint Management Tools." IDC's 2025-2026 MarketScape called it Worldwide Unified Endpoint Management Software. Microsoft's Forrester announcement of The Forrester Wave: Endpoint Management Platforms of Q2 2026 named Intune a Leader and quoted Forrester describing it as "built on Microsoft Entra, Microsoft Defender, Windows, and Windows 365 as a connected system, not a collection of adjacent tools."

Together, those labels emphasize connected endpoint operations across physical and virtual devices.

Where Intune fits across physical devices and Windows Cloud

Microsoft describes Intune as "a cloud-based endpoint management solution" that "manages user access to organizational resources and simplifies app and device management across your devices, including mobile devices, desktop computers, and virtual endpoints." Supported platforms include Android, iOS/iPadOS, Linux, macOS, and Windows.

Windows Cloud, the umbrella term for Windows 365 and Azure Virtual Desktop, sits inside that same estate. Organizations can use side-by-side management for Cloud PCs and physical devices, and many enterprises run both Windows 365 and Azure Virtual Desktop. Microsoft reinforced that positioning in April 2026 by adding a dedicated "Cloud PC management" navigation area to the Intune admin center.

Enrollment reach is the easier half of the story. Depth is where the estate gets uneven, and what Intune enforces once a device is enrolled varies by endpoint type.

How Intune control depth varies by endpoint type

Intune enforces a different subset of policies, remote actions, and update mechanisms on each endpoint type in the estate, and the endpoints it cannot manage show up in reports as "Not applicable" instead of as a visible gap.

The sections below walk through Azure Virtual Desktop, Windows 365 Cloud PCs, physical Windows devices, and the platform-specific limits that apply across all of them.

Azure Virtual Desktop session hosts

Intune's control depth on Azure Virtual Desktop depends on the host type. Microsoft states that Intune treats Azure Virtual Desktop personal VMs the same as Windows Enterprise physical desktops, so single-session personal hosts get the standard Windows control set. Multi-session hosts are far more limited. Only certificate and VPN device tunnel configuration templates reach Windows Enterprise multi-session, Microsoft Intune won't deliver unsupported templates to those devices, and update rings for Windows aren't currently supported there either.

Those unsupported policies appear as Not applicable in reports. To patch multi-session hosts through Intune, admins have to rebuild quality updates as Settings Catalog settings filtered for Enterprise multi-session. Assignment success also has to be evaluated against both the host type and the policy state shown in the portal, since rerunning a sync cannot make an unsupported template apply.

Remote actions and app delivery narrow further on Azure Virtual Desktop. Intune grays out six remote actions for multi-session and does not support or recommend them for single-session Azure Virtual Desktop VMs. The blocked actions are:

  • Autopilot reset
  • BitLocker key rotation
  • Fresh Start
  • Remote lock
  • Reset password
  • Wipe

Session hosts joined to Microsoft Entra Domain Services fall entirely outside Intune management, and Microsoft Intune documentation states that "Azure Virtual Desktop RemoteApp and MSIX app attach" aren't currently supported in Microsoft Intune.

Nerdio Manager for Enterprise works across these host types to report on session-host state, manage Intune policies, and automate Azure Virtual Desktop image and session-host workflows across the configuration differences above.

Windows 365 Cloud PCs

Windows 365 Enterprise Cloud PCs sit on a different part of the same surface. Management runs through Intune by design. You manage them from the Intune admin center, with Cloud PC-specific remote actions such as Reprovision and Resize, many with bulk support. You can use Windows 365 device management and Cloud PC remote actions to define the Cloud PC-specific control set.

The table below summarizes how those control surfaces compare across the four Windows endpoint types.

Capability

Physical Windows 11

Windows 365 Cloud PC (Enterprise)

AVD single-session

AVD multi-session

Update rings for Windows

Supported

Supported

Supported

Not supported

Configuration profile templates

All

All

All except Domain Join, Wi-Fi

Certificate + VPN device tunnel only

Wipe / Remote lock / Reset password

Supported

Reprovision instead of Wipe; Remote lock and Reset password not listed

Not supported

Grayed out

Windows Autopilot OOBE

Supported

Supported

Not recommended

Not supported

Reprovision / Resize / Restore

N/A

Cloud PC-specific

N/A

N/A

 

Physical Windows devices

For physical endpoints, physical Windows remote actions and Windows update policies define the baseline control set.

Physical devices carry fine print too, and Microsoft notes that "Settings Catalog doesn't include the necessary TPM startup authentication controls" required for reliable silent BitLocker enablement, so BitLocker belongs in Endpoint Security or device configuration policy.

Windows Autopatch excludes Entra-registered devices from every update policy type that shares its backend.

Platform-specific depth limits across the estate

Depth also stops at different points by platform. Linux endpoint security covers Antivirus and EDR only, with no disk encryption or firewall policy, and on iOS/iPadOS and Android, Defender ships as an app rather than a policy type.

Firmware settings through the Device Firmware Configuration Interface reach only Autopilot-deployed Windows devices, and Intune won't deploy a Win32 app that can't install silently. Those platform-specific policy gaps at least appear in a support matrix. The less visible policy state is a policy the portal shows as assigned that never lands on the device.

"Assigned" in the portal does not mean enforced on the device

Microsoft's Intune planning guide states that Intune applies policies to the users and groups you create. Intune has no policy hierarchy, and two policies that update the same setting produce a conflict.

The flat conflict model

Intune resolves conflicts differently depending on which policy types collide. A compliance policy value wins over a configuration policy value automatically, and when several compliance policies set the same setting, the most restrictive value wins. Two configuration policies against each other behave differently. Per Microsoft, "When conflicts occur, Intune generates an error and doesn't apply either setting."

Conflicts are easy to create because the same setting often lives in Settings Catalog, device configuration templates, security baselines, and Endpoint Security policies at once, sometimes under different names. Error 0x87d101f8 is the documented result "when two different Intune profiles attempt to set the same BitLocker configuration, which forces the MDM agent to reject both instructions." When that happens, neither policy takes effect on the device even though both appear as assigned in the portal.

A management layer can surface overlapping settings across baselines and profiles before a device reports a conflict or duplicate.

Group Policy and co-management residue

Hybrid estates add a second policy source. The MDMWinsOverGP setting "only applies to policies in Policy CSP." For other CSPs, such as the Defender CSP, Microsoft's guidance says the same setting should not exist in both GPO and MDM to avoid overlapping control. For settings outside Policy CSP, Microsoft warns that GPO and MDM can create a race condition with no guaranteed winner.

Reporting lag and the compliant-by-default setting

Compliance data reaches the portal on a delay, and the default tenant setting works in the same direction.

Enrolled Windows devices sync approximately every eight hours in steady state. This means a device that failed a BitLocker setting overnight may not report the changed state until its next check-in. Advanced Analytics event latency "can exceed 24 hours."

Two tenant behaviors compound the lag. Intune marks devices with no compliance policy assigned as Compliant by default, and Microsoft recommends changing that setting to Not compliant. Microsoft's May 2026 update also states outright that values in compliance reports should be treated as informational only.

A high compliance percentage in the portal can reflect both the sync delay and unassigned devices counted as compliant.

What Conditional Access inherits

Conditional Access in Entra ID uses the same Intune compliance state as an access signal, with Microsoft Defender for Endpoint signal where available. That means Conditional Access inherits the reporting lag and the compliant-by-default tenant setting described above. Microsoft also warns that Entra-joined Azure Virtual Desktop session hosts may not satisfy compliance policies designed for user endpoints, so access decisions on session hosts can fall back on incomplete signal.

A compliance report Microsoft labels informational does not by itself verify enforcement, and assembling additional evidence means opening several consoles.

Reporting delays, tenant defaults, and Conditional Access inheritance can together drive the portal's word for a setting apart from the device's actual behavior. Reconciling the two means leaving the Intune admin center for other Microsoft consoles, which is where the operational overhead compounds.

Managing a Microsoft-first estate takes at least six consoles

Even with Intune as the central UEM platform, a full Microsoft-first estate is administered across at least six separate consoles. The July 2026 licensing change added new capabilities to Intune without collapsing any of them into a single surface.

The six consoles admins move between

A typical Microsoft-first estate routes day-to-day endpoint work through the following six admin surfaces:

  1. Microsoft Intune admin center, for physical devices and Cloud PCs
  2. Azure portal, for Azure Virtual Desktop host pools and golden images
  3. Microsoft Defender portal, which needs admin access beyond Intune for Defender for Endpoint integration
  4. Configuration Manager console, since compliance status for ConfigMgr-managed devices is not visible in Intune
  5. Microsoft Entra admin center, for identity and role prerequisites
  6. Microsoft 365 admin center, for Windows 365 Business remote management

Each console holds a different slice of the estate, and a single change (rolling out a new baseline, investigating a compliance drop, or provisioning a new Cloud PC) frequently touches more than one of them. That console-hopping is where routine endpoint work stops feeling unified.

Azure Virtual Desktop lifecycle work sits outside Intune

Azure Virtual Desktop is the clearest example of work that spans consoles. Azure Virtual Desktop management covers the Azure portal, PowerShell, and Microsoft Intune, with different control depth on each surface. Host-pool, session-host image, and auto-scaling tasks in particular stay outside Intune.

Microsoft's own walkthrough for a custom session host image uses the Azure portal, and Autoscale is Azure Virtual Desktop's "native scaling service" that admins also configure there. Host pools on the standard management approach have no session host update feature at all, and Microsoft documents admins using automation tools and processes such as PowerShell scripts, IaC templates, and CI/CD pipelines.

What the July 2026 licensing change did and did not do

The July 2026 licensing update widened what Intune includes without touching the console split. Effective July 1, 2026, Microsoft 365 E3 rose from $36 to $39 per user per month and E5 from $57 to $60 (US list price, annual commitment). In exchange, E3 gained Intune Remote Help, Intune Advanced Analytics, and Intune Plan 2. E5 additionally gained Endpoint Privilege Management, Enterprise Application Management, and Microsoft Cloud PKI.

The two operational gaps left unchanged by the licensing update are the Azure Virtual Desktop lifecycle work that stays outside Intune and the multi-hour reporting latency inside Intune. Nerdio Manager automates the Azure Virtual Desktop lifecycle work and polls available endpoint data more frequently to shorten the delay between a state change on a device and its visibility to admins.

How Nerdio Manager adds unified reporting, policy controls, and automation across the estate

Nerdio Manager deploys into your Azure tenant and presents Windows 365, Intune, and Azure Virtual Desktop in one console.

Intune policy backup and restore

Under Endpoints > Intune > Policy Management, Nerdio Manager shows tabs for Compliance Policies and Configuration Profiles. Separate tabs cover Security Baselines and Conditional Access. Applications and Windows Update have their own tabs. Nerdio Manager can create and back up Intune policies. It can also restore them, extending Intune with policy recovery capabilities the native service does not provide.

For a governance, risk, and compliance (GRC) lead, those capabilities support documented change control and recovery rather than relying only on a procedure written on paper.

Application delivery in seconds for Cloud PCs

Nerdio measures Unified Application Management (UAM) deploying apps to Windows 365 Cloud PCs in about 30 seconds while delivery through native Intune can take up to 3 hours since Intune polls on its own schedule.

The same UAM catalog, which pulls from WinGet repositories and Intune, also covers Intune-enrolled physical Windows devices and reports deployment status in near real time. For multi-session Azure Virtual Desktop, where Intune's MSIX app attach support does not apply, Nerdio Manager provides an MSIX Image Management Library that handles image-side app work.

Desktop orchestration and Cloud PC lifecycle workflows

For Azure Virtual Desktop, Nerdio Manager automates Desktop orchestration for patching and versioning, plus staging and testing, for images, session hosts, and personal desktops.

Independent testing by Dr. Benny Tritsch measured updating a custom image at 146 clicks in the native Azure portal versus 13 in Nerdio Manager, 91% fewer clicks. Reimaging session hosts dropped from 90 clicks to 10. Fewer manual steps also means fewer chances to mis-set a value on an image that every session host inherits.

Auto-Heal automation repairs broken session hosts, and patented auto-scaling stops and deallocates idle hosts on schedule. Syneos Health, a clinical research organization, reported 70% faster configuration changes after adopting Nerdio Manager.

Reporting an auditor can read

Agentless monitoring covers Windows 365, Intune-enrolled devices, and Azure Virtual Desktop endpoints from the same console. Admins can configure the polling interval for available endpoint data down to one minute, with a default of every five minutes. That polling interval does not change Intune's roughly eight-hour steady-state device sync, and it does surface the most recent data Intune has published sooner than the native admin center does.

Executive dashboards track admin clicks and time saved, along with cost savings and automation impact. RBAC controls access, audit logging records changes, and feature rollback can reverse them. These controls produce the evidence an auditor asks for. They support the compliance strategy your organization owns, without certifying compliance with any framework.

Kevin Thompson, Senior Cloud Operations Manager at Sage, put the operational payoff in headcount terms. "Before Nerdio, we were adding one head for every 40 customers we added. Now, we have grown from 200 to 1,000 customers without adding any additional headcount, saving 20-plus heads."

Even with unified reporting in place, a handful of Intune tenant defaults still need a direct review before an audit.

Five settings to check in your estate before the next audit

Before the next audit cycle, run these five checks in the Intune admin center to surface the enforcement gaps a raw compliance percentage tends to hide.

  1. Change "Mark devices with no compliance policy assigned as" from Compliant to Not compliant. Microsoft recommends the change, and the default inflates the compliance number.
  2. Filter device configuration reports for Enterprise multi-session and count the "Not applicable" rows. Each one is an assigned policy that the endpoint does not enforce.
  3. Reconcile the Hybrid Microsoft Entra ID joined device count against the Intune enrolled count.
  4. Export Intune audit logs and Entra ID sign-in logs before they expire. The Intune admin center retains audit logs for up to 30 days, Entra ID P1 and P2 retain 30-day sign-in logs, and expired sign-in logs cannot be retrieved retroactively.
  5. Search device status for error 0x87d101f8 and review any overlapping baselines that set the same BitLocker value.

Together, these five checks expose the gaps behind the 98% figure from the opening scenario. Admins can then replace unsupported multi-session update rings with Settings Catalog quality settings and use more frequent polling to surface newly available status data sooner.

If your estate spans laptops, Cloud PCs, and session hosts, the enforcement differences between them can create audit findings. Get a demo to see how Nerdio Manager works across your Windows 365, Intune, and Azure Virtual Desktop environment, or try it free in your Azure tenant.

Frequently asked questions about unified endpoint management

Ready to get started?