Skip to content

Commit 075c311

Browse files
Merge pull request #35971 from MicrosoftDocs/main
Auto Publish – main to live - 2025-12-01 18:30 UTC
2 parents 4893a0c + c1a4860 commit 075c311

File tree

6 files changed

+242
-122
lines changed

6 files changed

+242
-122
lines changed

azure-sql/database/backup-immutability.md

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ description: Learn how Azure SQL Database immutability works for long-term reten
55
author: WilliamDAssafMSFT
66
ms.author: wiassaf
77
ms.reviewer: dinethi
8-
ms.date: 09/25/2025
8+
ms.date: 11/29/2025
99
ms.service: azure-sql-database
1010
ms.subservice: backup-restore
1111
ms.topic: concept-article
@@ -33,9 +33,11 @@ The Cohasset report is available in the [Microsoft Service Trust Center](https:/
3333

3434
Azure SQL Database LTR backups support both **time based** and **legal hold** types of immutabilities.
3535

36-
**Time-based immutability** is enabled at the policy level. Once the time based immutability is enabled and **locked**, any new LTR backups taken from that point forward inherit these settings, and the backups remain immutable until the end of the configured retention period. Any changes to the LTR retention or to immutability will only apply to future backups from the time of policy change. Changes to LTR retention or immutability aren't applied retroactively to existing LTR backups.
36+
- **Time-based immutability** is enabled at the policy level. Once the time based immutability is enabled and **locked**, any new LTR backups taken from that point forward inherit these settings, and the backups remain immutable until the end of the configured retention period.
37+
- Any changes to the LTR retention or to immutability will only apply to future backups from the time of policy change. Changes to LTR retention or immutability aren't applied retroactively to existing LTR backups.
38+
- For non-hyperscale databases when you configure an LTR policy for the first time the most recent full backup is considered for LTR and immutability is applied on this full backup. For more informatino, see [Long-term retention backups](long-term-retention-overview.md).
3739

38-
**Legal hold immutability** is a type of immutability that can be enabled or disabled on a specific existing backup, independent of any existing time based immutability. Legal hold immutability is useful for scenarios such as auditing, legal purposes, etc. where data from specific backups must be held immutable for an unknown amount of time, typically until an audit or litigation is complete. Legal hold immutability can be enabled and disabled on a backup at any time.
40+
- **Legal hold immutability** is a type of immutability that can be enabled or disabled on a specific existing backup, independent of any existing time based immutability. Legal hold immutability is useful for scenarios such as auditing, legal purposes, etc. where data from specific backups must be held immutable for an unknown amount of time, typically until an audit or litigation is complete. Legal hold immutability can be enabled and disabled on a backup at any time.
3941

4042
> [!TIP]
4143
> - For future backups, configure **time based immutability** at the policy level, a generally available feature.

0 commit comments

Comments
 (0)