Before you run
Data & scope
- Required tables
- 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.
// Hunting starter. Documentation checked 2026-11-13; not tenant-tested.
AzureActivity
| where TimeGenerated >= ago(1d) and TimeGenerated <= now()
| where CategoryValue =~ "Administrative"
| where OperationNameValue in~ (
"Microsoft.Storage/storageAccounts/write",
"Microsoft.Storage/storageAccounts/privateEndpointConnections/write",
"Microsoft.Storage/storageAccounts/privateEndpointConnections/delete")
| where ActivityStatusValue =~ "Succeeded"
| extend ReviewScope = case(
OperationNameValue has "privateEndpointConnections", "Private endpoint connection",
"Account update; network effect requires configuration comparison")
| project TimeGenerated, ReviewScope, OperationNameValue,
SubscriptionId, ResourceGroup, ResourceId = coalesce(_ResourceId, ResourceId),
Caller, CallerIpAddress, ActivityStatusValue, EventDataId, OperationId, CorrelationId
| order by TimeGenerated desc
| take 200
Read-only query. Run in your own authorized workspace after checking prerequisites.
This hunt produces a review queue for storage management changes that may affect network access. It selects successful account writes and private-endpoint connection writes or deletions. It does not detect a firewall opening directly: the generic storageAccounts/write action also covers changes unrelated to networking.
Require a configuration difference
For each account write, compare the approved previous state with the effective current configuration. Review public-network access, firewall defaults, allowed networks and relevant exceptions only when those settings actually changed. A tag-only update should not become a “public exposure” incident because it shares the same management action.
Private-endpoint connection changes need their own interpretation. Creation, approval, update and deletion do not all have the same effect, and deleting one connection does not prove that a public endpoint became reachable. Resolve the connection and examine the surrounding network design.
The explicit action names come from Microsoft’s Storage permissions reference. This recipe does not inventory all network resources that could affect a storage client, such as DNS, routing or the client’s virtual network.
Separate reachability from permission
Storage firewall rules govern access through the public endpoint, while requests still require applicable authorization. A newly permitted network source is not automatically allowed to read every object. Conversely, a restricted public endpoint does not remove a client’s authority through another valid path. Storage network access model.
For an AI ingestion or retrieval service, identify the actual endpoint, identity and path it uses. Test expected allowed and denied paths with nonsensitive objects under an approved validation plan. Check whether a deployment unintentionally shifted traffic from private to public connectivity, even when application behavior appears unchanged.
Preserve caller, resource, time and correlation evidence. Compare the management action with infrastructure review records and the responsible platform owner. A successful API response proves recorded management completion, not successful end-to-end application connectivity.
Tune and validate
Routine infrastructure convergence, disaster-recovery work and private-endpoint maintenance can produce legitimate entries. Scope exceptions to the expected configuration difference and change window rather than excluding every account write by an automation identity.
Validate using a known tag-only update, an approved network change and a private-endpoint connection event. The first case should demonstrate why a management event alone cannot classify exposure. Narrow by subscription or account when the 200-row cap is reached. This documentation-checked query scans 24 hours, has not run in a tenant, and does not calculate effective network reachability or data authorization.
Verify the source
Microsoft references
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 →