L13. Storage Account Security
Course outlineLesson 13 of 18
Combine scoped SAS, network restrictions, encryption key availability and configured malware response to protect Azure Storage data.
Course context: AZ-500 retired on August 31, 2026. Use these Azure security concepts for operational practice and continue with the current SC-500 course for certification preparation.
Shared Access Signatures
A SAS grants constrained data access. Limit its scope, permissions and lifetime, require HTTPS, and protect the token.
| Type | Signing key | Revocation approach |
|---|---|---|
| Account SAS | Storage account key | Rotate the signing account key |
| Service SAS | Storage account key | Revoke its stored access policy if used, otherwise rotate the signing key |
| User delegation SAS | Delegation key obtained through Microsoft Entra ID | Revoke user delegation keys for the account; plan for caching delays |
Disallowing Shared Key rejects account-key-authorized requests, including account and service SAS. A Blob user delegation SAS remains valid under this setting. Review service and client compatibility before changing it; the setting does not disable separately configured anonymous public blob access.
Storage Firewall and Private Access
Network rules restrict data-plane access through the public endpoint. They do not replace authorization and do not control Azure Resource Manager operations. Service endpoints allow approved subnets to reach the public service endpoint. Private endpoints provide private connectivity.
Disabling public network access blocks ordinary public endpoint and service endpoint traffic. Previously configured trusted-service or resource-instance exceptions can remain effective, so review them explicitly when designing private-only access. A trusted-service exception is limited to documented service scenarios and still needs appropriate authorization.
Encryption and Key Availability
Storage encrypts data at rest by default. With customer-managed keys, Storage uses a managed identity to wrap and unwrap its account encryption key through Key Vault or Managed HSM. Preserve key permissions and recovery protections. Losing access to the CMK can interrupt data access; do not delete keys as a routine security test.
Customer-provided keys for supported Blob operations are supplied on requests and are not stored by Azure Storage.
Defender for Storage
Activity monitoring, sensitive data threat detection and malware scanning address different risks. Malware scanning supports on-upload and on-demand scanning with the relevant configuration. It is not merely hash reputation, and enabling detection alone does not guarantee that malicious content is blocked or quarantined. Configure and verify the response path.
References
- SAS overview
- Create a Blob user delegation SAS
- Prevent Shared Key authorization
- Storage network controls
- Storage firewall limitations
- Customer-managed keys
- Customer-provided keys
- Defender for Storage
- AZ-500 retirement and legacy skills outline
Continue Learning
- ✓Prefer user delegation SAS where supported; it is signed with a delegation key obtained through Entra authorization
- ✓Account SAS uses account keys; a service SAS can use a stored access policy for revocation
- ✓Shared Key denial rejects key-based SAS; Blob user delegation SAS still works and anonymous access is separately configured
- ✓Storage firewall rules apply to data-plane public endpoint access; review trusted-service and resource-instance exceptions
- ✓CMK availability depends on managed identity key access and key lifecycle; preserve recovery protections
- ✓Defender for Storage includes configured malware scanning, activity monitoring and sensitive data threat detection
1. Which SAS approach avoids signing with the storage account key for Blob Storage?
2. What does enabling Defender for Storage malware scanning provide?
3. Shared Key access is disabled on an account. Which Blob request can still use SAS authorization?