Failing App Sign-ins
The question it answers: Which apps and scripts failed to sign in during the last 7 days, why, and are they still failing?
Apps and scripts that keep trying to sign in with an expired secret, an invalid certificate or a deleted registration. Each row is an integration that is already broken - or a leaked, rotated secret someone is still trying.
At a glance
Section titled “At a glance”| Where in the app | Entra ID › Sign-in Analytics › Failing App 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.failing-app-sign-ins |
Columns
Section titled “Columns”| Column | Key | Type |
|---|---|---|
| App | Name | Link |
| Error | Category | Status |
| Status | Finding | Text |
| Failures | Count | Text |
| Source IPs | DistinctUsers | Text |
| Detail | Detail | Text |
| Last failure | LastSeen | DateTime |
| App ID | Secondary | Text |
Filters
Section titled “Filters”| Filter | Key (API) | On when the page opens |
|---|---|---|
| Only apps still failing | failing | Yes |
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?$filter=signInEventTypes/any(t: t eq 'servicePrincipal') (7 days)
Through the API and MCP
Section titled “Through the API and MCP”GET /ir-api/v1/reports/entra.sign-ins.failing-app-sign-ins?size=100GET /ir-api/v1/reports/entra.sign-ins.failing-app-sign-ins?filter=failingAn AI assistant reads it with the MCP tool get_report and the id entra.sign-ins.failing-app-sign-ins. The client needs the Read grant for Entra ID. See Using the API.