Skip to content

Intune Primary User Mismatch (Windows)

The question it answers: Which Windows devices are used mostly by someone other than their Intune primary user?

The primary user decides who sees the device in Company Portal, who gets user-targeted apps, and who the asset belongs to. When the actual user differs - hand-me-down laptops, pooled devices - asset records and self-service go wrong. Leaver Devices covers devices of leavers.

Where in the appIntune › Device Operations & Hardening › Primary User Mismatch
WorkloadIntune
KindFindings list · dashboard tile
DataRead from Microsoft 365 when someone first opens it, then kept for the report cache lifetime (Settings > Data & cache, 1 hour unless changed).
LicenceMicrosoft Intune.
Report id (API and MCP)intune.operations.primary-user-mismatch
ColumnKeyType
SeveritySeverityStatus
IssueCategoryText
DeviceSubjectLink
CheckSettingText
Primary userValueText
FindingFindingText
Signed in (30 days)DetailText
Last sign-inWhenDate
Users (30 days)NumberNumber

A findings list hides columns that no row fills. Severity is Critical, Serious, Warning, OK or Info; rows rated Critical, Serious or Warning need attention (Working with findings).

Licence: Microsoft Intune.

Application permissions on the IntensiveReports app registration (all permissions):

PermissionAPIWhat it allowsNote
DeviceManagementManagedDevices.Read.AllMicrosoft GraphRead Microsoft Intune devices
User.Read.AllMicrosoft GraphRead all users’ full profiles
User-LifeCycleInfo.Read.AllMicrosoft GraphRead all users’ lifecycle information
Data sources it reads
  • GET /beta/deviceManagement/managedDevices?$select=userId,usersLoggedOn&$filter=operatingSystem eq 'Windows'
  • GET /v1.0/users (cached)
GET /ir-api/v1/reports/intune.operations.primary-user-mismatch?size=100

An AI assistant reads it with the MCP tool get_report and the id intune.operations.primary-user-mismatch. The client needs the Read grant for Intune. See Using the API.