Azure blobs store unstructured data such as images, executables, libraries, Word files, and Excel documents, and are accessed over HTTP or HTTPS.
A storage account must exist before blobs can be stored, and blobs are organized under containers within that account.
The session covers what blobs are, their hierarchy, access tiers, and lifecycle management for cost and performance optimization.
Containers and hierarchy
Containers are a flat structure inside a storage account; containers cannot be nested inside other containers.
Multiple containers can be used in one storage account to separate different blobs and apply access or configuration controls.
Folder-like structures inside containers are virtual; the underlying container structure remains flat.
Container-level settings can control whether stored objects are private, public, or anonymously accessible.
Access tiers and cost
Blob access tiers such as hot, cool, and cold affect performance and cost, with faster access generally costing more to store.
Hot storage may be cheaper overall for frequently accessed blobs because access charges can be lower than cooler tiers.
An inferred access tier is inherited from the storage account default, and changing that default can change all blobs with inferred tiers.
Explicitly assigned tiers stay fixed until manually or programmatically changed.
Lifecycle management
Lifecycle management can automatically move blobs to lower-cost tiers after they have not been accessed or used for a defined period.
Moving blobs between tiers requires cost analysis because lower storage costs can be offset by higher access charges.
Billing may be based on the highest tier used during a billing cycle, so frequently moving data between hot and cool tiers may not produce expected savings.
Rules using periods like 30, 60, or 90 days should account for billing-cycle behavior before savings appear.
Replication options
Geo-redundant storage can replicate data from a primary region to its Microsoft-defined paired region, such as US East to US West.
Regional replication remains within the appropriate geographic authority for data domicile requirements.
Containers can also be configured for asynchronous replication to manually selected regions on a per-container basis.
Replication can help place blob data closer to users or workloads in other regions.
Portal demonstration
The demo creates a storage account in the Azure portal, using a globally unique storage account name and selecting a region and account options.
Network access is initially disabled, then enabled for the administrator's current IP address so the resources can be managed through the portal.
The demo reviews data protection settings such as soft delete and encryption options, including Microsoft-managed keys and bring-your-own-key scenarios.
A container is created, an object is uploaded, and the blob URL is opened in a browser using the storage account endpoint format.
Wrap-up
The episode focuses on configuring blobs inside a storage account, including access tiers, lifecycle management, and basic portal operations.
Security and access controls for blobs are identified as topics for other recordings.
Actiepunten
Create a storage account before storing blobs in it.
Use lifecycle management carefully and evaluate access frequency before moving blobs to lower-cost tiers.
Watch other videos in the course or explore Microsoft Learn at aka.ms/learn to continue learning.
