Skip to content

Commit 92ce9f8

Browse files
Update note on version-level immutability and retention
Clarified the explanation of version-level immutability and retention policies for blob versions.
1 parent 86c7cc0 commit 92ce9f8

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

articles/storage/blobs/immutable-policy-configure-version-scope.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -509,8 +509,8 @@ az storage blob immutability-policy delete \
509509

510510
---
511511

512-
513-
> With version‑level immutability enabled, each blob version gets its own immutable retention at upload. Even with unlocked retention policy, changing the container’s default later does not shorten existing versions.
512+
> [!NOTE]
513+
> With version‑level immutability enabled, each blob version receives its own immutable retention period at the moment it is created. Even if the container’s default policy is unlocked, modifying the container‑level default retention policy later can never shorten, override, or reduce the retention already assigned to existing versions. When a new version is uploaded, you may optionally assign a unique retention period specifically for that version. If no unique value is assigned, the version automatically inherits the container’s current default retention policy.
514514
515515
## Lock a time-based retention policy
516516

0 commit comments

Comments
 (0)