Your compliance team requires an ordered, durable history of blob create, modify, and delete events for all containers in a storage account, and your .NET worker must be able to resume processing from the last processed position after restarts. What should you implement?

The Azure Storage change feed provides an ordered, durable, and complete record of all blob changes, including create, modify, and delete operations. It's designed for reliable, resumable processing, as it stores a continuation token that your .NET worker can use to resume from the last processed position after a restart. Event Grid events are not guaranteed to be ordered and are not durable for long-term replay, making them unsuitable for a complete historical record. Diagnostic logs in Log Analytics provide audit trails but are not designed for reliable, resumable processing of individual blob changes for application logic. Soft delete and blob versioning help with data recovery and historical states but don't provide a stream of events for processing, requiring complex and inefficient reconstruction logic.