← Sentinel query library

Identity · Microsoft Sentinel

Investigate noninteractive user sign-in failures

Separate background delegated authentication failures by user, application, resource and reported error without confusing them with workload identities.

Before you run

Data & scope

Required tables
AADNonInteractiveUserSignInLogs
Time window
24 hours
  • Microsoft Entra ID connector with AADNonInteractiveUserSignInLogs explicitly selected and arriving.
  • Microsoft Entra ID P1 or P2 for sign-in ingestion and access to this table; SigninLogs alone is insufficient.

Documentation review by Codex (AI). No live-tenant execution or detection-performance claim. Validate schema, data coverage and expected results in your workspace.

Kusto Query Language
Download .kql
// Hunting starter. Documentation checked 2026-11-13; not tenant-tested.
AADNonInteractiveUserSignInLogs
| where TimeGenerated >= ago(1d) and TimeGenerated <= now()
| extend NumericResult = tolong(ResultType)
| where ResultType =~ "Failure"
    or (isnotnull(NumericResult) and NumericResult != 0)
| summarize FailureRows = count(), FirstSeen = min(TimeGenerated),
    LastSeen = max(TimeGenerated), Descriptions = make_set(ResultDescription, 5),
    SourceIPs = make_set(IPAddress, 10), CorrelationIds = make_set(CorrelationId, 5)
    by AADTenantId, UserId, UserPrincipalName, AppId, AppDisplayName,
        ResourceDisplayName, ResultType, ConditionalAccessStatus
| order by FailureRows desc
| take 200

Read-only query. Run in your own authorized workspace after checking prerequisites.

Background delegated authentication can fail while an application still appears signed in to the user. This hunt groups those failures by identity, client application, destination and reported result. Use it when an agent acting for a user or another delegated application reports refresh, session or access problems.

Distinguish delegated and application identities

Noninteractive user sign-ins are performed on behalf of a user without a fresh interactive authentication prompt. They are different from application-only service-principal authentication and managed identity activity. Microsoft’s noninteractive sign-in explanation provides the event context.

The table reference describes Success and Failure result strings. The query also handles convertible nonzero numeric results so a numeric error remains visible. Empty or unrecognized nonnumeric values are not automatically declared failures. Inspect the raw vocabulary in your own ingestion before assuming the filter covers every representation. Table contract.

FailureRows counts collected records. Background retries can generate many records from a single broken application dependency. Counts should not be interpreted as the number of people actively typing a password or the number of protected operations denied by a downstream API.

Investigate the dependency

Open representative events and correlate their times with application errors. Determine whether a password reset, session revocation, new policy, expired grant or account change explains the behavior. Check the reported resource as well as the client application: a successful application session can still fail to acquire a token for a particular downstream service.

Use the sampled correlation IDs as investigation pivots and retain the original event IDs when collecting detailed evidence. Do not place access tokens or refresh tokens in incident notes. Confirm expected behavior with the application owner before suppressing a high-volume pattern.

Tune and validate

Legitimate session expiry, intermittent connectivity and retry loops can create large groups. Prioritize sensitive identities and unfamiliar resources, but keep any exclusion narrow and time-bound. A low count does not make an event harmless, and a familiar client can still be used in a compromised session.

Test a known numeric failure, a literal Failure value, success and missing-result cases. Verify that failures appear while missing values do not become manufactured incidents. This documentation-checked query has not been executed in a tenant. Collection must explicitly include this table; empty SigninLogs output is not evidence that background delegated authentication is healthy.

Verify the source

Microsoft references

  1. Microsoft Learn — AADNonInteractiveUserSignInLogs schema ↗
  2. Microsoft Learn — Noninteractive user sign-ins ↗
  3. Microsoft Learn — Microsoft Entra ID connector ↗
Before turning a hunt into an alert

Measure normal activity, validate known test cases, account for ingestion delays, choose a threshold and entity mapping, and assign an owner. Results require investigation.

Follow the detection learning path →