What should you use to prevent concurrency conflicts during receipt processing with blobs?

Blob leases provide an exclusive write lock on a blob for a specified duration, typically 15 to 60 seconds, or infinitely. This prevents other clients from writing to or deleting the blob while the lease is active, effectively managing concurrency during operations like receipt processing. If a client tries to write to a leased blob without the lease ID, the operation will fail. Blob properties, such as ETag or Last-Modified-Time, can be used for optimistic concurrency control (checking if the blob has changed since it was last read), but they don't prevent concurrent writes. Blob SnapshotTime is used for creating point-in-time copies of a blob, not for concurrency management. Blob metadata stores user-defined key-value pairs and does not inherently prevent concurrent access.