You're a great admin... on-prem. Now, become a great admin in the cloud and prove it by passing the Microsoft Certified: Azure Administrator Associate exam!
Gauge your current knowledge
Gauge your current knowledge
Azure Storage access tiers let you balance cost and performance based on how often you use your data. For Azure Blob Storage, the tiers are hot, cool, cold, and archive. The hot tier costs more to store but less to access, so it fits data you read or write often. The cool and cold tiers lower storage costs for data you access less frequently, but they charge more when you do access it. The archive tier is offline—it has the lowest storage cost but the highest retrieval cost and latency. For Azure Files, standard tiers (transaction optimized, hot, and cool) run on standard hardware and differ by transaction and storage pricing, while a premium tier uses SSDs for high-throughput workloads.
When you create a storage account, you set a default access tier that applies to all blobs or file shares unless you override it at upload time. For blobs, you can explicitly set the tier during upload using tools like Azure Portal, PowerShell, Azure CLI, or AzCopy. For example, the --tier Archive flag in Azure CLI places a blob directly into archive. For Azure Files, you choose the tier when creating the share; transaction optimized is recommended for initial migrations because those shares handle high transaction activity well.
To move data between tiers, use the Set Blob Tier operation to go to a cooler tier or the Copy Blob operation to rehydrate from archive back to an online tier. Azure Blob Storage lifecycle management automates these transitions with rules written in JSON—for instance, a policy can archive blobs not accessed in 90 days. Azure Files also supports moving standard shares between tiers, but each move incurs transaction costs, so only change tiers when usage patterns shift significantly. For bulk operations, you can script tier changes with Azure PowerShell (Set-AzStorageBlobTier) or Azure CLI (az storage blob set-tier).
To minimize costs, upload data directly to the most cost-effective tier rather than changing it later, because each transition adds transaction fees. Use lifecycle policies to automatically move data to cooler tiers as it ages. Be aware of early deletion penalties: data in cool, cold, or archive tiers must stay for a minimum of 30, 90, or 180 days, respectively, or you pay a prorated charge. For Azure Files, choose the standard tier based on the balance of transaction volume and storage size, with the cool tier often being cost-effective for shares that are rarely accessed.
Azure Blob Storage provides four tiers: Hot, Cool, Cold, and Archive. Each is designed for a different access pattern and has a distinct cost profile.
The Hot tier has the highest storage cost but the lowest access and transaction costs. Use it for active data that is read and written frequently, such as data being prepared for processing.
The Cool tier lowers storage costs but raises access costs. Data stored here must remain for a minimum of 30 days. It suits short-term backups or older datasets that are infrequently accessed but still need quick availability.
The Cold tier offers even lower storage costs and higher access costs than Cool. Data must stay for at least 90 days. It is best for long-term backups or compliance data that is rarely accessed but must be retrievable quickly when needed.
The Archive tier has the lowest storage costs and the highest access costs. Data must remain for 180 days. It is ideal for long-term archival or legal data that is rarely accessed and can tolerate hours of retrieval latency.
When choosing a tier, estimate how often data will be read and written, then analyze actual usage with Azure Monitor. Implement lifecycle management policies to automatically move data to the appropriate tier as patterns change. The trade-off is clear: cooler tiers save on storage but cost more to access and have longer minimum retention periods.
Selecting a storage tier affects pricing, latency, access frequency, and data retention. For Azure Blob Storage, the Hot tier gives the lowest transaction costs for frequent access, while Cool, Cold, and Archive progressively lower storage prices but increase access fees. Changing tiers later adds write costs and potential retrieval fees, so choosing the correct tier up front is important.
For Azure Files, the choice between Premium (SSD-based, high throughput, low latency) and Standard (HDD-based, cost-effective) depends on workload performance needs. Within Standard, you pick between Transaction Optimized, Hot, and Cool tiers, balancing capacity and transaction costs.
Lifecycle Management policies automate moving blobs to cooler storage as they age. However, data retention requirements impose minimum storage durations: 30 days for Cool, 90 days for Cold, and 180 days for Archive. Deleting or moving data before those periods ends triggers an early deletion penalty—a prorated charge for the remaining days.
Performance is affected by the physical distance between client and storage region and the tier’s latency. Online tiers (Hot, Cool, Cold) provide millisecond access, but the Archive tier requires a rehydration process that can take up to 15 hours. To optimize costs during rehydration, use Standard-priority rehydration for non-urgent data to avoid high-priority surcharges. Pack small files into TAR or ZIP archives to reduce the number of transactions. Monitor Storage Insights to detect underutilized accounts and adjust tiers accordingly.
StudyCerts
StudyCerts