Blob storage for central control.
Use Cases and Deployment Scope
Pros
- Hosting large files.
- Vanity URLs.
- Temporary access.
- Different levels of access to files.
Cons
- Enumeration of folders is not possible.
- Spaces in file names can be problematic.

Ease of Use: Users have praised the AWS S3-compatible API for its intuitive interface, which simplifies tasks through features like drag and drop functionality, making data management more efficient and user-friendly. They find the seamless navigation and accessibility beneficial for various workflows.
Cost-Effectiveness: Reviewers appreciate the budget-friendly nature of both AWS S3-compatible API and Azure Blob Storage, highlighting their ability to provide reliable storage solutions at a reasonable cost without compromising quality. The affordability coupled with performance is a significant advantage stated by users.
Security Features: Customers value the comprehensive security measures offered by both services, including robust file encryption, secure data transfer protocols such as HTTPS, and versatile access control options like Shared Access Signatures. This level of security assurance plays a crucial role in their decision-making process.
Azure Blob storage is currently used in various ways at our company.
First, like cloud storage for various Azure SaaS platforms. Things like managed SQL instances and data lake storage for Azure AI / ML. It is useful in that it is tiered, so you can use hot tier for these use cases.
Secondly, a more common use is to use the cold and archive tiers as a cheap location to store long-term backups and archives. We think of it as a replacement for tape offloading in our DR strategy. One thing to be away from is that the cost to bring those backups/archives back from the cloud can be very high. So this is used more as a place of last resort for disaster recovery currently, but it definitely has its place.
Well suited for newly developed micro applications that need to access data in the cloud.
Well suited for being the storage layer for SaaS offerings within the Azure Service Catalog. The integration is usually built-in.
Well suited for backup storage target for long-term RPO objectives, when the expectation of actual retrieval need is very low.
Well suited for long-term offsite archival storage.
Well suited for emergency storage needs (burst storage) for an immediate need.
Not appropriate for data that has high amounts of ingress and egress churn.
Not appropriate for applications that require ultra-low latency response time from the storage layer.