Blob containers and access levels in Azure - Step-by-Step Execution

Process Flow - Blob containers and access levels

Create Blob Container

↓

Set Access Level

↓

Access Level Options

First, create a blob container. Then choose an access level: Private (no public access), Blob public (public read for blobs only), or Container public (public read for blobs and container listing).

Execution Sample

Azure

az storage container create --name mycontainer --account-name mystorage
az storage container set-permission --name mycontainer --account-name mystorage --public-access blob

Creates a blob container named 'mycontainer' and sets its access level to allow public read access to blobs only.

Process Table

Step	Command	Action	Access Level Set	Result
1	az storage container create --name mycontainer --account-name mystorage	Create container 'mycontainer'	Private (default)	Container created with private access
2	az storage container set-permission --name mycontainer --account-name mystorage --public-access blob	Set access level to Blob public	Blob public	Blobs readable publicly, container listing not allowed
3	Access container blobs anonymously	Try to read blob	Blob public	Success: Blob data accessible
4	Access container listing anonymously	Try to list blobs	Blob public	Fail: Listing denied
5	az storage container set-permission --name mycontainer --account-name mystorage --public-access container	Set access level to Container public	Container public	Blobs and container listing readable publicly
6	Access container listing anonymously	Try to list blobs	Container public	Success: Blob list accessible
7	az storage container set-permission --name mycontainer --account-name mystorage --public-access off	Set access level to Private	Private	No public access to blobs or listing
8	Access blob anonymously	Try to read blob	Private	Fail: Access denied

💡 Access level set to Private, no public access allowed, ending demonstration.

Status Tracker

Variable	Start	After Step 1	After Step 2	After Step 5	After Step 7
Access Level	N/A	Private (default)	Blob public	Container public	Private

Key Moments - 3 Insights

Why can I read blobs but not list them after setting access to Blob public?

Because Blob public access allows anonymous read of blobs only, but container listing is still restricted. See execution_table rows 3 and 4.

What changes when I set access to Container public?

Both blob data and container listing become publicly accessible. See execution_table rows 5 and 6.

What happens if I set access to Private after public access?

All anonymous access is blocked, including reading blobs and listing. See execution_table rows 7 and 8.

Visual Quiz - 3 Questions

Look at the execution_table, what is the access level after Step 2?

A Private

B Container public

C Blob public

D Off

💡 Hint

Check the 'Access Level Set' column in row for Step 2.

At which step does anonymous listing of blobs become possible?

A Step 3

B Step 5

C Step 4

D Step 7

💡 Hint

Look for when 'Access container listing anonymously' succeeds in the 'Result' column.

If you set access level to Private, what happens when trying to read blobs anonymously?

A Access denied

B Access allowed

C Only container listing allowed

D Only blob read allowed

💡 Hint

See Step 8 in execution_table for anonymous blob read result.

Concept Snapshot

Blob containers hold blobs (files) in Azure Storage.
Access levels control public visibility:
- Private: no public access
- Blob public: public read of blobs only
- Container public: public read of blobs and container listing
Set access with Azure CLI or portal.
Choose level based on security needs.

Full Transcript

This visual execution shows how to create an Azure blob container and set its access level. First, the container is created with private access by default. Then, the access level is changed to Blob public, allowing anonymous users to read blobs but not list them. Next, setting access to Container public allows anonymous users to list blobs as well. Finally, setting access back to Private blocks all anonymous access. The execution table traces each step, showing commands, actions, access levels, and results. Variable tracking shows how the access level changes over time. Key moments clarify common confusions about what each access level permits. The quiz tests understanding of access level effects and anonymous access behavior.