Globally unique resources that provide access to data management services and serve as the parent namespace for the services.
Hello JeffreyCMI
Thank you for posting the question!
To investigate further could you please help me with the below details.
- Are you currently tracking your Azure costs in the Azure Cost Management tool?
- Have you used any specific configurations for your storage account that might affect pricing (like redundancy options)?
However, in the meantime you can check the below suggestion. Your Storage Actions pricing calculation is mostly correct:
- Task execution: $0.25 ✓
- Objects scanned: (600,000 / 1 million) × $0.10 = $0.06 ✓
- Objects targeted: (600,000 / 1 million) × $1.00 = $0.60 ✓
I expect to be charged Cold-tier write operations at (600,000 / 10,000) * $0.18 = $10.80. (West US 2, LRS, Flat Namespace). Please confirm my intuition is correct.?
- Yes, you'll be charged for Cold tier write operations at (600,000 / 10,000) × $0.18 = $10.80. Each blob tier change requires a write operation.
But am I also charged for blob list operations when using Storage Actions? Anything else?
Please be informed that most actions incur charges for operations on the storage account, and Storage Actions needs to enumerate blobs to identify targets. However, the specific list operation charges aren't clearly detailed in the pricing documentation.
You would likely incur some list operation costs, but these are typically much smaller than write operations (usually around $0.05-0.06 per 10,000 operations in West US 2).
Since you're moving to Archive tier, you'll also incur Archive write operation charges for the 600,000 blobs being written to Archive storage. At the end of your billing cycle, the charges for each meter are summed. Your bill or invoice shows a section for all Azure Storage Actions costs. There's a separate line item for each meter.
Regarding SDK vs Storage Actions comparison:
The main cost difference is the Storage Actions service fee ($0.91) versus your compute costs to run the SDK solution. For 600,000 blobs, Storage Actions might be more cost-effective unless you have very efficient compute resources, but SDK gives you more control and cost transparency.
Let me know if you have any questions, we are here to assist you.
Please do consider to “up-vote” wherever the information provided helps you, this can be beneficial to other community members.