The .NET client library should support TransactionScope
Often when doing batch processing you may want a all or nothing approach when uploading to blob storage with multiple files. In this situation it would be very useful if the .NET Microsoft.WindowsAzure.Storage.Blob classes supported being within a System.Transactions.TransactionScope.
My proposal for behavior is if there was a ambient transaction during a blob operation it should support at minimum ReadUncommited transaction isolation (Higher levels of isolation could be supported via existing locking/leasing mechanisms in blob storage).
Any overwrite operation will snapshot the previous blob, if the transaction is rolled back the snapshot is promoted back to the main data, if the transaction is committed the snapshot of the overwritten data will be deleted.