Configure Azure Blob Storage
MS Learn module: Configure Azure Blob Storage · Learning objectives: understand the purpose & benefits of Blob storage; create & configure blob storage accounts; manage containers and blobs; optimize performance & scalability; implement lifecycle-management policies to automate data movement and deletion; determine pricing for blob storage.
Overview (why this module matters)
Blob (object) storage is the scale-out, unstructured data workhorse of Azure. This module covers the full lifecycle: creating containers/blobs, moving them between access tiers, and automating tiering/deletion with lifecycle-management rules so storage cost stays aligned with data age.
Units / lessons covered
- Introduction / Implement Azure Blob Storage
- Create blob containers
- Create blob access tiers
- Add blob lifecycle-management rules
- Determine blob object replication
- Upload blobs (block/append/page, SAS, AzCopy)
- Determine storage pricing
- Simulation: blob storage / Knowledge check / Summary & resources
Concepts introduced (link each term note)
- Azure Blob Storage — block/append/page blobs, containers
- Access tiers: hot/cool/cold/archive
- Immutable storage / retention (compliance context)
- Storage account (holding account)
- Standard vs Premium block blobs
- Keys & SAS when uploading
- AzCopy for bulk blob transfer
Key terms / commands
# create container
az storage container create -n <container> --account-name <sa> --account-key <key>
# set blob access tier
az storage blob set-tier --container-name <c> --name <blob> --tier Cool --account-name <sa>
# lifecycle rule via ARM template (tier to Cool after 30d, Archive after 90d, delete after 365d)
Hands-on / what to try
- Upload a block blob in the portal, change its tier Hot→Cool→Archive, attempt access while archived.
- Define a lifecycle-management rule; verify tier/deletion movements.
- Use AzCopy to copy blobs between containers/accounts with a SAS.
Exam focus
- Block = default/general, append = logs, page = VM disks.
- Access tiers + lifecycle automation heavily tested (age/last-modified rules).
- Archive = offline, requires rehydration before read; watch minimum-duration penalties.
- Object replication to copy blobs between accounts.
Related
Path MOC · blob-storage · access-tier · immutable-storage · azcopy