Azure Storage Accounts and Blob Storage: Redundancy, Access Tiers, Lifecycle, Data Lake and Static Websites

Microsoft Azure Architect Technologies AZ 300 60 min min read Updated: Nov 17, 2026 Beginner
Azure Storage Accounts and Blob Storage: Redundancy, Access Tiers, Lifecycle, Data Lake and Static Websites
Beginner Topic 1 of 3

Storage Account Services

ServiceUse
Blob StorageObjects: images, backups, logs, data lakes
Azure FilesManaged SMB and NFS file shares
Queue StorageSimple message queue
Table StorageSimple NoSQL key-value (Cosmos DB for Table is the premium option)
Managed disksVM disks (separate resource type)
  • Use Standard general-purpose v2 for most needs. Premium accounts use SSD for low latency (block blobs, file shares, page blobs)
  • The account name is globally unique, 3 to 24 lowercase letters and numbers
  • Endpoints look like https://stshopprod.blob.core.windows.net

Redundancy Options

OptionCopiesProtects against
LRS (locally redundant)3 copies in one datacenterDisk and rack failure
ZRS (zone-redundant)3 copies across 3 zones in one regionDatacenter (zone) failure
GRS (geo-redundant)LRS in primary + LRS in a paired regionRegional disaster (data available after Microsoft or customer failover)
RA-GRSGRS plus read access to the secondaryRead during regional outage
GZRSZRS in primary + LRS in the secondary regionZone and region failure
RA-GZRSGZRS plus read access to secondaryHighest durability and availability
Remember Geo replication is asynchronous, so recent writes may be lost in a regional disaster (RPO is not zero). ZRS is synchronous inside the region.
bash az storage account create -g rg-data -n stshopprod482 -l centralindia --sku Standard_ZRS --kind StorageV2 \ --min-tls-version TLS1_2 --allow-blob-public-access false --https-only true az storage container create --account-name stshopprod482 -n reports --auth-mode login az storage blob upload --account-name stshopprod482 -c reports -n 2026/report.pdf -f report.pdf --auth-mode logi

Access Tiers

TierForNotes
HotFrequent accessHighest storage cost, lowest access cost
CoolInfrequent, kept at least 30 daysLower storage cost
ColdRare, kept at least 90 daysLower again
ArchiveAlmost never, kept at least 180 daysCheapest, offline: rehydrate (hours) before reading
bash az storage blob set-tier --account-name stshopprod482 -c reports -n 2024/old.pdf --tier Archive --auth-mode login az storage blob set-tier --account-name stshopprod482 -c reports -n 2024/old.pdf --tier Hot --rehydrate-priority Standard --auth-mode logi

Lifecycle Management

json {"rules": [{ "name": "age-out", "enabled": true, "type": "Lifecycle", "definition": { "filters": {"blobTypes": ["blockBlob"], "prefixMatch": ["reports/"]}, "actions": {"baseBlob": { "tierToCool": {"daysAfterModificationGreaterThan": 30}, "tierToArchive": {"daysAfterModificationGreaterThan": 180}, "delete": {"daysAfterModificationGreaterThan": 2555}}}}}]}
bash az storage account management-policy create --account-name stshopprod482 -g rg-data --policy @policy.jso

Protecting Data

FeaturePurpose
Soft delete (blobs and containers)Recover deleted data for a retention period
VersioningKeep previous versions on overwrite
Point-in-time restoreRestore block blobs to an earlier time
Immutable storage (WORM)Time-based retention and legal hold for compliance
Resource locksStop account deletion
Object replicationCopy blobs asynchronously between accounts or regions
EncryptionAlways on with Microsoft-managed keys. Optional customer-managed keys in Key Vault
bash az storage account blob-service-properties update -n stshopprod482 -g rg-data --enable-delete-retention true --delete-retention-days 14 \ --enable-versioning true --enable-container-delete-retention true --container-delete-retention-days 14

Data Lake Storage Gen2

  • Turn on hierarchical namespace to get real folders, POSIX-style ACLs and fast directory operations for analytics (Synapse, Databricks, Fabric, Spark)
  • Same Blob account with analytics features. Decide before creating the account (it can be enabled by upgrade in some cases)

Static Website

bash az storage blob service-properties update --account-name stshopprod482 --static-website --index-document index.html --404-document 404.html --auth-mode login az storage blob upload-batch --account-name stshopprod482 -s ./site -d '$web' --auth-mode logi
  • For HTTPS on a custom domain and caching, put Azure Front Door or CDN in front

Practice

  1. Create a ZRS account with public access disabled
  2. Upload a file, change its tier to Cool and back
  3. Add a lifecycle rule and soft delete
  4. Choose a redundancy option for: dev files, regional-critical data, global compliance archive

Conclusion

Storage accounts provide Blob, Files, Queue and Table. Pick redundancy by failure you must survive (ZRS for zones, GZRS for regions), tier data by access frequency, automate with lifecycle rules and protect with soft delete, versioning and immutability.

Quick Summary: services; redundancy; tiers; lifecycle; protection; Data Lake; static website.

Get Newsletter

Subscibe to our newsletter and we will notify you about the newest updates on Edugators