Azure Blob Storage — Trivia & Quick Facts¶
Terse, quiz-worthy facts about Azure Blob Storage — specific numbers, limits, and defaults worth memorizing.
- Storage account names are globally unique, 3-24 characters, lowercase letters and digits only.
- A general-purpose v2 (
StorageV2) account is the normal default for most Blob workloads. - Blob types are block, append, and page blobs.
- Standard online tiers are Hot, Cool, and Cold; Archive is offline.
- GPv2 minimum-duration charging is generally 30 days for Cool, 90 for Cold, and 180 for Archive.
- Archive rehydration can take up to 15 hours at standard priority.
- Redundancy is selected at the storage-account level and is shared by every service in that account.
- GRS/GZRS replication to the secondary region is asynchronous — it is not a zero-data-loss guarantee.
- Azure RBAC
Contributordoes not inherently grant Blob data access — a separate data-plane role is required. - Microsoft recommends Entra ID authorization and disabling Shared Key where dependencies permit.
- SAS tokens can be used without exposing the account key, but overly broad/long-lived SAS is still a bearer credential risk.
- Hierarchical namespace enables real directories and ACLs and cannot be reverted to flat namespace once enabled.
- Lifecycle management can tier or delete supported blobs but cannot rehydrate archived blobs.
- Blob soft delete and versioning both preserve billable data copies.
- Without HNS, blob-name slashes represent virtual folders, not atomic directories — "renaming" one can mean copying and deleting many objects.