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 provides storage tiers to help balance cost and performance based on how often you access your data. These tiers apply to General-purpose v2 storage accounts, which are recommended for the latest features and performance. Each tier has its own pricing model for storage capacity and data access, making it critical to choose the right tier for your workflow.
The Hot tier offers the lowest latency and highest throughput for frequently accessed data. It's ideal for scenarios like live streaming or video-on-demand, where you read data constantly. While storage prices are higher, the cost per read and write operation is lower compared to cooler tiers, ensuring smooth playback and quick access for end users.
The Cool tier provides lower storage costs for data accessed less often, such as source assets awaiting encoding or long-term archives. However, it comes with higher read and write operation costs, so it's best used when you don't plan to read data frequently. You can reduce overall expenses by moving infrequently accessed master or mezzanine files into this tier, though heavy read patterns can increase your monthly bill.
A common strategy uses separate storage accounts tuned for each tier: Standard_LRS for development or testing with local redundancy, and Standard_RAGRS for production with geo-redundancy. You might store master files in a Cool account to cut retention costs and output encoded streams into a Hot account for optimal streaming performance.
Azure storage accounts offer several data redundancy choices to protect against failures and disasters. These options help ensure durability of your data by keeping multiple copies and enhance availability by distributing those copies across locations. Selecting the right redundancy strategy is crucial for meeting recovery objectives and balancing costs.
Locally Redundant Storage (LRS) replicates your data three times within a single region. Zone-Redundant Storage (ZRS) also keeps three copies but spreads them across two or three availability zones in one region—or even across regions in some cases. Both options maintain three independent copies on separate nodes to protect against hardware failures, with LRS being the most cost-effective and ZRS offering higher resilience against zonal outages.
Geo-Redundant Storage (GRS) copies data to a secondary region hundreds of miles away, resulting in six total copies (three in the primary and three in the secondary). This provides regional disaster protection by keeping data far apart. Read-Access Geo-Redundant Storage (RA-GRS) adds read-only access to the secondary region, so you can read from backups even if the primary region is still operational.
When choosing among redundancy options, consider your application's criticality, budget, and recovery requirements. Critical workloads that need minimal downtime often use GRS or RA-GRS, while dev/test environments may opt for LRS. Remember that some redundancy settings cannot be changed after a storage account is created, so plan ahead. Key decision factors include durability (number of copies and geographic spread), availability (read-access and resilience to zone or region failures), cost (higher redundancy generally means higher pricing), and recovery objectives (targeted Recovery Point Objective and Recovery Time Objective).
Azure storage accounts provide unique namespaces for your data and come in several types: General Purpose v2, Blob Storage, and General Purpose v1. The General Purpose v2 account kind is recommended for most workloads, offering standard performance, flexible redundancy options like Zone Redundant Storage or RA-GRS, and features such as a hierarchical namespace for analytics. You can also choose default access tiers (Hot, Cool, Archive) and enable soft delete to protect data from accidental removal.
Azure Blob Storage is Microsoft's object storage solution for massive amounts of unstructured data like text or binary files. It supports streaming and random access, making it perfect for serving images, videos, and building enterprise data lakes. Blobs are accessible globally over HTTP/HTTPS via URLs, REST APIs, Azure SDKs, or protocols like NFS and SFTP. Azure Blob Storage also offers tiered access and lifecycle management rules to optimize costs based on data usage patterns.
Azure File Storage provides fully managed network file shares that you can mount via SMB, NFS, or REST APIs. This service is ideal for lift-and-shift scenarios where applications use native file system APIs, replacing or supplementing on-premises file servers and NAS devices. Multiple virtual machines across Windows, Linux, or macOS can share and access the same files, and you can generate shared access signatures to allow secure, time-limited access over a URL. Common uses include storing development tools, configuration files, logs, and crash dumps that need to be accessible from many VMs.
Queue Storage and Table Storage cover messaging and NoSQL data needs. Queue Storage allows asynchronous message queueing to decouple application components and improve resiliency. Table Storage offers a schemaless, key/attribute NoSQL store for flexible datasets like user profiles, metadata, or device information. These services are cost-effective and simple to operate, making them suitable for web-scale applications that don't require complex joins or relational schemas.
Beyond these core services, Azure provides specialized storage types for specific needs: Azure Disks for persistent VM-attached disks, Azure Elastic SAN for iSCSI-based SAN deployments, Azure NetApp Files for enterprise-grade NAS with SMB and NFS support, Azure Container Storage for dynamic Kubernetes persistent volumes, and Azure Managed Lustre for high-performance computing workloads. Each option addresses unique performance, protocol, and management considerations to fit diverse cloud scenarios.
Azure provides several security and management tools to protect and monitor your storage data. You can use Managed Identity or account access keys to authorize access, but it's best to avoid sharing storage account keys and treat them like passwords. Rotate keys regularly and store them securely in Azure Key Vault, and use Azure RBAC and SAS tokens for granular, time-limited access.
Storage Explorer settings let you disable usage of keys and enforce Azure RBAC for enhanced security. Azure storage offers two main access tiers to balance performance and cost: the Hot tier is optimized for frequent read/write operations and ideal for streaming live or on-demand video, while the Cool tier is designed for infrequently accessed data and long-term retention with lower storage costs but higher access fees. You can reduce long-term costs by moving master or mezzanine files to cool storage while keeping streaming assets in hot storage.
Choosing the right SKU affects data durability and business continuity. For testing, use Standard_LRS (locally redundant storage). For production environments, consider Standard_RAGRS (read-access geo-redundant storage) to protect against region failures. These options help you plan for cost management and service-level agreements.
Azure offers different storage account types to match various workload requirements. General-purpose v1 (GPv1) accounts offer basic storage features and billing models, while General-purpose v2 (GPv2) accounts provide the latest performance improvements and access tier capabilities. You can use features like hot, cool, and archive tiers only with GPv2, and it's recommended to choose GPv2 for new workloads to leverage enhanced scalability and cost management.
Blob storage accounts focus on object storage and tiering for cost optimization. They support the hot tier for active streaming scenarios and the cool tier for less frequently accessed content. You can store large media files efficiently, optimize costs by moving older assets to cool storage, and keep streaming assets in hot storage for low latency.
When selecting a SKU, consider replication and durability needs. For testing, Standard_LRS (locally redundant storage) is common. For production, Standard_RAGRS (read-access geo-redundant storage) ensures business continuity by replicating data to a secondary region. Always choose storage accounts in the same region as your services to avoid additional egress charges.
StudyCerts
StudyCerts