Hey everyone! I'm trying to use a single Azure Blob Storage provision for two separate organizations. My plan is to differentiate the containers by adding organization prefixes, such as `a-container-1` and `b-container-1`, and then programmatically access each organization's containers using the `prefix` option in the API documentation.
This solution works fine, but I need to find a way to break down the costs for each organization's set of containers so that they know how much they owe. Is there a way for me to estimate the costs specifically for all the containers with the `a-` prefix or something similar? Given the circumstances, a dedicated Blob Storage instance would be ideal, but that seems off the table right now. Thanks for any guidance!
2 Answers
You can’t directly check container properties for size, unfortunately. The best approach is to enable blob inventory; it generates a CSV report in another container. Then you can run SQL queries on that data with Synapse or something similar to create a cost report based on the files' sizes and their hot or cool statuses. Just remember, this method won’t account for transfer costs, only storage.
Honestly, this situation screams for two separate storage accounts. Mixing data from different organizations in one storage account can lead to data protection issues, and the organizations might not like their data being so close to another company's data. It’s worth pushing for separate accounts to maintain best practices.
Couldn’t agree more, but I mentioned this idea to them and it fell on deaf ears. The data isn't particularly sensitive, and both organizations are under the same parent company I work for. Org B is hesitant to get a separate account since they know we’re already using one for Org A. Just a frustrating situation all around!