Common Scenarios¶
Azure Storage is used in diverse scenarios across cloud applications. This section maps business requirements to the most effective storage services.
Scenario Mapping¶
| Scenario | Service | Key Consideration |
|---|---|---|
| App File Storage | Blobs | Use Hot tier for active files |
| Log/Backup | Blobs | Archive tier for long-term retention |
| Static Content | Blobs | CDN integration for low latency |
| Function Runtime | Azure Storage account | Uses Blob, Queue, Table; Azure Files for app code in some hosting plans |
| Lift-and-Shift | Files | AD integration for permissions |
| Big Data | Blob Storage with Data Lake Storage Gen2 | Hierarchical namespace for analytics |
Scenario Service Selection¶
mermaid graph LR Log[Log/Backup] --> Blob[Blob Storage] Static[Static Web] --> Blob Legacy[Legacy Apps] --> Files[Azure Files] Analytics[Big Data] --> ADLS[Data Lake Gen2] Messaging[Microservices] --> Queue[Queue Storage]
Implementation Advice¶
- Use lifecycle management policies to move data to cheaper tiers automatically.
- Enable soft delete to protect against accidental data loss.
- Utilize shared access signatures (SAS) to grant limited access to storage resources.
Tip
Start with one scenario as a baseline architecture, then iterate with security and performance controls from the Platform and Best Practices sections.