Study guide

10.4 Storage Data Protection: Soft Delete, Versioning, Point-in-Time Restore & Backup

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.4 Storage Data Protection: Soft Delete, Versioning, Point-in-Time Restore & Backup

Key Takeaways Explain This Topic AI

Point-in-time restore requires blob soft delete, change feed, and blob versioning first, and covers only block blobs in standard general-purpose v2 accounts — never premium block blobs, append blobs, page blobs, or hierarchical-namespace accounts.

The point-in-time restore period must be at least one day shorter than the blob soft delete retention period, and a deleted container can never be recovered by point-in-time restore.

Point-in-time restore is not supported when version-level immutability is enabled on the account or a container, so compliance-retention data belongs in its own storage account.

A locked time-based retention policy can never be deleted and its interval can only be extended — a maximum of five increases for a container-level policy — with intervals from 1 day to 146,000 days.

Azure Files soft delete is enabled by default on new storage accounts, defaults to 7 days within a 1–365 day range, and protects only whole shares; individual files need share snapshots or Azure Files backup.

Last updated: August 2026

Matching the Control to the Threat

Each protection feature answers a different failure mode. The exam tests whether you can pick the minimum set that satisfies a stated requirement.

  • Threat Control What it does
  • Blob deleted by mistake or by malware Blob soft delete Deleted blob is retained and restorable for 1–365 days

Whole container deleted Container soft delete Deleted container restorable for 1–365 days (configured separately)

Blob overwritten with encrypted content Blob versioning Every write creates a new version; previous versions remain readable

  • Bulk corruption across many blobs Point-in-time restore Rolls a container or prefix back to a chosen timestamp
  • File share deleted Azure Files soft delete Deleted share and its snapshots restorable for 1–365 days

Insider or admin deletes data deliberately Immutable storage (time-based retention or legal hold) Write-once, read-many; not even an Owner can delete before expiry

Account or subscription lost entirely Azure Backup vaulted backup A copy lives in a backup vault outside the storage account

Versioning stops overwrites. Soft delete stops deletes. Neither stops a determined administrator — that is what a locked time-based retention policy is for. Say the requirement out loud and the answer usually names itself.

Point-in-Time Restore and Its Prerequisites

Point-in-time restore (PITR) is the flagship recovery feature and the one with the most testable constraints.

You must enable all three prerequisites before PITR can be turned on:

  • Blob soft delete
  • Change feed (the ordered transaction log of every change)
  • Blob versioning

Account and data constraints:

Supported for block blobs in standard-performance general-purpose v2 accounts only . Append blobs, page blobs, and premium block blobs are never restored , and accounts with a hierarchical namespace (Azure Data Lake Storage) are not supported at all.

Only data in the hot and cool tiers can be restored. If a container in the requested range holds archive-tier blobs, the whole operation fails — partial restores do not exist.

The restore period must be at least one day less than the blob soft delete retention period. A 7-day soft delete therefore permits a restore period of 1–6 days; setting the two equal is rejected.

The window starts a few minutes after you enable PITR, so a 30-day policy switched on May 1 can still only reach 15 days back on May 15.

Operational constraints worth memorizing:

One restore specifies up to 10 lexicographical container or blob-name ranges ; omit the range to restore every container in the account.

The operation is atomic — it either restores every change or fails — and only one restore may run on an account at a time . It cannot be cancelled, although a second restore can undo the first.

Read, write, and delete operations against the affected ranges are blocked in the primary region for the duration.

The caller needs write access to every container; Microsoft names the Storage Account Contributor role at account, resource group, or subscription scope.

PITR does not restore containers. Deleting a container is not a block-blob operation, so it cannot be rolled back, and a range that includes a deleted container makes the restore fail outright. That is exactly why container soft delete is a separate mandatory control and not a duplicate of blob soft delete.

Change feed is independently useful: it is an append-only, immutable log of create, update, and delete events with the identity that made the change, stored in a system container. Security teams read it for forensic reconstruction of an incident.

Immutable Storage: Container-Level and Version-Level WORM

Immutable (write-once, read-many) storage is the only control that stops a subscription Owner from destroying data. It ships in two forms, and choosing between them is a routine exam decision.

  • Aspect Container-level WORM Version-level WORM
  • Where a policy can be set Container only Account, container, or blob version

Policy types available Time-based retention and legal hold Time-based retention at account and container; both at version level

  • Prerequisite None Blob versioning must be enabled
  • Hierarchical namespace Supported Not supported

Deletion behaviour A container with a locked policy is deletable only when empty Account or container is deletable only when empty

Time-based retention intervals run from a minimum of 1 day to a maximum of 146,000 days (400 years) . A new policy is created unlocked , which is a testing state: an unlocked policy can be shortened, extended, or deleted outright, and Microsoft recommends locking it within roughly 24 hours. Once locked , the policy can never be deleted and the retention interval can only be increased — at most five times over the lifetime of a container-level policy, while version-level policies have no such limit. Only a locked policy meets SEC 17a-4(f), CFTC 1.31(c)-(d), and FINRA 4511.

Legal holds have no expiry at all: data stays immutable until the hold is explicitly cleared, which is the right answer whenever the required retention period is unknown. A container-level legal hold must carry one or more user-defined alphanumeric tags — typically a case or matter ID — and every container with a policy keeps a policy audit log recording user ID, command type, timestamps, and retention interval.

The trap: immutability and point-in-time restore do not coexist. PITR is not supported when version-level immutability is enabled on a storage account or on a container in that account. With a container-level policy, a restore can be started, but blobs the policy protects are not modified, so the account never reaches a consistent state at the chosen timestamp. Pick one model per account, and give compliance-retention data its own storage account when a scenario appears to demand both.

Soft Delete for Azure Files

File shares have their own soft delete, configured on the file service rather than the blob service, and the differences are testable:

It is a storage-account-level setting that applies to every classic share in the account, and it is enabled by default on new storage accounts .

Retention defaults to 7 days and can be set anywhere from 1 to 365 days . The clock starts when the share is deleted, and shares deleted before a retention change expire on the value that was configured at deletion time.

Undeleting restores the share and all of its contents, including its snapshots .

It protects only at the share level . Recovering an individual file needs share snapshots or Azure Files backup — a distinction that separates a correct answer from a plausible one.

Purging a soft-deleted share early is deliberately awkward: undelete the share, disable soft delete, delete it again, then re-enable soft delete for the account.

Azure Backup for Blobs and Files

Azure Backup adds a management layer with its own access boundary.

Model Where data lives Recovery granularity Use when

Operational backup (blobs) In the source account, using soft delete, versioning, and change feed Continuous point-in-time within the retention window Fast local recovery, short retention

Vaulted backup (blobs) Copied to a backup vault outside the account Scheduled recovery points Long-term retention; protection against account deletion

Azure Files backup Snapshots managed by a Recovery Services vault, optionally vaulted Share or item level Scheduled protection for SMB shares

The security argument for vaulted backup is separation of blast radius: an attacker who compromises the storage account or its subscription still cannot delete the copies held in the vault, especially with the vault protections covered in the backup security section.

Putting It Together: A Ransomware-Resistant Blob Configuration

A defensible baseline for a business-critical container:

allowSharedKeyAccess = false and allowBlobPublicAccess = false — remove the credential-theft path first, because no recovery feature helps if the attacker has legitimate write access.

Blob versioning on.

Blob soft delete at 30 days, container soft delete at 30 days.

Change feed on, PITR at 29 days — on an account that does not use version-level immutability, since the two are mutually exclusive.

Vaulted backup with retention that outlives your incident-detection time.

Immutable storage with a locked time-based retention policy for compliance-relevant data, held in a separate storage account so it does not disable point-in-time restore for the rest of the estate.

Diagnostic logs to Log Analytics with an alert on mass-delete patterns and on any AuthenticationType = AccountKey request.

Resource lock (CanNotDelete) on the storage account so the account itself cannot be removed in a single API call.

Note the ordering: identity and access hardening first, recovery second. A ransomware operator with a valid account key can disable versioning and shorten retention before encrypting, which is why allowSharedKeyAccess = false and least-privilege data roles do more for resilience than any single recovery toggle.