Endpoint management
UEM
Unified Endpoint Management
Unified Endpoint Management describes the consolidation of device and application management for every major endpoint type, Windows, macOS, iOS/iPadOS, Android, and now Linux, under a single management platform and policy model, replacing the historical split between separate tools for PCs, one for mobile devices, and often another again for Mac.
Why UEM matters in a Microsoft estate
UEM matters for endpoint teams because device, app, compliance, update, and troubleshooting signals often sit across several Microsoft admin areas. Linking these terms back to Intune and device-reporting routes helps readers move from definition to action.
How UEM shows up in practice
The term emerged as the natural evolution of Mobile Device Management once organisations realised the same underlying problems, enrolment, configuration, compliance enforcement, security policy, and application delivery, applied across every device type an employee might use. Maintaining Configuration Manager for Windows, a separate MDM product for mobile, and manual processes for Mac created duplicated policy logic, inconsistent security baselines across platforms, and a worse admin experience with no single view of an organisation's actual device estate. Microsoft Intune is Microsoft's UEM platform, built on the Mobile Device Management and Mobile Application Management capabilities described elsewhere in this glossary but positioned specifically around that single-pane-of-glass promise: one console, the Intune admin center, for enrolling and managing every supported platform, with policy types, compliance policies, configuration profiles, and endpoint security policies, designed to apply consistent, platform-appropriate security outcomes rather than identical settings across genuinely different operating systems.
In practice the "unified" part of UEM is aspirational to a degree that varies by platform: Windows management through Intune is deep and mature, benefiting from Microsoft's own CSP-based management stack and years of Configuration Manager heritage now expressed as cloud policy, while non-Windows platforms depend on what Apple's and Google's respective MDM frameworks expose. Certain settings and remote actions that exist natively on Windows simply have no equivalent on iOS or Android, and admins moving from a Windows-first mindset are regularly caught out by capability gaps that aren't a Microsoft limitation but a platform one.
UEM's real payoff in a Microsoft estate is consolidation of both operational effort and licence spend: retiring a legacy MDM product or a standalone Mac management tool in favour of Intune removes a parallel subscription and a parallel admin skill set. But that consolidation only delivers savings if the legacy tool is actually decommissioned and its licences cancelled, a step that gets missed surprisingly often when a migration is declared complete at the point devices are dual-enrolled rather than at the point the old platform is switched off, leaving an organisation paying for two overlapping UEM platforms for months or years after the "unified" migration was supposedly finished.