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.
Do Azure storage-related APIs participate in System.Transactions?
-
23-06-2022 - |
Question
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?
Solution
Licensed under: CC-BY-SA with attribution
Not affiliated with StackOverflow