Copyright (c) 2026 MindMesh Academy. All rights reserved. This content is proprietary and may not be reproduced or distributed without permission.

3.1.1.3. Configure Blob Storage

3.1.1.3. Configure Blob Storage

💡 First Principle: Azure Blob Storage provides a highly scalable, cost-effective, and secure solution for unstructured data, with features designed to optimize for diverse access patterns, compliance needs, and data protection.

Scenario: You need to store millions of images for a web application, and also store long-term backups that are rarely accessed but must be retained for compliance.

What It Is: Azure Blob Storage is Microsoft's object storage solution for the cloud. It's designed to store vast amounts of unstructured data, like images, videos, documents, backups, and archives.

Blob Types:
  • Block blobs: Ideal for large files (documents, media, backups). Data is uploaded in blocks for efficient, parallel uploads. Most common type.
  • Append blobs: Designed for append-only operations, such as logging scenarios where new data is continuously added to the end of a blob.
  • Page blobs: Support random read/write access, making them suitable for virtual hard disk (VHD) files for Azure VMs.

Containers: Blobs are grouped into containers, which provide a logical structure and can have access policies to control permissions at the container or blob level. Containers are similar to folders in a file system.

Key Configuration Features:
  • Access Tiers: (Hot, Cool, Cold, Archive) - Optimize costs based on access frequency and retrieval latency. (See 3.1.1.4 for more detail).
  • Immutability:
    • WORM (Write Once, Read Many) policies can be set to prevent modification or deletion for a specified retention period, supporting compliance needs for data governance.
  • Soft Delete:
    • Allows recovery of blobs or containers that were accidentally deleted, adding a layer of data protection.
Object Replication for Block Blobs

Redundancy settings (LRS, ZRS, GRS) copy an entire account to a location Azure chooses. Object replication is the tool when you choose the destination: it asynchronously copies block blobs from a container in one storage account to a container in another account, in the same region or a different one, and even in a different subscription. Use it to put read copies close to users in another region, to let compute in a second region process the same data, or to replicate only processed results.

Prerequisites:
  • Blob versioning enabled on both the source and destination accounts.
  • Change feed enabled on the source account. Azure Storage reads the source change feed to find the writes and deletes to replicate.
  • Both accounts are general-purpose v2 or premium block blob accounts. Accounts with a hierarchical namespace aren't supported, and only block blobs replicate (not append blobs or page blobs).

How a policy is built: A replication policy names one source account and one destination account and contains one or more rules. Each rule maps one source container to one destination container and can filter blobs by name prefix. The policy is created on the destination account first. Azure assigns it a policy ID, and the same policy ID is then associated with the source account, because replication only takes place when the IDs match.

Behaviors that surprise people:
  • Existing blobs are skipped by default. A new rule copies only blobs created after it exists, unless you choose to copy existing blobs too or set a custom copy scope.
  • The destination container rejects writes. While the policy is active, writes to the destination container fail with 409 (Conflict). Reads and deletes are still allowed. To write there again, delete the rule or the whole policy.
  • Versions replicate, snapshots don't. The current version and previous versions are copied, but blob snapshots are not.
  • Archive tier breaks replication. Replication fails for a blob in the archive tier in either account, and changing a source blob's tier doesn't change the tier of its replica.
  • Limits: A source account can replicate to at most two destination accounts (one policy each), and each policy holds up to 1,000 rules.
  • Versioning is locked on. You can't disable blob versioning on an account while an object replication policy is in effect.
  • Cross-tenant replication is off by default for accounts created on or after December 15, 2023, through the AllowCrossTenantReplication property.
Geo-redundant storage (GRS/GZRS)Object replication
What is copiedThe entire accountSelected containers, optionally filtered by prefix
DestinationThe paired secondary regionAny storage account you choose
PrerequisitesNone beyond the redundancy settingVersioning on both accounts, change feed on the source

⚠️ Exam Trap: When a replication policy can't be created, check the prerequisites: versioning on both accounts and change feed on the source. Enabling soft delete or geo-redundancy satisfies neither.

⚠️ Common Pitfall: Using the wrong blob type for the workload, such as using block blobs for VM disks, which would be inefficient and not supported for managed disks.

Key Trade-Offs:
  • Performance vs. Cost (Access Tiers): Hot tier offers the best performance but at the highest storage cost. Archive tier offers the lowest storage cost but with high retrieval latency and cost.

Reflection Question: How does configuring Azure Blob Storage with appropriate blob types (e.g., Block blobs) and features like access tiers and immutability policies fundamentally enable you to optimize for performance, compliance, and cost across diverse unstructured data workloads?

See how it connects
Alvin Varughese
Written byAlvin Varughese
Founder•22 professional certifications earned