Study guide

10.1 Storage Account Security & Access Controls

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.1 Storage Account Security & Access Controls

Key Takeaways Explain This Topic AI

User Delegation SAS is the most secure Shared Access Signature type because it is signed using Microsoft Entra ID credentials rather than the account key, eliminating key exposure risks.

Disabling shared key access ( allowSharedKeyAccess = false ) blocks all requests authenticated via Storage Account Access Keys or key-signed SAS tokens, mandating Microsoft Entra ID authentication for all data plane operations.

Immutable Blob Storage enforces Write Once, Read Many (WORM) compliance using Legal Holds or Time-Based Retention Policies. A locked retention policy cannot be altered or removed even by Global Administrators.

Customer-Managed Keys (CMK) combined with Infrastructure Encryption provide double encryption at rest using two independent AES-256 cryptographic layers.

Defender for Storage provides real-time threat protection, agentless on-upload malware scanning, and sensitive data discovery for blob storage repositories.

Last updated: August 2026

6.4 Storage Account Security & Access Controls

Azure Storage accounts host critical enterprise data across Blobs, Files, Queues, and Tables. Securing storage assets requires enforcing robust authentication controls, eliminating legacy access keys, implementing double encryption at rest, guaranteeing data immutability for compliance, and enabling real-time threat protection.

Storage Authentication & Access Control Hierarchy

Azure Storage supports multiple authentication mechanisms ranging from legacy shared keys to modern Zero Trust Entra ID governance. +-----------------------------------------------------------------------------------+

  • | STORAGE ACCOUNT ACCESS CONTROL HIERARCHY |
  • +-----------------------------------------------------------------------------------+
  • | 1. Shared Key Access (Root Key 1 & 2) ----> Full Account Admin Access (High Risk)|
  • | 2. Account & Service SAS (Key Signed) ----> Delegated URI Access (Medium Risk) |
  • | 3. User Delegation SAS (Entra Signed) ----> OAuth Signed, Keyless (Low Risk) |
  • | 4. Microsoft Entra ID Azure RBAC -------> Keyless, Fine-Grained (Recommended) |
  • +-----------------------------------------------------------------------------------+
  • Account Access Keys

Every storage account generates two 512-bit master access keys ( key1 and key2 ). Presenting an access key grants full administrative and data plane control over every service and container within the storage account.

Risk Vector: Access keys cannot be scoped by permission, expiration, or resource path. If leaked, an attacker gains complete control.

Key Rotation: Managed key rotation requires updating application configuration to use key2 , rotating key1 , switching applications back to key1 , and rotating key2 .

Disabling Shared Key Access ( allowSharedKeyAccess = false )

To enforce a Zero Trust identity model, organizations should explicitly disable account key authentication by setting allowSharedKeyAccess = false on the storage account configuration:

Enforced Result: Any incoming data plane request authenticated via storage account keys or SAS tokens signed with account keys is rejected by Azure Storage.

Mandatory Entra ID Authentication: Forces all client applications and users to authenticate using Microsoft Entra ID credentials (via Azure RBAC roles such as Storage Blob Data Contributor or Storage Blob Data Reader ).

Shared Access Signatures (SAS) Comparison

A Shared Access Signature (SAS) is a signed URI string granting constrained access rights to storage resources:

  • SAS Feature / Metric Account SAS Service SAS User Delegation SAS
  • Signing Credential Primary Storage Account Key Primary Storage Account Key Microsoft Entra ID Credentials
  • Resource Scope Account-wide (Blobs, Files, Queues) Specific container or blob Specific blob container or blob
  • Storage Key Exposure High (Key used to sign token) High (Key used to sign token) Zero (No account key used)
  • RBAC Authorization Bypasses Entra RBAC Bypasses Entra RBAC Enforces User/App Entra RBAC
  • Recommended Use Legacy multi-service delegates Legacy single-container access All modern application access
  • Stored Access Policies

A Stored Access Policy is defined on a specific blob container or file share (up to 5 policies per container). Linking a Service SAS to a Stored Access Policy provides centralized management:

Allows administrators to modify SAS start time, expiration time, or permissions without reissuing SAS strings.

Enables instant revocation of issued SAS tokens by deleting or modifying the underlying Stored Access Policy.

Encryption Architecture: SSE, CMK & Infrastructure Encryption

All data written to Azure Storage is automatically encrypted at rest using 256-bit AES Server-Side Encryption (SSE) .

Platform-Managed vs. Customer-Managed Keys (CMK)

Platform-Managed Keys (PMK): Keys are generated, rotated, and managed automatically by Microsoft.

Customer-Managed Keys (CMK): Keys are stored in Azure Key Vault or Managed HSM. Enables customer key rotation, access revocation (by disabling key access), and cryptographic audit logging.

Infrastructure Encryption (Double Encryption)

Infrastructure Encryption adds a second, independent layer of AES-256 hardware-level encryption at the physical storage infrastructure layer:

Data is encrypted twice using two different encryption keys and algorithms (one at the service layer, one at the storage infrastructure layer).

Must be enabled at storage account creation time ( requireInfrastructureEncryption = true ) and cannot be disabled later.

Immutable Blob Storage for WORM Compliance

Immutable Blob Storage enforces Write Once, Read Many (WORM) compliance for financial and legal mandates (e.g., SEC Rule 17a-4, FINRA 4511). +-----------------------------------------------------------------------------------+

  • | IMMUTABLE BLOB POLICY STATES |
  • +-----------------------------------------------------------------------------------+
  • | +-----------------------------------------------------------------------------+ |
  • | | Legal Hold: Indefinite immutability, set/cleared by authorized users. | |
  • | +-----------------------------------------------------------------------------+ |
  • | | Time-Based Retention Policy (Unlocked): Retention period active; changeable.| |
  • | +-----------------------------------------------------------------------------+ |
  • | | Time-Based Retention Policy (LOCKED): IMMUTABLE! Retention period CANNOT be | |
  • | | reduced or deleted by ANY user, Subscription Owner, or Microsoft Support. | |
  • | +-----------------------------------------------------------------------------+ |
  • +-----------------------------------------------------------------------------------+
  • 1. Time-Based Retention Policies

Retains blob data immutably for a designated duration (e.g., 2,555 days for 7 years):

Unlocked State: The retention policy can be tested, extended, shortened, or removed.

Locked State: Once a time-based policy is explicitly Locked :

The retention period cannot be shortened or removed by any user.

Data within the container cannot be modified, overwritten, or deleted by anyone—including Subscription Owners, Global Administrators, or Microsoft Support—until the retention period expires.

2. Legal Holds

A Legal Hold is an indefinite immutability lock applied during active litigation or audits. Unlike locked time-based policies, a Legal Hold can be cleared by users possessing the Storage Blob Data Owner role once litigation resolves.

Defender for Storage Threat Protection

Microsoft Defender for Storage provides advanced AI-driven threat intelligence and real-time security monitoring for blob containers:

Malware Scanning on Upload

Agentless In-Line Scanning: Automatically scans newly uploaded blobs for malware in near-real-time without requiring host agents.

Automated Quarantine Workflows: If malware is detected, Defender tags the blob's Index Tags (e.g., MalwareScanningResult = Malicious ), enabling Event Grid topics to trigger automated quarantine or deletion workflows.

Sensitive Data Threat Detection & Anomaly Monitoring

Detects suspicious access patterns, including:

Unusual data exfiltration spikes or anonymous access attempts.

Access originating from known malicious IP addresses or Tor exit nodes.

Compromised credential usage patterns.

Loading diagram... Disabling Storage Account Shared Key Access for Zero Trust Entra ID Governance