← Sentinel query library

Cloud control plane · Microsoft Sentinel

Review successful Azure resource deletion operations

Find recorded control-plane deletions, preserve caller and correlation evidence, and separate completed management operations from requests still in progress.

Before you run

Data & scope

Required tables
AzureActivity
Time window
24 hours
  • Azure Activity export from the relevant subscriptions to AzureActivity in this workspace.
  • Query access and at least 24 hours of retained Administrative activity; portal Activity Log alone does not populate this table.

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.
AzureActivity
| where TimeGenerated >= ago(1d) and TimeGenerated <= now()
| where CategoryValue =~ "Administrative"
| where OperationNameValue endswith "/delete"
| where ActivityStatusValue =~ "Succeeded"
| project TimeGenerated, SubscriptionId, ResourceGroup,
    ResourceId = coalesce(_ResourceId, ResourceId),
    OperationNameValue, Caller, CallerIpAddress,
    ActivityStatusValue, ActivitySubstatusValue,
    EventDataId, OperationId, CorrelationId
| order by TimeGenerated desc
| take 200

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

Use this inventory during an unexplained outage, a destructive-change investigation, or a review of retirement automation. It returns successful Administrative operations whose management action ends in /delete. The selection is deliberately broad: a deleted policy assignment, deployment object or diagnostic setting can appear alongside a deleted workload resource.

Read the event as management evidence

The success filter excludes Started, Accepted and failed operations from this particular view. Keep the operation name and resource identifier together: deletion of a deployment record does not establish deletion of every resource that deployment once created. Likewise, a parent-resource transaction can affect several children without producing a conveniently complete list of individual child deletions.

Azure distinguishes management activity from resource-specific data operations. Deleting a blob, secret version or database row generally requires the corresponding resource telemetry. An empty result here cannot establish that all application data still exists. Activity Log scope.

Each output row is a recorded event, not a guaranteed unique destructive transaction. Use EventDataId to recognize repeated delivery, and OperationId and CorrelationId to reconstruct related records. Those identifiers serve different purposes; do not discard a child event merely because it shares a correlation value. Event schema.

Investigate consequence and authority

Confirm the resource’s authoritative current state and its expected owner. Compare the event time with approved infrastructure changes, expiry policies, incident-response actions and service migrations. Resolve the caller to a directory identity where possible; a caller string and an IP address alone do not prove which person approved a pipeline run.

Preserve the relevant change request, deployment version and affected-resource inventory before recovery work changes the evidence. Assess dependent agents, retrieval indexes, model deployments and logging destinations. A small deleted control object can create wider operational impact than its resource name suggests.

Tune and validate

Expected teardown pipelines and ephemeral test environments are common results. Scope exceptions to an identified automation identity, subscription and resource pattern, with an owner and expiry. Avoid excluding all deletion events from a highly privileged deployment principal.

The 200-row cap limits returned evidence, not scanned work. Narrow the time or subscription when the result fills that cap. Verify one approved historical deletion and its related management records; no new destructive test is needed. This documentation-checked hunt has not run in a tenant and does not classify a deletion as malicious or determine whether recovery is possible.

Verify the source

Microsoft references

  1. Microsoft Learn — AzureActivity table ↗
  2. Microsoft Learn — Activity Log scope and limitations ↗
  3. Microsoft Learn — Activity Log event schema ↗
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 →