Study guide
2.9 Azure Storage Accounts and Services
Microsoft Azure Fundamentals AZ-900
Track your progress as you read
Finished sections get a check mark.
1 Introduction
About the Microsoft Azure Fundamentals (AZ-900) Exam Study Strategies and Exam Tips
2 Domain 1: Cloud Concepts (25-30%)
1.1 What Is Cloud Computing? 1.2 Cloud Service Models (IaaS, PaaS, SaaS) 1.3 Cloud Deployment Models (Public, Private, Hybrid) 1.4 The Consumption-Based Model
3 Domain 2A: Azure Architecture Components
2.1 Azure Regions and Availability Zones 2.2 Azure Resource Hierarchy (Management Groups, Subscriptions, Resource Groups) 2.3 Azure Resource Manager (ARM) Overview
4 Domain 2B: Azure Compute Services
2.3 Azure Virtual Machines 2.4 Azure App Service, Containers, and Serverless 2.5 Azure Virtual Desktop
5 Domain 2C: Azure Networking Services
2.6 Azure Virtual Networks (VNet) 2.7 Azure VPN Gateway and ExpressRoute 2.8 Azure Load Balancing and Content Delivery
6 Domain 2D: Azure Storage Services
2.9 Azure Storage Accounts and Services 2.10 Azure Database Services 2.11 Azure Data Services and Analytics
7 Domain 2E: Azure Identity, Access, and Security
2.11 Microsoft Entra ID (Azure Active Directory) 2.12 Azure RBAC, Zero Trust, and Defense in Depth 2.13 Azure Security Services
8 Domain 3A: Azure Cost Management
3.1 Factors That Affect Azure Costs 3.2 Azure Pricing Calculator and Cost Management 3.3 Using Tags for Cost Management and Organization
9 Domain 3B: Azure Governance and Compliance
3.3 Azure Policy 3.4 Resource Locks and Tags 3.5 Azure Blueprints, ARM Templates, and Bicep 3.6 Azure Governance Features: Putting It All Together
10 Domain 3C: Azure Monitoring and Management Tools
3.6 Azure Monitor and Service Health 3.7 Azure Compliance, Privacy, and Trust 3.8 Azure Activity Log, Diagnostics, and Resource Health
11 Additional Azure Services and Exam Review
Azure AI and Machine Learning Services Azure IoT and DevOps Services AZ-900 Exam Review: Key Concepts Summary Common AZ-900 Exam Scenarios and Practice
12 Advanced Azure Topics and Service Deep Dives
Azure Migration Services and Tools High Availability and Disaster Recovery in Azure Azure Networking: Private Link, Service Endpoints, and Bastion Azure Management Tools: Portal, CLI, PowerShell, and Cloud Shell Azure SLAs, Service Lifecycle, and Support Plans
2.9 Azure Storage Accounts and Services
Key Takeaways Explain This Topic AI
Azure Storage offers four data services in one account: Blob (objects), Files (SMB/NFS shares), Queue (messaging, 64 KB messages), and Table (NoSQL key-value).
A storage account name is globally unique and forms the endpoint URL, e.g. https://accountname.blob.core.windows.net .
Redundancy topology matters: LRS stays within a datacenter, ZRS spans three or more zones, and GRS/GZRS add a secondary region; RA variants add secondary read access.
Hot, Cool, Cold, and Archive trade storage cost against access cost; Cool/Cold/Archive have 30/90/180-day minimum billable durations, and Archive requires rehydration.
Use a general-purpose v2 account for supported standard-service combinations; compare current Data Box capacity and availability when bandwidth makes offline transfer useful.
Last updated: October 2026
Quick Answer: A standard general-purpose v2 Azure Storage account can host four services: Blob (objects), Files (SMB/NFS shares), Queue (64 KB messages), and Table (NoSQL). Redundancy options range from LRS (replication within one datacenter) to GZRS (replication across zones and a secondary region). Blob tiers are Hot, Cool, Cold, Archive. On AZ-900, match the keyword in the question to the service: "shared drive" = Files, "objects/backups" = Blob, "region failure" = GRS/GZRS, "zone failure" = ZRS/GZRS.
What a Storage Account Is
A storage account is a top-level container that gives your data a globally unique namespace . The account name (3-24 lowercase letters and numbers) must be unique across all of Azure because it becomes part of a public endpoint URL. Each service gets its own endpoint built from that name:
- Service Endpoint format
- Blob https:// accountname .blob.core.windows.net
- Files https:// accountname .file.core.windows.net
- Queue https:// accountname .queue.core.windows.net
- Table https:// accountname .table.core.windows.net
A single account can host all four services at once. Storage service endpoints support HTTPS ; whether a client can reach data depends on network rules, authentication, and authorization. Access methods vary by service and include account keys, shared access signatures (SAS) , and Microsoft Entra ID identities.
Account Types
- Type Services Performance
- Standard general-purpose v2 Blob, Files, Queue, Table Standard (HDD-backed)
- Premium block blobs Blob only Premium (SSD), high transaction rate
- Premium file shares Files only Premium (SSD)
- Premium page blobs Page blobs only Premium (SSD)
On the Exam: Standard general-purpose v2 is a common choice when you need supported standard storage services in one account. It can host the four standard services, but available redundancy and access-tier combinations depend on the service and region; for example, Archive blobs do not support ZRS or GZRS, and Azure Files does not support RA-GRS or RA-GZRS. Premium account types target specialized workloads.
- The Four Data Services
- Blob Storage (objects)
Blob (Binary Large Object) Storage holds unstructured data: images, video, backups, logs, documents. There are three blob types: block blobs for general files up to 190.7 TiB , append blobs optimized for logging, and page blobs (up to 8 TiB) that back virtual hard disks for VMs.
Access Tiers
- Tier Best for Storage cost Access cost Minimum billable duration
- Hot Frequent access Highest Lowest None
- Cool Infrequent Lower Higher 30 days
- Cold Rare Lower still Higher still 90 days
- Archive Offline/long-term Lowest Highest 180 days
A worked example: you retain 10 TB of compliance logs for at least 180 days and can wait hours when an old file is requested. Archive may reduce storage charges if retrieval and early-deletion costs still make the total favorable. If logs need immediate access, choose an online tier instead. An archived blob is offline until rehydrated to Hot, Cool, or Cold; rehydration may take hours.
Azure Files (shared drives)
Azure Files provides fully managed file shares reachable over SMB (Server Message Block) and NFS (Network File System) . Multiple machines mount the same share like a network drive. Azure File Sync caches a cloud share on on-premises Windows servers for hybrid access. Reach for Files whenever a question says "replace a file server," "shared drive," or "lift-and-shift an app that expects SMB."
Queue and Table Storage
Queue Storage holds messages (up to 64 KB each) for asynchronous, decoupled communication between app components — a web tier drops work; a worker tier picks it up later, so each scales independently.
Table Storage is a schemaless NoSQL key-value store for large volumes of structured-but-non-relational data. Azure Cosmos DB for Table is an alternative with global distribution and other feature differences; choose by requirements.
Redundancy Options
- Option Replication topology Protects against
- LRS Locally Redundant Storage Replicas within one datacenter Local hardware failure
- ZRS Zone-Redundant Storage Replicas across three or more availability zones Zone failure
GRS Geo-Redundant Storage LRS in primary plus asynchronous replication to secondary region Region failure, subject to failover and recovery conditions
GZRS Geo-Zone-Redundant Storage ZRS in primary plus asynchronous replication to secondary region Zone and region failures, subject to failover and recovery conditions
RA-GRS and RA-GZRS add read access to the secondary region without a failover, subject to access controls. With GRS/GZRS, secondary access follows a supported failover, which may be customer-managed or Microsoft-managed. Memory hooks: a zone-failure requirement suggests ZRS or GZRS; a region-failure requirement suggests GRS or GZRS; a secondary-read requirement suggests an RA variant. Read access is distinct from durability.
Migration and Movement Tools
- Tool What it does Use when
- Azure Migrate Discover, assess, and plan supported workload migrations Supported server-migration scenarios
Azure Data Box Shipped offline-transfer devices; current models include 120 TB and 525 TB usable options Large transfers where network upload is impractical; check regional availability
- AzCopy Scriptable command-line copy Automated/CI transfers over the wire
- Storage Explorer GUI for browsing/managing storage Interactive ad-hoc management
For a large transfer with limited bandwidth, compare an available Data Box device with network-transfer tools such as AzCopy; device capacity and availability depend on the current model and region.