Sign-ins from Unmanaged & Non-compliant Devices
The question it answers: Which applications did people reach successfully from unmanaged or non-compliant devices in the last 7 days?
Which applications people successfully reach from devices your organisation does not manage, or manages but considers non-compliant. Apps high on this list are where ‘require compliant device’ or app-enforced restrictions would change the most - and where data most easily lands on private hardware.
At a glance
Section titled “At a glance”| Where in the app | Entra ID › Sign-in Analytics › Unmanaged Device Sign-ins |
| Workload | Entra ID |
| Kind | Table |
| Data | Built from the tenant data IntensiveReports keeps in memory and refreshes in the background, so it opens at once. |
| Licence | Microsoft Entra ID P1. |
| Report id (API and MCP) | entra.sign-ins.unmanaged-device-sign-ins |
Columns
Section titled “Columns”| Column | Key | Type |
|---|---|---|
| App | Name | Text |
| Type | Category | Status |
| Users | DistinctUsers | Text |
| Sign-ins | Count | Text |
| Breakdown | Finding | Text |
| Device OS | Secondary | Text |
| Users (sample) | Detail | Text |
What it needs
Section titled “What it needs”Licence: Microsoft Entra ID P1.
Application permissions on the IntensiveReports app registration (all permissions):
| Permission | API | What it allows | Note |
|---|---|---|---|
AuditLog.Read.All | Microsoft Graph | Read all audit log data |
Data sources it reads
GET /beta/auditLogs/signIns (7 days)
Through the API and MCP
Section titled “Through the API and MCP”GET /ir-api/v1/reports/entra.sign-ins.unmanaged-device-sign-ins?size=100An AI assistant reads it with the MCP tool get_report and the id entra.sign-ins.unmanaged-device-sign-ins. The client needs the Read grant for Entra ID. See Using the API.