This chapter covers Azure Blob Storage access tiers—Hot, Cool, Cold, and Archive—which are fundamental to cost optimization in Azure. For the AZ-104 exam, this topic appears in roughly 10-15% of storage-related questions, often in the context of lifecycle management, cost reduction, and performance tuning. Understanding the precise differences between tiers, their cost structures, and how to automate tier transitions is critical for passing the exam and for real-world Azure administration. We will dissect each tier's characteristics, default settings, rehydration times, and the exact commands to manage them.
Jump to a section
Think of Azure Blob Storage access tiers like a logistics warehouse with three storage zones: Hot, Cool, and Archive.
Hot tier is like a shelf right next to the shipping dock. Items here are immediately accessible; you can grab them in milliseconds. But shelf space is expensive because it's prime real estate. This is where you keep frequently accessed data—like daily sales reports. The cost to store is high, but retrieval is cheap and instant.
Cool tier is like a back-room shelf. Items are still accessible, but it takes a few extra seconds to walk to the back and retrieve them. The storage cost is lower because it's less convenient, but you pay a small penalty each time you retrieve an item (like a restocking fee). This is for data accessed infrequently—maybe once a month, like quarterly tax documents.
Archive tier is like a deep underground vault. Items are stored in sealed boxes. To get anything out, you must submit a retrieval request, wait hours (or even a day) for the box to be located and brought up, and then pay a significant retrieval fee. Storage is extremely cheap, but access is slow and costly. This is for data you must keep for years—like legal records or old backups—but almost never need.
Just like in a warehouse, you decide where to place each item based on how often you need it. Azure automatically moves blobs between tiers based on lifecycle policies, similar to a warehouse manager rotating stock from the dock to the back room when it hasn't been touched in 30 days. The key trade-off is always: storage cost versus access cost and latency.
What Are Azure Blob Storage Access Tiers?
Azure Blob Storage access tiers are pricing tiers that allow you to optimize storage costs based on data access frequency. There are four tiers: Hot, Cool, Cold, and Archive. Each tier has different storage costs, access costs, and latency characteristics. Blobs in the Hot tier have the highest storage cost but lowest access cost and latency (milliseconds). Cool and Cold tiers have lower storage costs but higher access costs and slightly higher latency (still milliseconds for reads, but with early deletion penalties). Archive tier has the lowest storage cost but requires manual rehydration (taking hours) before data can be read.
Why Access Tiers Exist
The primary purpose is cost optimization. Storing rarely accessed data in Hot tier wastes money. By moving data to cooler tiers, you reduce storage costs but accept higher access charges and potential latency. For compliance or retention, you might keep data in Archive for years at minimal cost.
How Access Tiers Work Internally
When you upload a blob, you specify its access tier (default is Hot for general-purpose v2 storage accounts). Azure stores the blob in a physical storage infrastructure optimized for that tier. For Hot, the data is on fast SSDs or high-performance HDDs with replication. For Cool/Cold, it might be on lower-cost HDDs with slightly slower access. For Archive, data is stored in a separate, low-cost storage system (often tape-based or very slow HDD) and is offline; you cannot read it directly until you initiate a rehydration operation that moves it back to Hot or Cool tier.
Key Components: Defaults, Timers, and Values
Default tier: For GPv2 and BlobStorage accounts, the default access tier is Hot. For BlockBlobStorage accounts, default is Hot. You can set the default at the storage account level, which applies to new blobs unless overridden.
Tier changes: You can change a blob's tier manually or automatically via lifecycle management. Changing from Hot to Cool/Cold/Archive is immediate (no rehydration). Changing from Cool/Cold/Archive to Hot requires rehydration (moving data to Hot tier). For Archive, rehydration can take up to 15 hours (Standard priority) or 1 hour (High priority).
Early deletion penalty: For Cool tier, if you delete or move blobs before 30 days, you incur an early deletion charge equal to the storage cost for the remaining days. For Cold tier, the minimum retention is 90 days. For Archive, it's 180 days. Hot tier has no minimum.
Access costs: Read operations in Hot are cheapest; writes are also cheap. Cool has higher read/write costs. Cold has even higher. Archive has no read/write costs because data is offline; you only pay for rehydration (data retrieval) and read operations after rehydration.
Rehydration priority: Standard (takes 1-15 hours) or High (takes under 1 hour, but costs more).
Lifecycle management: You define rules using the Azure portal, PowerShell, CLI, or ARM templates. Rules can move blobs between tiers, delete blobs, or take snapshots. Example: Move blobs to Cool if not modified for 30 days, to Archive after 90 days, delete after 365 days.
Configuration and Verification Commands
Azure CLI
Set default access tier at storage account level:
az storage account update --name mystorageaccount --resource-group myrg --access-tier CoolUpload a blob with specific tier:
az storage blob upload --account-name mystorageaccount --container-name mycontainer --name myblob --file myfile.txt --tier HotChange blob tier:
az storage blob set-tier --account-name mystorageaccount --container-name mycontainer --name myblob --tier ArchiveRehydrate from Archive:
az storage blob set-tier --account-name mystorageaccount --container-name mycontainer --name myblob --tier Cool --rehydrate-priority HighList blobs with tier:
az storage blob list --account-name mystorageaccount --container-name mycontainer --query "[].{name:name, tier:properties.blobTier}"PowerShell
Set default tier:
Set-AzStorageAccount -ResourceGroupName myrg -Name mystorageaccount -AccessTier CoolUpload blob:
Set-AzStorageBlobContent -Container mycontainer -File myfile.txt -Blob myblob -StandardBlobTier Hot -Context $ctxSet tier:
Set-AzStorageBlobTier -Container mycontainer -Blob myblob -StandardBlobTier Archive -Context $ctxRehydrate:
Set-AzStorageBlobTier -Container mycontainer -Blob myblob -StandardBlobTier Cool -RehydratePriority High -Context $ctxVerification: Use Azure portal: navigate to storage account > Containers > select blob > Properties > Access tier. Or use CLI/PowerShell to query tier property.
How Access Tiers Interact with Related Technologies
Azure Backup: Backup data is stored in the vault's storage. You can change the backup tier (e.g., from Hot to Cool) to reduce costs. Backup policies can include tiering rules.
Azure Data Lake Storage Gen2: Uses blob storage under the hood, so access tiers apply to Data Lake files. However, hierarchical namespace does not affect tiering.
Azure CDN: CDN caches content from blob storage; the access tier of the source blob doesn't affect CDN performance, but the origin fetch cost depends on the tier.
Azure Storage Lifecycle Management: This is the primary automation tool. You can create rules that filter by blob type, prefix, or blob index tags. Action can be: move to Cool, move to Archive, delete, or take snapshot.
Immutable Blob Storage: Even immutable blobs can be tiered, but the retention policy remains. Deleting before retention expires is not allowed, but tier changes are allowed unless the policy prevents it (e.g., legal hold).
Performance Considerations
Latency: Hot and Cool have similar latency for first-byte read (typically under 10 ms for a blob in the same region). Archive has no direct read; you must rehydrate first, which takes hours.
Throughput: Hot tier supports higher throughput limits per storage account. Cool and Cold have lower limits. For example, a GPv2 account in Hot tier can achieve up to 20,000 IOPS (for block blobs) vs lower for Cool.
Cost: Always evaluate the total cost: storage + access (read/write) + data transfer + early deletion. Use the Azure Pricing Calculator.
Common Misconfigurations
Setting default tier to Archive: New blobs are uploaded to Archive, but they cannot be read immediately. This is rarely desired for active data.
Not accounting for early deletion: Moving blobs from Cool to Hot within 30 days incurs early deletion penalty. Similarly for Cold (90 days) and Archive (180 days).
Rehydrating with Standard priority for urgent data: Standard can take up to 15 hours, which may cause application timeouts. Use High priority when data is needed quickly.
Forgetting to set rehydration priority: Default is Standard. If you need faster access, explicitly set High.
Exam Relevance
On AZ-104, you will be asked to recommend a tier based on access patterns, calculate cost implications, and configure lifecycle management rules. Know the exact numbers: 30 days for Cool, 90 for Cold, 180 for Archive. Know that Archive is offline and requires rehydration. Understand that you can set default tier at account level or per blob.
Identify Access Pattern
Determine how frequently data is accessed. For example, data accessed multiple times per day should be Hot. Data accessed once a month or less is Cool. Data accessed once a year or never is Archive. Also consider latency requirements: if sub-second access is needed, Hot or Cool; if hours of delay is acceptable, Archive. This step is crucial because choosing the wrong tier leads to unnecessary costs or poor performance.
Create Storage Account with Default Tier
In Azure portal, when creating a storage account (GPv2 or BlobStorage), you can set the default access tier to Hot or Cool. Archive cannot be default because new blobs must be accessible. For existing accounts, you can change the default tier using the 'Configuration' blade. This default applies to all new blobs unless overridden at upload time.
Upload Blobs with Specific Tier
When uploading blobs via portal, CLI, PowerShell, or SDK, you can specify the tier. For example, using Azure CLI: `az storage blob upload --tier Cool`. If not specified, the account default is used. You can also change the tier after upload using `set-tier` command. The tier change is immediate for Hot/Cool/Cold/Archive (except rehydration from Archive).
Configure Lifecycle Management Rules
In the storage account, go to 'Lifecycle management' and add a rule. Define a filter (e.g., by blob type, prefix, or tag). Then add actions: e.g., 'Move to Cool' after 30 days, 'Move to Archive' after 90 days, 'Delete' after 365 days. The rule runs once per day. You can also add actions for snapshots. This automates tier transitions without manual intervention.
Monitor and Optimize
Use Azure Monitor and Storage Insights to track blob access patterns. Check metrics like Blob Count, Blob Capacity, and Transaction counts per tier. If you see many reads from Archive, consider moving those blobs to a cooler tier? Actually, if blobs are frequently read from Archive, rehydrate them to Hot/Cool and adjust lifecycle rules. Also review early deletion charges to avoid surprises.
Scenario 1: Healthcare Compliance Data A hospital stores patient records for 7 years as required by law. The data is accessed rarely (maybe once a year for audits). - Problem: Storing in Hot tier is expensive. - Solution: Use lifecycle management to move blobs to Cool after 30 days, then to Archive after 90 days. The Archive tier costs ~$0.002 per GB/month vs Hot at ~$0.018. Over 7 years, this saves thousands of dollars. - Configuration: Create a lifecycle rule: filter by container 'patient-records', action: move to Cool after 30 days from creation, move to Archive after 90 days. - Considerations: If an audit requires immediate access, rehydrate with High priority (costs more but faster). Ensure the storage account is in the same region as the application to minimize data transfer costs. - Common mistake: Not setting the correct minimum retention period. If blobs are moved to Archive before 180 days, early deletion charges apply. But since they are kept for years, this is fine.
Scenario 2: Media Streaming Platform A video streaming service stores user-uploaded videos. New videos are accessed frequently for the first week (Hot), then rarely after that (Cool). Old videos may be kept for archival purposes (Archive). - Problem: Manual tiering is impractical at scale. - Solution: Use lifecycle management with blob index tags. Tag videos with 'category: new', 'category: standard', 'category: archive'. Rules can move based on tags and age. - Configuration: Rule 1: For blobs with tag 'category: new', move to Cool after 7 days from creation. Rule 2: For blobs with tag 'category: standard', move to Archive after 90 days. - Performance: Rehydration from Archive for an old video might take hours, so the application must handle this gracefully (e.g., show a 'processing' message). - What goes wrong: If a video is accessed after being archived, the user experiences delay. To mitigate, either rehydrate proactively or keep popular old videos in Cool.
Scenario 3: Backup and Disaster Recovery A company uses Azure Backup to back up on-premises servers. Backup data is stored in a Recovery Services vault, which uses blob storage behind the scenes. - Problem: Backup data grows quickly; storing all in Hot is costly. - Solution: Configure backup policy to use 'Cool' tier for monthly or yearly backups. Azure Backup allows tiering for long-term retention points. - Configuration: In backup policy, set 'Instant Restore' tier for daily backups (Hot) and 'Cool' tier for weekly/monthly backups. - Considerations: Restoring from Cool tier may take longer and incur higher costs per restore. Ensure SLAs are met. - Common mistake: Not understanding that backup tiering is separate from blob tiering; backup policies have their own tiering options. But underlying storage still uses blob tiers.
What AZ-104 Tests - Objective 2.1: Implement and manage storage accounts. This includes configuring access tiers. - Specific areas:
Differences between Hot, Cool, Cold, and Archive tiers (cost, latency, minimum retention).
How to change a blob's tier manually and via lifecycle management.
Rehydration process and priority options.
When to use each tier based on access patterns.
Early deletion penalties: 30 days for Cool, 90 for Cold, 180 for Archive.
Default tier setting at account vs blob level.
Common Wrong Answers 1. "Archive tier provides read access within minutes." Wrong: Archive requires rehydration which takes hours (up to 15 for Standard, 1 for High). Candidates confuse Archive with Cool/Cold. 2. "Changing from Cool to Hot incurs early deletion penalty." Wrong: Early deletion applies only when moving *out* of Cool (or Cold/Archive) before the minimum retention period. Moving *to* Hot does not incur penalty; the penalty is on the source tier if you delete/move before 30 days. 3. "You can set default tier to Archive." Wrong: Archive cannot be default because blobs must be accessible upon creation. The default can only be Hot or Cool. 4. "Lifecycle management runs continuously." Wrong: It runs once per day. Changes may take up to 24 hours to apply.
Specific Numbers to Memorize - Cool minimum retention: 30 days - Cold minimum retention: 90 days - Archive minimum retention: 180 days - Rehydration Standard: up to 15 hours - Rehydration High: under 1 hour - Lifecycle management evaluation: once per day
Edge Cases - Immutable blobs: Can be tiered, but cannot be deleted before retention period. Early deletion penalty still applies if you move them out of a tier before minimum days? Actually, moving to a different tier is allowed; early deletion penalty applies only if you *delete* or *move out* of the tier before minimum days. But moving from Cool to Archive after 10 days incurs early deletion penalty because you are moving out of Cool before 30 days. - Snapshots: Lifecycle management can also apply to snapshots. You can delete snapshots older than X days. - Blob index tags: Can be used in lifecycle rules to filter blobs. Tags are not automatically updated; you must manage them.
How to Eliminate Wrong Answers - If a question mentions "immediate read access" for Archive, it's wrong. - If a question says "no additional cost" for tier change, check if early deletion applies. - If a question asks for lowest storage cost, Archive is cheapest, but remember the rehydration cost. - Always consider the access frequency and latency requirements.
Access tiers: Hot, Cool, Cold, Archive. Each has different storage cost, access cost, and latency.
Default tier for GPv2 accounts is Hot. Can be changed to Cool, but not to Archive.
Minimum retention periods: Cool = 30 days, Cold = 90 days, Archive = 180 days. Early deletion incurs prorated charge.
Archive tier is offline; blobs must be rehydrated to Hot or Cool before reading. Rehydration takes up to 15 hours (Standard) or 1 hour (High).
Lifecycle management automates tier transitions. Rules run once per day. Use filters by blob type, prefix, or index tags.
Changing tier from Hot to Cool/Cold/Archive is immediate. Reverse (from Cool to Hot) is immediate unless from Archive, which requires rehydration.
Blob tier can be set at upload or changed later. Use Azure CLI `az storage blob set-tier` or PowerShell `Set-AzStorageBlobTier`.
To move blobs from Archive to Hot, use `set-tier` with `--rehydrate-priority High` for faster access (costs more).
Lifecycle rules can also apply to snapshots (e.g., delete snapshots older than 30 days).
Monitor blob access patterns using Storage Insights to optimize tier selection and avoid unnecessary costs.
Immutable blobs can be tiered, but retention policies still apply. Legal hold prevents tier changes? Actually, legal hold does not prevent tier changes, but deletion is blocked.
Azure Backup uses tiering for long-term retention points; backup tiering is separate from blob tiering but uses similar concepts.
These come up on the exam all the time. Here's how to tell them apart.
Hot Tier
Highest storage cost (~$0.018/GB/month for LRS)
Lowest access cost (read: $0.0004/10k, write: $0.005/10k)
No minimum retention period
Sub-millisecond latency for first byte
Best for data accessed frequently (multiple times per day)
Cool Tier
Lower storage cost (~$0.01/GB/month for LRS)
Higher access cost (read: $0.001/10k, write: $0.01/10k)
Minimum retention: 30 days (early deletion penalty applies)
Similar latency to Hot (milliseconds)
Best for data accessed infrequently (once a month or less)
Cool Tier
Storage cost: ~$0.01/GB/month
Minimum retention: 30 days
Access cost: read $0.001/10k, write $0.01/10k
Designed for data accessed less than once a month
Early deletion penalty: 30-day prorated charge
Cold Tier
Storage cost: ~$0.0045/GB/month (lower than Cool)
Minimum retention: 90 days
Access cost: read $0.002/10k, write $0.02/10k (higher than Cool)
Designed for data accessed less than once a quarter
Early deletion penalty: 90-day prorated charge
Archive Tier
Lowest storage cost (~$0.002/GB/month)
No direct read access; requires rehydration (hours)
Minimum retention: 180 days
Rehydration cost: $0.01/GB for Standard, $0.05/GB for High
Best for long-term retention (years) with rare access
Cool Tier
Higher storage cost (~$0.01/GB/month)
Direct read access (milliseconds)
Minimum retention: 30 days
No rehydration needed; read cost is $0.001/10k
Best for data accessed monthly
Mistake
Archive tier allows direct read access with higher latency.
Correct
Archive is offline; you cannot read data directly. You must first rehydrate the blob to Hot or Cool tier, which takes hours. Only then can you read it.
Mistake
Changing a blob's tier from Cool to Hot incurs an early deletion penalty.
Correct
Early deletion penalty applies only when you delete or move blobs out of Cool (or Cold/Archive) before the minimum retention period (30 days for Cool). Moving from Cool to Hot is allowed without penalty, but if the blob has been in Cool for less than 30 days, you will be charged for the remaining days.
Mistake
Lifecycle management rules are applied immediately after creation.
Correct
Lifecycle management runs once per day. After creating a rule, it may take up to 24 hours for the first evaluation and action to occur.
Mistake
You can set the default access tier to Archive for a storage account.
Correct
The default access tier can only be Hot or Cool. Archive cannot be default because blobs must be accessible immediately upon creation.
Mistake
Cold tier is the same as Cool tier but with a different name.
Correct
Cold tier is a separate tier introduced after Cool. It has lower storage cost than Cool but higher access costs and a minimum retention of 90 days (vs 30 for Cool). It is designed for data that is accessed less than once per quarter.
Reveal each answer, then mark whether you got it right. Score 60%+ to unlock the next chapter.
Cold tier is a newer tier with lower storage cost but higher access costs and a longer minimum retention period (90 days) compared to Cool (30 days). Cold is designed for data accessed less than once a quarter, while Cool is for data accessed less than once a month. Both offer milliseconds latency, but Cold has higher read/write charges. On the exam, know that Cold is cheaper to store but more expensive to access, and has a 90-day minimum.
Rehydration from Archive can take up to 15 hours with Standard priority or under 1 hour with High priority. High priority costs more. You specify priority when initiating rehydration via CLI, PowerShell, or portal. The blob becomes readable only after rehydration is complete and the tier changes to Hot or Cool.
Yes, you can change the default access tier for a general-purpose v2 or BlobStorage account in the 'Configuration' blade of the storage account. The new default applies to all new blobs uploaded after the change. Existing blobs are not affected. The default can be set to Hot or Cool, not Archive.
You will incur an early deletion penalty equal to the storage cost for the remaining days (prorated). For example, if you delete a blob after 10 days in Cool, you pay for the remaining 20 days of storage. The same applies to Cold (90 days) and Archive (180 days). Hot has no early deletion penalty.
Yes, lifecycle management can apply to blobs in Archive. For example, you can have a rule that deletes blobs after 365 days, even if they are in Archive. However, you cannot move blobs from Archive to a lower tier via lifecycle management; you must manually rehydrate first. Lifecycle management can move blobs from Hot to Cool to Archive, but not from Archive to Hot.
Yes, you can use blob index tags as filters in lifecycle management rules. For example, you can create a rule that moves blobs with tag 'category=archive' to Archive after 30 days. Tags are key-value pairs that you assign to blobs. This allows fine-grained control over which blobs are tiered.
Changing a blob's tier (e.g., from Hot to Cool) does not incur a direct cost for the operation itself, but you may incur early deletion charges if moving out of a tier before the minimum retention period. Additionally, reading data after rehydration from Archive incurs data retrieval costs. The write operation to change tier is free.
You've just covered Azure Blob Storage Access Tiers — now see how well it sticks with free AZ-104 practice questions. Full explanations included, no account needed.
Done with this chapter?