Stuck Remote Actions (wipe, retire, lock)
The question it answers: Which wipe, retire and lock actions have not completed because the device never checked in?
A wipe or lost-mode lock only happens when the device checks in. A lost laptop that never received its wipe still holds the data. Intune Audit Log shows who issued an action; this report shows whether it completed.
At a glance
Section titled “At a glance”| Where in the app | Intune › Device Operations & Hardening › Stuck Remote Actions |
| Workload | Intune |
| Kind | Findings list · dashboard tile |
| Data | Read from Microsoft 365 when someone first opens it, then kept for the report cache lifetime (Settings > Data & cache, 1 hour unless changed). |
| Licence | Microsoft Intune. |
| Report id (API and MCP) | intune.operations.stuck-remote-actions |
Columns
Section titled “Columns”| Column | Key | Type |
|---|---|---|
| Severity | Severity | Status |
| Action | Category | Text |
| Device | Subject | Link |
| Check | Setting | Text |
| State | Value | Text |
| Finding | Finding | Text |
| User / OS / last sync | Detail | Text |
| Issued | When | Date |
| Days | Number | Number |
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).
What it needs
Section titled “What it needs”Licence: Microsoft Intune.
Application permissions on the IntensiveReports app registration (all permissions):
| Permission | API | What it allows | Note |
|---|---|---|---|
DeviceManagementManagedDevices.Read.All | Microsoft Graph | Read Microsoft Intune devices |
Data sources it reads
GET /beta/deviceManagement/managedDevices?$select=deviceActionResults
Through the API and MCP
Section titled “Through the API and MCP”GET /ir-api/v1/reports/intune.operations.stuck-remote-actions?size=100An AI assistant reads it with the MCP tool get_report and the id intune.operations.stuck-remote-actions. The client needs the Read grant for Intune. See Using the API.