Menu
I can't find any information on this anywhere and yet the question is simple.
Can I wrap storage-related actions in a TransactionScope such that e.g. if there is a rollback, the uploaded file is rolled back also?
If the native APIs don't do this already, is there a public implementation anywhere?
938
Azure Files supports identity-based authorization over Server Message Block (SMB) through Azure AD DS. You can use RBAC for fine-grained control over a client's access to Azure Files resources in a storage account.
Azure Storage space is charged based on storage capacity, storage transaction numbers (the number of read and write operations performed on the storage), and the amount of data transferred.
Different Azure Storage types (File, Blob, Queue and Table)
If you're referring to Table or Blob updates, there's no notion of explicit commit or rollback. When you make an API call (whether direct REST call or via PowerShell / CLI / SDK), it's just an action against storage, and it will either succeed or fail (although some actions take a while and the call may return before completion). There's no transaction scope wrapping this action. You'd need to take care of undoing your Table / Blob updates at an app level.
187
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
