← Sentinel query library

Identity governance · Microsoft Sentinel

Inspect properties changed by application updates

Expand recorded application update properties and retain raw old/new values for review without assuming all fields have the same JSON shape.

Before you run

Data & scope

Required tables
AuditLogs
Time window
7 days
  • Microsoft Entra ID connector with AuditLogs collected throughout the stated lookback and access to audit payloads.
  • Any Microsoft Entra ID license supports audit ingestion; workspace query permissions and appropriate directory evidence access are required.

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.
AuditLogs
| where TimeGenerated >= ago(7d) and TimeGenerated <= now()
| extend AuditOperation = coalesce(ActivityDisplayName, OperationName)
| where AuditOperation =~ "Update application" and Result =~ "success"
| extend ActorObjectId = coalesce(tostring(InitiatedBy.user.id),
        tostring(InitiatedBy.app.servicePrincipalId)),
    ActorName = coalesce(tostring(InitiatedBy.user.userPrincipalName),
        tostring(InitiatedBy.app.displayName))
| mv-expand Target = TargetResources
| where tostring(Target.type) =~ "Application"
| extend ApplicationObjectId = tostring(Target.id),
    ApplicationName = tostring(Target.displayName)
| mv-expand ChangedProperty = Target.modifiedProperties
| extend PropertyName = tostring(ChangedProperty.displayName),
    OldValue = tostring(ChangedProperty.oldValue), NewValue = tostring(ChangedProperty.newValue)
| project TimeGenerated, AADTenantId, AuditId = Id, AuditOperation, ActorObjectId,
    ActorName, ApplicationObjectId, ApplicationName, PropertyName, OldValue, NewValue, CorrelationId
| order by TimeGenerated desc, ApplicationObjectId asc, PropertyName asc
| take 200

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

Application updates can change redirect destinations, identifiers and other behavior that matters to an AI application’s trust boundary. This query exposes the modified properties recorded by successful generic Update application events. It is designed for change inspection, not automatic classification of every update as harmful.

Preserve the original property representation

The first expansion selects Application targets; the second produces one row per recorded modified property. ApplicationObjectId is the directory application object’s ID, not the application client ID or a service-principal object ID. The initiator remains separate from the modified object.

OldValue and NewValue are the values recorded in the audit property contract. They can contain serialized arrays or other representations. A textual difference can reflect ordering or formatting rather than a meaningful security change. Parse a verified property schema before writing a comparison that claims a URI, permission or audience was added. Modified-property contract.

Events with an empty modified-properties collection produce no property rows. The query also excludes dedicated credential-management and safe-rollout operations, which have distinct activity names. Review those separately instead of interpreting this view as a complete application change inventory.

Assess the effect in context

Compare the changed values with an approved configuration revision and deployment record. For a redirect-related change, verify the exact destination, scheme, host and path against the application’s intended flow. Do not visit or execute destinations copied from an unfamiliar audit payload during triage.

Inspect related ownership, credential and consent changes when the same object is involved. A benign release, application rename or configuration normalization can explain an update. An apparently small unexplained change can still affect a sensitive sign-in path, so prioritize impact rather than the number of properties.

Validate representative changes

Use a harmless application update to confirm target typing and property names. Test an event changing two properties, an empty property list and a service-principal update. The first should yield two property rows; the others should not be mistaken for equivalent application updates.

The 200-row cap applies after expansion and can split an event’s property set. Narrow to an audit ID for a complete review. This documentation-checked hunt has not been tenant-tested. Microsoft’s application monitoring guidance provides broader context; the audit diff alone does not prove exploitation or establish current effective configuration.

Verify the source

Microsoft references

  1. Microsoft Learn — AuditLogs table schema ↗
  2. Microsoft Learn — Microsoft Entra audit activities ↗
  3. Microsoft Learn — Target resource contract ↗
  4. Microsoft Learn — Modified property contract ↗
  5. Microsoft Learn — Security operations for applications ↗
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 →