Azure Blob Event Grid does not provide Blob Version ID for BlobCreated/BlobDeleted events

Question

Azure Blob Event Grid does not provide Blob Version ID for BlobCreated/BlobDeleted events

Shiv 0

Hi Microsoft Team,

We have enabled Blob Versioning on an Azure Storage Account and created an Event Grid subscription for:

Microsoft.Storage.BlobCreated
Microsoft.Storage.BlobDeleted

We are using the Event Grid Schema and sending events to a Salesforce webhook.

Our requirement is to maintain blob version history in Salesforce. However, the Event Grid event payload does not contain the Blob Version ID (versionId). The documented BlobCreated and BlobDeleted schemas also don't expose this property.

Additionally, when we delete a specific blob version, we are not receiving a BlobDeleted event that identifies that particular version.

Questions:

Is there any supported way to get the Blob Version ID in an Event Grid BlobCreated/BlobDeleted event?
Is there an Event Grid event specifically triggered when an individual blob version is deleted?
If Event Grid cannot provide the Version ID, what is the recommended Azure-native solution to achieve this without using an Azure Function?

Our target flow is:

Azure Blob → Event Grid → Salesforce Webhook → Salesforce Version History

We need a reliable way to identify the exact blob version affected by each create/delete operation.

Thank you.

Tejaswini Billakurthi 250 Reputation points Microsoft External Staff Moderator

2026-09-08T08:54:00.7866667+00:00

Hi @Shiv ,

Thank you reaching out to Microsoft Q & A!

The behaviour you're seeing matches the documented schema. The Blob Storage Event Grid data object contains api, clientRequestId, requestId, eTag, contentType, contentLength, blobType, url and sequencer, but no versionId — so there is currently no supported way to read the blob version ID from a BlobCreated / BlobDeleted event: https://learn.microsoft.com/azure/event-grid/event-schema-blob-storage#event-properties

On your second question, deleting an individual version won't raise an event either. The documentation states that a BlobDeleted event is added only when the base (root) blob is deleted, not when a version or snapshot is deleted: https://learn.microsoft.com/azure/storage/blobs/storage-blob-change-feed#conditions-and-known-issues

For the version history requirement, the Azure-native source that does carry the version ID is the blob change feed. From schema version 4 onward, each record includes data.blobVersion, along with previousInfo.BlobVersion and LastVersion for the version that was superseded: https://learn.microsoft.com/azure/storage/blobs/storage-blob-change-feed#change-event-records

The change feed is a durable, per-blob ordered log written to the $blobchangefeed container within a few minutes of the change, so it is read (pulled) rather than pushed. A Logic App on a recurrence trigger can read those records and write to Salesforce using the built-in Salesforce connector, with no Azure Function involved.

If you require an authoritative version history, Blob Change Feed is the recommended approach because it records version information directly. If near real-time processing is required, Event Grid can trigger a Logic App that queries Blob Storage, but the retrieved version ID reflects the current state of the blob at the time of the lookup and may not represent the exact version associated with the original event.

Please "Upvote the Answer" if this information helped you. This will help us and others in the community as well.

1 answer

Your answer

Answer 1

Shiv 0

Thank you for the clarification.

I have one follow-up question regarding deletion of a specific blob version.

You mentioned that Blob Change Feed contains the blobVersion for version-related changes. However, you also mentioned that deleting an individual blob version does not generate a BlobDeleted event.

For example, if a blob has:

test.pdf 
├── Version 1 
├── Version 2 
└── Version 3

and the user deletes Version 2 only, is this deletion recorded anywhere in Blob Change Feed, along with the deleted Version ID?

If it is not recorded in Change Feed, what is the recommended Azure-supported way to detect that a specific blob version was deleted and obtain the deleted Version ID so that we can notify/update Salesforce?

Our required flow is:

Azure Blob 
↓ 
Specific Blob Version Deleted/ new blob uploads/version uploads 
↓ 
Detect Deleted Version ID 
↓ 
Salesforce

Our requirement is to maintain accurate version history in Salesforce, including individual blob-version deletions.

Thank you.

Tejaswini Billakurthi 250 Reputation points Microsoft External Staff Moderator

2026-09-10T06:43:15.6+00:00

Hi @Shiv ,

Thank you for the response!

On the documented behaviour: the change feed article states "BlobDeleted events are not generated when blob versions or snapshots are deleted. A BlobDeleted event is added only when a base (root) blob is deleted."

https://learn.microsoft.com/azure/storage/blobs/storage-blob-change-feed#conditions-and-known-issues

So there's no BlobDeleted event for a version-only deletion. I haven't found public documentation confirming whether any other change feed record is written for that operation, so I'd treat that as unconfirmed rather than settled either way.

The other Azure-native source worth looking at is Azure Storage resource logs. A version-scoped delete is issued as DELETE https://<account>.blob.core.windows.net/<container>/<blob>?versionid=<DateTime> — the versionid URI parameter is what targets the individual version:

https://learn.microsoft.com/rest/api/storageservices/delete-blob

Enabling a diagnostic setting with the StorageDelete category sends those requests to the StorageBlobLogs table, which has a Uri column recording the requested URI:

https://learn.microsoft.com/azure/azure-monitor/reference/tables/storagebloblogs

Whether the version ID is present in that column in your account is worth checking against a single test deletion before building on it. If it is, the flow stays function-free: diagnostic setting → Log Analytics → Logic App on a recurrence using the Azure Monitor Logs connector → Salesforce connector. Storage logging is best-effort rather than the transactional guarantee change feed provides, so it fits best alongside change feed — which does carry data.blobVersion for version creation from schema version 4 onward — rather than replacing it.

Please "Upvote the Answer" if this information helped you. This will help us and others in the community as well.