Why Blob containers and access levels in Azure? - Purpose & Use Cases

The Big Idea

What if you could share files securely without worrying about who can see them?

The Scenario

Imagine you have a folder full of photos on your computer, and you want to share some with friends but keep others private. You try to do this by copying files to different USB drives and emailing links manually.

The Problem

This manual sharing is slow and confusing. You might send the wrong files, forget to update permissions, or accidentally share private photos. Managing who can see what becomes a big headache.

The Solution

Blob containers with access levels let you organize your files in the cloud and control who can see or edit them easily. You set simple rules once, and the system handles sharing securely and automatically.

Before vs After

✗ Before

Copy files to USB; Email links; Track who got what

✓ After

Set container access level; Upload blobs; Share URLs with permissions

What It Enables

You can safely share large amounts of data with different people, controlling access without extra effort.

Real Life Example

A company stores marketing images in a blob container set to public read access so their website can load images directly, while keeping internal documents private in a separate container.

Key Takeaways

Manual file sharing is slow and error-prone.

Blob containers organize data with clear access rules.

Access levels simplify secure sharing and management.

Practice

1. What does setting a blob container's access level to private mean?

easy

A. Anyone can read blobs but cannot list them.

B. Anyone can read and list blobs in the container.

C. Only the owner can read or list blobs in the container.

D. The container is deleted automatically after 24 hours.

Solution

1. Step 1: Understand the meaning of private access level

   Private means no public access; only authorized users can access blobs.

2. Step 2: Compare with other access levels

   Unlike blob or container levels, private restricts all public read or list operations.

3. Final Answer:

   Only the owner can read or list blobs in the container. -> Option C

4. Quick Check:

   Private access = owner-only access [OK]

Hint: Private means no public read or list access [OK]

Common Mistakes:

• Confusing private with blob-level public read
• Thinking private allows public listing
• Assuming private deletes container automatically

2. Which of the following is the correct way to set a blob container's access level to allow public read of blobs but not listing containers using Azure CLI?

easy

A. az storage container set-permission --name mycontainer --public-access container

B. az storage container set-permission --name mycontainer --public-access blob

C. az storage container set-permission --name mycontainer --public-access private

D. az storage container set-permission --name mycontainer --public-access none

Solution

1. Step 1: Identify the access level for public read of blobs only

   The blob access level allows public read of blobs but not container listing.

2. Step 2: Match the Azure CLI command syntax

   The command uses --public-access blob to set this level correctly.

3. Final Answer:

   az storage container set-permission --name mycontainer --public-access blob -> Option B

4. Quick Check:

   Blob access = public read blobs only [OK]

Hint: Use '--public-access blob' for public blob read only [OK]

Common Mistakes:

• Using 'container' instead of 'blob' for public read
• Using 'private' which disables public access
• Using 'none' which is invalid in Azure CLI

3. Given a container with access level set to container, what will happen if an anonymous user tries to list blobs in the container?

medium

A. The user can list blobs and read blob content anonymously.

B. The container will block all anonymous requests.

C. The user can read blobs but cannot list them.

D. The user will receive an error because listing is not allowed.

Solution

1. Step 1: Understand the container access level

   This level allows anonymous users to list blobs and read blob content.

2. Step 2: Analyze anonymous user permissions

   Anonymous users can list blobs and read blobs but cannot modify or delete.

3. Final Answer:

   The user can list blobs and read blob content anonymously. -> Option A

4. Quick Check:

   Container access = public list and read [OK]

Hint: Container access allows public list and read [OK]

Common Mistakes:

• Confusing container with blob access level
• Assuming anonymous users cannot list blobs
• Thinking container blocks anonymous requests

4. You set a blob container's access level to blob but anonymous users report they cannot list blobs. What is the most likely cause?

medium

A. The storage account is disabled.

B. The container name is incorrect in the URL.

C. The blobs are encrypted and cannot be read.

D. Blob access level does not allow listing blobs publicly.

Solution

1. Step 1: Recall what blob access level permits

   Blob access allows anonymous read of blobs but not listing blobs in the container.

2. Step 2: Evaluate other options for likelihood

   Incorrect container name or disabled account would cause different errors; encryption does not block listing.

3. Final Answer:

   Blob access level does not allow listing blobs publicly. -> Option D

4. Quick Check:

   Blob access = no public listing [OK]

Hint: Blob access disables public listing, only allows read [OK]

Common Mistakes:

• Expecting blob access to allow listing
• Blaming encryption for listing issues
• Ignoring container name correctness

5. You want to share some files publicly but prevent users from listing all files in your Azure blob container. Which access level should you choose and why?

hard

A. Set access level to blob to allow public read of blobs but block listing.

B. Set access level to private to block all public access.

C. Set access level to container to allow public read and listing.

D. Set access level to public to allow full access.

Solution

1. Step 1: Identify the requirement for public read without listing

   You want users to read files but not see all file names.

2. Step 2: Match access level to requirement

   blob access allows public read of blobs but prevents listing container contents.

3. Step 3: Exclude other options

   private blocks public read; container allows listing; public is not a valid access level.

4. Final Answer:

   Set access level to blob to allow public read of blobs but block listing. -> Option A

5. Quick Check:

   Blob access = public read, no listing [OK]

Hint: Use blob access to share files without listing [OK]

Common Mistakes:

• Choosing container access which allows listing
• Using private which blocks public read
• Thinking 'public' is a valid access level