Skip to content

Update blob-inventory.md Handling duplicates #127354

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 6 commits into from
Jul 11, 2025
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions articles/storage/blobs/blob-inventory.md
Original file line number Diff line number Diff line change
Expand Up @@ -434,6 +434,16 @@ If a container or directory is deleted with soft-delete enabled, then the contai

Only blobs that are explicitly deleted appear in reports. Therefore, to obtain a complete listing of all soft-deleted blobs (directory and all child blobs), workloads should delete each blob in a directory before deleting the directory itself.

### Handling duplicates in Blob Inventory

Blob Inventory operates on a distributed system, which means that in rare cases, duplicate blob entries might appear in your reports.

If when post processing your inventory report, your use case requires unique blob entries, you can use the `Name` field to identify and return only the unique blobs.


If your report includes blob versions, use both the `Name` and `Version ID` fields together to identify and return only the unique blobs and versions.


## Next steps

- [Enable Azure Storage blob inventory reports](blob-inventory-how-to.md)
Expand Down