Once set on a retention policy, this stops anyone, even an administrator, from disabling, deleting or relaxing it. You add it after creating the policy, and adaptive scopes are not supported.
Read more: Microsoft Learn
In the Ultra Transcenders books
Each book explains Preservation Lock in context, with comparison tables and the common traps.
Terms in this definition
- Once flow
A flow that executes a single time and repeats only if the pipeline is fully refreshed. It's a common choice for a first full load ahead of a change feed, and that refresh becomes dangerous once the original files no longer exist.
- Set
Secret permission in Key Vault for writing secrets; some older material refers to it as Create.
- Retention policy
A preview feature in ACR Premium that removes untagged manifests once a chosen number of days has passed since they lost their tag (7 by default, anywhere from 0 to 365).
- Architecture Definition Document
A key deliverable bringing together the main architecture artifacts across the four domains for every relevant state: baseline, transition and target. It sets out, in qualitative terms, what the architect intends.
- Exclusions
Scopes taken out of a policy assignment; they can only narrow its coverage, never widen it.
Related terms
- Retention label policy
Makes retention labels available in chosen locations for people to apply by hand, or applies them automatically. Preservation Lock is allowed only when all labels in it are regulatory record labels.
- SEC Rule 17a-4
A US rule that records must be stored in a form that cannot be changed, meaning a retention policy cannot be switched off or made less strict after it starts. Preservation Lock in Purview supports compliance with it.