Start here! Get your feet wet with the Microsoft cloud and begin your journey to earning your Microsoft Certified: Azure Fundamentals certification!
Gauge your current knowledge
Gauge your current knowledge
Azure offers storage tiers to optimize cost and performance for storing different types of data. Each tier represents a level of data accessibility and cost structure. By selecting the right tier, organizations can balance storage expenses against performance needs. Understanding tiers helps to manage data at scale. This approach ensures that frequently accessed data remains quickly available while infrequently accessed data is stored more cheaply.
The Hot tier is designed for data that you access frequently. It provides the lowest latency and the highest throughput, making it ideal for active workloads. Storage costs are higher in this tier, but access charges are minimal. You should use the Hot tier for scenarios like real-time analytics, live content streaming, and transactional data. This tier ensures that your most critical data is always instantly available.
The Cool tier offers a lower storage cost than Hot but charges more for data access. This tier suits infrequently accessed data that still needs to be retrieved occasionally. Typical use cases include backup data, long-term logs, and older media files. You can think of it as the middle ground between performance and cost. The Cool tier helps you save money when data isn't needed every day.
The Archive tier provides the lowest storage cost but has the highest latency for data retrieval. It is meant for long-term retention and compliance data that you rarely need to access. Retrieval can take hours, so it's best for data that can tolerate delays. This tier is perfect for compliance archives, raw scientific data, and historical records. By using Archive, you minimize storage bills for data that is essentially dormant.
When choosing a tier, consider your access patterns, data retrieval times, and budget constraints. Key factors include frequency of access, required retrieval speed, and total cost of storage versus access. Azure also allows you to transition data between tiers as needs change, ensuring ongoing cost efficiency.
Azure Blob Storage provides three main tiers—Hot, Cool, and Archive—to help organizations balance performance and cost. Each tier is designed with specific access patterns and pricing in mind. By understanding these tiers, teams can optimize costs while meeting their data retrieval needs. Choosing the right tier depends on how often data is accessed and how quickly it must be retrieved.
The Hot tier is optimized for frequent access and delivers the lowest access latency. It is ideal when you need to retrieve data quickly and often. Use cases include storing active documents and media files that users open daily, keeping logs and telemetry data that applications query in real time, and hosting images or videos on a website where performance is critical. While storage prices are higher in this tier, access costs are lower, making it cost-effective for heavy usage.
The Cool tier is designed for infrequently accessed data that still needs to be available in minutes. It suits scenarios where data is needed occasionally but not on a daily basis. Common use cases are backups of on-premises systems that are only restored during troubleshooting, historical analytics data that is queried a few times per quarter, and media content archives that might be accessed during specific events. This tier offers moderate storage costs and slightly higher access fees compared to Hot.
The Archive tier is meant for long-term retention of data that is rarely accessed and can tolerate hours of retrieval time. It provides the lowest storage cost but has the highest access latency. Typical uses include compliance and regulatory records that must be kept for years, legal documents or financial statements that are seldom reviewed, and scientific data sets that are preserved for future research. When selecting a tier, evaluate your access frequency, retrieval speed, and budget to ensure the best fit for your storage needs.
Azure Blob Storage offers three storage tiers—hot, cool, and archive—designed for different access patterns. The hot tier delivers the fastest access but at higher storage cost. The cool and archive tiers reduce storage prices but impose higher access and transaction charges. Choosing the right tier depends on balancing performance with budget.
Storage expenses vary by tier: the cooler the tier, the lower the per-gigabyte storage fee, but the data access costs and transaction costs rise. Key factors include storage costs billed per GB per month that decrease from hot to archive, data access costs billed per GB read that are higher for cool and archive, and transaction costs billed per 10,000 operations that increase in cooler tiers. Additional fees can affect total spending, such as geo-replication data transfer costs when you enable cross-region redundancy and outbound data transfer costs for data leaving an Azure region. Monitoring these charges helps avoid unexpected expenses in distributed or multi-region deployments.
Moving blobs between tiers incurs both charges and performance impacts. Changing a blob's tier is billed as either a write operation to the destination tier or a read operation from the source tier, plus any early deletion fees. The archive tier requires rehydration before access, which adds both time and cost. Planning tier changes carefully helps control costs and meet performance needs.
You can optimize costs with lifecycle management policies and reserved capacity. Lifecycle policies automatically transition data to cooler tiers based on rules like last modification dates. Reserved capacity offers discounted storage rates when you commit to a one- or three-year term. Regularly reviewing your data usage and tier placement ensures a balance of performance and cost.
Azure Storage provides multiple access tiers—Hot, Cool, Cold, and Archive—to balance performance and cost. The Hot tier is optimized for frequent reads with higher storage costs but low access fees. The Cool tier is for data accessed infrequently with a minimum 30-day retention and lower storage costs. The Cold tier (GPv2 only) has a minimum 90-day retention and even lower storage costs. The Archive tier is offline, has the lowest storage cost, and requires data to stay for at least 180 days.
When you create a storage account, you set a default blob tier, typically Hot or Cool. Data Box devices send data to the storage account's default tier, and you can change this setting later in the portal. After upload, you may move data from the default tier to another tier based on workload needs and cost considerations. General Purpose v1 accounts don't support tiering; only GPv2 and Blob storage accounts allow tier changes.
Azure Blob storage lifecycle management offers a policy-based approach to automate data tiering and expiration. Policies run on a schedule and evaluate access patterns and retention rules to move data. This automates transitions to lower-cost tiers and helps maintain compliance with data retention requirements. Alternatively, you can use Azure PowerShell and the SetBlobTier operation in scripts to tier blobs manually.
A lifecycle management policy consists of rules, each with filters and actions. Filters include prefixMatch to target specific containers or paths and blobIndexMatch to select blobs by index tags. Actions include moving blobs to Cool, Cold, or Archive tiers and deleting blobs at the end of their lifecycle. To define a rule, you specify conditions such as last modified days or last accessed days and link them to a tier transition or deletion.
Best practices for data lifecycle management emphasize choosing tiers based on access patterns and cost models. Regularly analyze containers using inventory reports and last access time tracking to inform policies. Pack small files into larger archives (e.g., TAR or ZIP) to reduce transaction costs. Always consider early deletion charges when moving blobs before their minimum retention periods.
Azure Storage access tiers such as Hot, Cool, Cold, and Archive let you choose the right blend of performance, cost, and data access. Each tier is optimized for different usage patterns and has minimum retention requirements. For instance, the Archive tier requires data to be stored for at least 180 days to avoid early deletion charges. Understanding the security features alongside these tiers helps maintain compliance and protect your data.
Access control is vital for securing blob data. Azure Storage supports Microsoft Entra ID authorization with role-based access control (Azure RBAC) to grant precise permissions, Shared Key authorization for legacy applications and SAS tokens for time-limited, scoped access, and Private endpoints and firewall rules to restrict network access. By combining these methods, you can ensure only authorized users and services can access your storage. You should plan permissions based on the least-privilege principle.
Encryption safeguards your data both at rest and in transit. By default, Azure uses Microsoft-managed keys to encrypt data at rest, and you can opt for customer-managed keys stored in Azure Key Vault for extra control. TLS encryption (with minimum TLS version 1.2) protects data in transit. These measures help meet security standards and regulatory compliance requirements.
To guard against accidental or malicious data loss, Azure provides data protection features that work across all tiers. The main tools include Soft delete that retains deleted blobs for a configurable period allowing restore within that time, Blob versioning that automatically preserves previous versions when a blob is overwritten, and Immutable storage that enforces write-once, read-many policies for compliance with regulations like SEC 17a-4. These features help you maintain data integrity and meet retention obligations.
Monitoring and auditing support compliance and security posture reviews. You can enable Logging and Metrics in Azure Monitor and configure Storage Analytics to track access and operations. Additionally, blob inventory reports and lifecycle management policies provide insight into data access patterns and ensure that data moves to the most cost-effective and secure tier. Regular reviews of these logs and reports help demonstrate compliance with organizational and regulatory standards.