Study guide
10.3 Selecting and Configuring Access to Azure Blob Storage
Microsoft Azure Security Technologies AZ-500
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Exam Overview & Azure Security Architecture Foundation
1.1 Azure Security Engineer Role & Exam Logistics 1.2 Microsoft Cybersecurity Reference Architecture & Zero Trust Principles
2 Chapter 2: Secure Identity and Access - Authentication, MFA & PIM
2.1 Microsoft Entra ID Security, Users, and Groups 2.2 Authentication Methods, MFA, and Conditional Access Policy Design 2.3 Microsoft Entra Privileged Identity Management (PIM)
3 Chapter 3: Secure Identity and Access - RBAC & Workload Identity
3.1 Azure RBAC, Custom Roles, and Governance 3.2 Workload Identities and Managed Identities 3.3 External Identities and Cross-Tenant Collaboration
4 Chapter 4: Microsoft Entra Application Access & Consent Governance
4.1 Enterprise Applications, OAuth Permission Grants & Consent Governance 4.2 App Registrations, Permission Scopes & Service Principal Credentials
5 Chapter 5: Secure Azure Networking - Boundary & Perimeter Protection
5.1 Virtual Network Security & Micro-segmentation 5.2 Azure Firewall and Firewall Manager 5.3 Web Application Firewall (WAF) & Azure Front Door
6 Chapter 6: Secure Azure Networking - Private Access & Monitoring
6.1 Private Connectivity with Private Endpoints & Private Link 6.2 Azure Bastion & Remote Management Security 6.3 Network Perimeter Protection & Flow Monitoring
7 Chapter 7: Network Architecture, Routing & Hybrid Connectivity
7.1 Azure Virtual Network Manager, Network Groups & User-Defined Routes 7.2 VPN Gateway, ExpressRoute Encryption & Virtual WAN Secured Hub 7.3 Network Integration for App Service, Functions, App Service Environment & SQL Managed Instance
8 Chapter 8: Public and Edge Access Protection
8.1 Azure Application Gateway Security, TLS Policy & Mutual Authentication 8.2 Azure Front Door, CDN Caching & TLS for App Service and API Management
9 Chapter 9: Compute, Container & Registry Security
9.1 Azure Virtual Machine Hardening & Host Security 9.2 Azure Key Vault Deep Dive & Secrets Lifecycle 9.3 Container & Azure Kubernetes Service (AKS) Security 9.4 Azure Container Instances, Container Apps & Registry Access Control
10 Chapter 10: Storage Security, Access Methods & Data Protection
10.1 Storage Account Security & Access Controls 10.2 Selecting and Configuring Access to Azure Files 10.3 Selecting and Configuring Access to Azure Blob Storage 10.4 Storage Data Protection: Soft Delete, Versioning, Point-in-Time Restore & Backup
11 Chapter 11: Data Platform & Database Security
11.1 Azure SQL Database Security & Always Encrypted 11.2 Database Auditing & Vulnerability Assessment 11.3 Data Discovery, Classification, & Microsoft Purview Integration
12 Chapter 12: Cloud Governance, Key Lifecycle & Asset Protection
12.1 Azure Policy for Security Governance: Definitions, Initiatives, Effects & Remediation 12.2 Key Vault Backup, Recovery & Automated Key Rotation 12.3 Implementing Security Controls to Protect Backups 12.4 Security Controls for Asset Management: Locks, Tags, Resource Graph & Azure Arc
13 Chapter 13: Microsoft Defender for Cloud - Posture & Workload Protection
13.1 Microsoft Defender for Cloud & Secure Score 13.2 Defender Cloud Workload Protection (CWP) Plans 13.3 Defender for Cloud Inventory, Compliance Standards & Custom Standards 13.4 Connecting AWS and GCP Environments to Microsoft Defender for Cloud
14 Chapter 14: External Attack Surface & Vulnerability Management
14.1 Microsoft Defender External Attack Surface Management (EASM) 14.2 Agentless Scanning & Microsoft Defender Vulnerability Management for Azure VMs 14.3 Defender for Cloud DevOps Security: GitHub, Azure DevOps & GitLab
15 Chapter 15: Security Monitoring, Microsoft Sentinel & Automation
15.1 Azure Monitor Data Collection Rules & Network Security Event Monitoring 15.2 Microsoft Sentinel Data Connectors, Content Hub & Normalization 15.3 Microsoft Sentinel Workspace & KQL Threat Hunting 15.4 Sentinel Incident Management & SOAR Automation
10.3 Selecting and Configuring Access to Azure Blob Storage
Key Takeaways Explain This Topic AI
Control-plane roles such as Owner and Contributor do not grant blob data access — data-plane roles like Storage Blob Data Reader are required.
A user delegation SAS is signed with Microsoft Entra credentials rather than the account key and is limited to a maximum of seven days.
A service SAS bound to a stored access policy is the only SAS type that can be revoked without rotating the account key.
Setting allowBlobPublicAccess to false blocks anonymous read at the account level regardless of individual container settings.
Attribute-based access control conditions can restrict a data role to blobs matching a path prefix or index tag.
Last updated: August 2026
Choosing an Authorization Method
The previous section catalogued what the authorization mechanisms are. This section is about choosing between them for a stated requirement, and about the two capabilities — data-plane roles and ABAC conditions — that make Microsoft Entra ID authorization precise enough to replace shared keys entirely.
- Requirement in the scenario Correct choice
- An Azure workload reads blobs Managed identity + data-plane RBAC role
- A named person needs read access for an audit Microsoft Entra group + Storage Blob Data Reader
- A partner needs 48 hours of read access to one blob User delegation SAS
- A legacy application cannot use OAuth Service SAS bound to a stored access policy , on a migration deadline
- Only some blobs in a container, by path or tag ABAC condition on the role assignment
- A public download page Anonymous read , only if the content is genuinely public
- The control-plane / data-plane trap
Assigning Owner or Contributor on a storage account does not grant access to blob data. Those are control-plane roles: they let the principal manage the account and, critically, read the account keys , which is an indirect path to the data. The data-plane roles are separate:
Storage Blob Data Reader — read blobs and list containers.
Storage Blob Data Contributor — read, write, delete.
Storage Blob Data Owner — full access including POSIX ACL management on Data Lake Storage Gen2.
If a scenario says "the auditor must read blobs but must not be able to manage the account", assign Storage Blob Data Reader and nothing else. If it says "the operator must manage the account but must never read customer data", assign Contributor and set allowSharedKeyAccess = false so the indirect key path is closed.
Operational Rules for Shared Access Signatures
Beyond the SAS types themselves, four operational rules decide whether a SAS is safe:
A user delegation SAS has a maximum validity of seven days , tied to the lifetime of the delegation key. There is no way to issue a year-long user delegation SAS.
The permissions of a user delegation SAS are the intersection of the SAS grant and the signing identity's RBAC role. A Storage Blob Data Reader cannot mint a write SAS, which means SAS issuance cannot be used to escalate privilege.
A SAS expiration policy on the account defines a recommended maximum SAS lifetime and logs a diagnostic entry whenever a longer one is issued, turning "someone created a ten-year SAS" from an invisible event into a detectable one.
Always constrain a SAS with an allowed IP range and HTTPS-only protocol, and scope it to the single blob and single permission it needs. A SAS is a bearer credential in a URL — it will end up in a browser history, a proxy log, or a support ticket.
Revoking a user delegation SAS means revoking the delegation key ( az storage account revoke-delegation-keys ) or removing the signing identity's role; revoking a key-signed SAS means changing the stored access policy it references, or rotating the account key.
Attribute-Based Access Control Conditions
Azure ABAC adds conditions to a data-plane role assignment, evaluated by the storage service at request time:
Restrict by blob path prefix , so one Storage Blob Data Contributor assignment covers only /finance/2026/ and nothing else in the container.
Restrict by blob index tag , so a principal reaches only blobs tagged classification=public regardless of where they sit.
Restrict by request attributes such as the operation being performed, or whether the request arrived over a private endpoint.
A condition is expressed against the request and resource attributes, for example allowing read only where @Resource[Microsoft.Storage/storageAccounts/blobServices/containers/blobs:path] starts with a given prefix.
ABAC turns "one role assignment per container" sprawl into a single assignment with a precise boundary, and it is the answer whenever a scenario needs sub-container granularity without creating dozens of assignments or splitting data across accounts. It also composes with the SAS rules above: a user delegation SAS minted by a condition-limited identity inherits that limit, because SAS permissions are the intersection of the grant and the signer's effective access.
Shutting Down the Weak Paths
These account-level settings are the practical hardening checklist, and each one closes a distinct bypass:
Setting Secure value Effect
allowBlobPublicAccess false Anonymous read becomes impossible even if a container is individually set to public
- allowSharedKeyAccess false Account keys and key-signed SAS are rejected; only Microsoft Entra ID works
- minimumTlsVersion TLS1_2 or higher Blocks legacy TLS negotiation
- supportsHttpsTrafficOnly true Rejects plaintext HTTP requests
- publicNetworkAccess Disabled , with private endpoints Removes the internet path to the account entirely
- defaultToOAuthAuthentication true Portal and tooling default to Entra ID rather than reaching for keys
Note the interaction that catches people out: setting allowSharedKeyAccess = false breaks every existing service and account SAS , because those are signed with the account key. Inventory the consumers, migrate them to user delegation SAS or managed identities, and only then flip the switch — otherwise the change reads as an outage rather than a hardening win.
Encryption scopes belong in the same conversation. They apply a different key — including a customer-managed key in Key Vault — to an individual container or even an individual blob within one storage account. That lets a multi-tenant application isolate tenants cryptographically without provisioning one storage account per tenant, and it lets you revoke one tenant's access to their own data by disabling that scope's key.
Finally, monitor the paths you have not yet closed . Send StorageRead , StorageWrite , and StorageDelete diagnostic logs to Log Analytics and alert on any request where AuthenticationType == "AccountKey" once you believe key usage has been migrated away. That single query is the most reliable way to find the application nobody remembered before it breaks in production.