2.1AZ-104Intermediate
Est: ~15 mins•Verified: 2026-08

Storage Accounts: Blob Access Tiers & Lifecycle

Deploy and optimize Azure Storage accounts, configure Hot/Cool/Cold/Archive tiers, automated lifecycle management rules, and immutable blob storage.

Tags:#Azure Storage#Blob#Lifecycle Management#Archive#Cost Optimization#AZ-104
01

Overview

Azure Blob Storage is Microsoft's massively scalable object storage solution for unstructured data. Optimizing storage performance and cost requires mastering Blob Access Tiers:

  1. Hot Tier: Optimized for data that is in active, frequent use. Lowest access cost; highest storage cost.
  2. Cool Tier: Optimized for data that is infrequently accessed and stored for at least 30 days. Lower storage cost; higher access cost.
  3. Cold Tier: Optimized for infrequently accessed data stored for at least 90 days.
  4. Archive Tier: Offline tier for data stored for at least 180 days (backups, legal records). Lowest storage cost; highest retrieval cost. Rehydration takes up to 15 hours (or under 1 hour with High Priority).

Lifecycle Management Rules automate tier transitions and deletions based on file age or last modified date.

---

02

When to Use: Tier Cost Trade-off Matrix

Access TierMin Retention PeriodData Access LatencyBest Used For
HotNoneMillisecondsActive web assets, daily working files.
Cool30 daysMillisecondsShort-term backups, raw telemetry logs accessed monthly.
Cold90 daysMillisecondsQuarterly reports, secondary disaster recovery replicas.
Archive180 daysHours (Offline rehydration)Compliance archives, legal evidence, long-term regulatory logs.

---

03

Prerequisites

Azure Resources:

  • General-purpose v2 (standard) storage account or Blob storage account.
  • Contributor or Storage Blob Data Owner permissions.

---

04

Portal Path

TEXT
Azure Portal (https://portal.azure.com)
└── Storage accounts > [Target Storage Account]
    └── Data management
        ├── Containers (Create containers, set public access level)
        └── Lifecycle management (Add automated tiering & deletion rules)

---

05

Step-by-Step Implementation

Step 1: Configure Automated Lifecycle Management Rule

  1. In the Azure portal, navigate to your storage account.
  2. Under Data management, select Lifecycle management > Click Add a rule.
  3. Rule name: Archive-After-30-Delete-After-365.
  4. Rule scope: Apply rule to all blobs in the storage account.
  5. Blob type: Check Block blobs > Base blobs.
  6. Configure rules:
  • If base blobs were Last modified more than 30 days ago > Move to Cool storage.
  • If base blobs were Last modified more than 90 days ago > Move to Archive storage.
  • If base blobs were Last modified more than 365 days ago > Delete the blob.
  1. Click Add to save.

---

06

PowerShell Automation

Create Lifecycle Management Policy via Azure PowerShell:

PowerShell
# Define lifecycle rule action
$Action = Add-AzStorageAccountManagementPolicyAction -BaseBlobAction TierToCool -daysAfterModificationGreaterThan 30 `
    | Add-AzStorageAccountManagementPolicyAction -BaseBlobAction TierToArchive -daysAfterModificationGreaterThan 90 `
    | Add-AzStorageAccountManagementPolicyAction -BaseBlobAction Delete -daysAfterModificationGreaterThan 365

# Create rule filter
$Filter = New-AzStorageAccountManagementPolicyFilter -PrefixMatch @("logs/", "backups/") -BlobType blockBlob

# Compile rule and apply to storage account
$Rule = New-AzStorageAccountManagementPolicyRule -Name "AutoArchiveRule" -Action $Action -Filter $Filter
Set-AzStorageAccountManagementPolicy -ResourceGroupName "rg-data" -StorageAccountName "storproduction001" -Rule $Rule

---

07

Verification Checklist

VERIFICATION CHECKLIST
0/4 (0%)
Lifecycle management rule displays active status in storage account.
Blobs older than 30 days automatically shift access tier from Hot to Cool.
Blobs in Archive tier display status Archive and cannot be read without rehydration.
Deletion rules successfully purge files exceeding 365 days.
08

Troubleshooting Matrix

Error Code / SymptomRoot CauseExact Resolution
Early Deletion Penalty FeeBlob moved to Cool and deleted before 30 days, or Archive before 180 days.Adhere to minimum retention durations before deleting or re-tiering blobs.
Cannot download Archived blobArchive tier is offline storage. Blob must be rehydrated to Hot/Cool first.Initiate Rehydrate blob action in Azure portal; select Standard or High Priority.

---

09

AZ-104 Exam Notes

Exam Blueprint & High-Yield Traps

High-Frequency Exam Objectives & Traps:

  1. Early Deletion: Cool has a 30-day minimum, Cold has 90-day, and Archive has 180-day minimum. Deleting or changing tier before this period incurs a pro-rated early deletion fee.
  2. Archive Rehydration: Archive blobs cannot be read directly by applications. You must rehydrate them to Hot or Cool first.
  3. Hierarchical Namespace: Enabling Data Lake Gen2 (Hierarchical Namespace) allows directory-level ACLs.

---

10

Official Documentation

PREVIOUS TOPIC1.2 Azure Governance: Management Groups, Azure Policy & Resource LocksNEXT TOPIC2.2 Azure Files, Azure File Sync & Storage Private Endpoints