Validate Blob inventory output before accepting its completion event

Source facts

BlobInventoryPolicyCompleted can be raised for a run that fails before processing begins, such as an invalid policy or missing destination container. The event name alone therefore does not establish a successful report.

Microsoft says generation of the checksum file marks completion of a rule run. That checksum covers the manifest, which describes the rule’s generated inventory files. A large inventory can produce multiple report files. Microsoft Learn.

Applicability

Identify the inventory rule, destination and downstream consumer. Decide which run and rule definition the consumer expects; do not substitute a report left by an earlier run when current output is missing.

DSE recommendation

DSE recommends a report-acceptance step that checks the event outcome, corresponding manifest and checksum, and the expected set of output files. Record a failed or incomplete run as such and keep dependent analysis on hold. Avoid selecting the first matching CSV or Parquet file and silently treating it as the whole inventory.

Verification

Test the consumer against a successful run, a documented pre-run failure scenario and a run represented by multiple files. Confirm it associates all evidence with the correct rule and run. Verify that missing output creates an actionable failure instead of an empty-success report. Retain the accepted manifest and file list alongside the resulting analysis for later reconciliation.

Official references

Microsoft Learn: Azure Storage blob inventory. Source retrieved September 9, 2026.