Chapter 11 — Azure Storage Services

What is Azure Storage?

Azure Storage is Microsoft's cloud storage solution for modern data. It provides highly available, massively scalable, durable, and secure storage for all types of data objects.

Azure Storage is used by VMs (for disks), applications (for files and databases), and developers (for queues and tables).


Azure Storage Account

A Storage Account is the top-level container that holds all your Azure storage services. Everything you store in Azure goes into a storage account.

Storage Account: "mystorageaccount"
├── Blob Storage    (unstructured data — files, images, videos)
├── File Storage    (shared file system — like a network drive)
├── Queue Storage   (message queuing between app components)
└── Table Storage   (NoSQL key-value data)

Storage Account Types

Type

Description

Supports

Standard general-purpose v2

Most common — use for almost everything

Blob, File, Queue, Table

Premium block blobs

High-performance blob storage

Large/frequent blob operations

Premium file shares

High-performance file shares

File storage only

Premium page blobs

High-performance page blobs

VHD/disk storage for VMs


1. Azure Blob Storage

What Is It?

Blob Storage stores unstructured data — any type of file in any format. "Blob" stands for Binary Large Object.

Common uses:

  • Images and videos served on websites

  • Log files

  • Backups and archives

  • Documents (PDFs, Word files)

  • Big data analytics input/output

Blob Types

Blob Type

Description

Use Case

Block Blob

Stores text and binary data in blocks

Files, images, videos, documents

Append Blob

Optimized for append operations

Log files, audit trails

Page Blob

Random read/write in 512-byte pages

Azure VM disks (VHD files)

Access Tiers

Azure Blob Storage offers access tiers based on how frequently you access data:

Tier

Access Frequency

Storage Cost

Access Cost

Use Case

Hot

Frequently

Higher

Lower

Active data, website content

Cool

Infrequently (30+ days)

Lower

Higher

Backups, short-term archive

Cold

Rarely (90+ days)

Lower

Higher

Long-term infrequent access

Archive

Rarely (180+ days)

Lowest

Highest

Long-term archive, compliance

Archive tier data is offline — it must be rehydrated (brought back online) before you can access it. This takes hours.


2. Azure File Storage

What Is It?

Azure Files provides fully managed file shares in the cloud that are accessible via the SMB (Server Message Block) or NFS (Network File System) protocol — the same protocols used by Windows and Linux file servers.

Your Windows Server (on-premises)
  └── Maps a network drive to:  \\mystorageaccount.file.core.windows.net\myshare
        ↕
  Azure File Share (in the cloud)

Key Features

Feature

Detail

Protocol

SMB 2.1, 3.0, 3.1.1 and NFS 4.1

OS support

Windows, Linux, macOS

Fully managed

No file server to manage

Access

Directly from Azure VMs or on-premises via VPN

Azure File Sync

Sync on-premises file servers with Azure Files

When to Use Azure Files

  • Lift-and-shift applications that depend on file shares

  • Replace or supplement on-premises file servers

  • Share configuration files between multiple VMs

  • Applications that use SMB to write/read data


3. Azure Queue Storage

What Is It?

Azure Queue Storage stores messages that can be retrieved and processed asynchronously. Queues decouple components of an application — allowing them to communicate without directly calling each other.

Application A (Producer)
  │  Writes message: "Process order #12345"
  ▼
  Queue Storage (holds messages — up to 64KB each)
  │  Message waits until consumed
  ▼
Application B (Consumer)
  │  Reads and processes the message
  ▼
  Order #12345 is processed

Key Features

Feature

Detail

Max message size

64 KB

Max queue size

Unlimited (stored as long as the storage account allows)

Message TTL (Time to Live)

Default 7 days, configurable up to 7 days

Visibility timeout

Message hidden while being processed (prevents double processing)

Access

Via REST API, Azure SDKs

When to Use Queue Storage

  • Decoupling application components (producer-consumer pattern)

  • Handling bursts of requests without overloading the consumer

  • Asynchronous task processing (send email, resize image, process payment)

  • Microservices communication


4. Azure Table Storage

What Is It?

Azure Table Storage is a NoSQL key-value store for structured, non-relational data. It stores data in tables of entities (rows), each identified by a unique key.

Table: "CustomerOrders"
PartitionKey  RowKey     CustomerName   OrderDate    Amount
─────────────────────────────────────────────────────────
"US"          "ORD-001"  Alice          2026-01-15   $120.00
"US"          "ORD-002"  Bob            2026-01-16   $85.00
"EU"          "ORD-003"  Claire         2026-01-17   $200.00

Key Concepts

Concept

Description

Table

Collection of entities (like a database table)

Entity

A single row — up to 255 properties, 1MB max

PartitionKey

Groups entities for efficient querying

RowKey

Unique identifier within a partition

No schema

Each entity can have different properties

When to Use Table Storage

  • Storing user preferences, settings, or metadata

  • Session data for web applications

  • Non-relational structured data at scale

  • IoT device telemetry data

Note: For more advanced NoSQL capabilities (global distribution, multiple APIs), use Azure Cosmos DB instead.


5. Azure Disk Storage

What Is It?

Azure Managed Disks are block-level storage volumes used as the hard drives for Azure Virtual Machines.

Azure Virtual Machine
  ├── OS Disk (C:\ drive) — Contains Windows/Linux OS
  ├── Temporary Disk (D:\ drive) — Ephemeral, lost on reboot
  └── Data Disk(s) — Extra storage you attach to the VM

Disk Types

Disk Type

Performance

Cost

Use Case

Ultra Disk

Up to 160,000 IOPS

Highest

SAP HANA, top-tier databases

Premium SSD v2

High, configurable

High

Production databases

Premium SSD

High

High

Production workloads

Standard SSD

Moderate

Medium

Dev/test, web servers

Standard HDD

Low

Lowest

Backup, infrequent access

IOPS = Input/Output Operations Per Second — how fast the disk can read/write.


Storage Redundancy Options

Azure replicates your data to protect against hardware failures. You choose your redundancy level:

Option

Full Name

Copies

Protection Against

LRS

Locally Redundant Storage

3 (same data center)

Hardware failure in one rack

ZRS

Zone-Redundant Storage

3 (across 3 zones)

Zone/data center failure

GRS

Geo-Redundant Storage

6 (3 local + 3 in paired region)

Regional disaster

GZRS

Geo-Zone-Redundant Storage

6 (ZRS + paired region)

Zone failure + regional disaster

Durability with GRS: 99.999999999% (that's eleven 9s!)

Storage Services Summary

Service

Data Type

Use Case

Blob Storage

Files, images, videos, backups

Unstructured data at scale

File Storage

File shares (SMB/NFS)

Shared drives for apps and VMs

Queue Storage

Messages

Async communication between apps

Table Storage

NoSQL key-value

Structured non-relational data

Disk Storage

VM disk volumes

OS and data disks for VMs


Quick Recap

Blob    → Store any file type (images, videos, backups)
File    → Cloud network drive (SMB/NFS)
Queue   → Message passing between app components
Table   → Simple NoSQL structured storage
Disk    → Virtual hard drives for VMs

Access tiers (Blob): Hot → Cool → Cold → Archive (cheapest but slowest)
Redundancy: LRS < ZRS < GRS < GZRS (most protected)

Official References


Next Chapter → Chapter 12: Azure Database Services