Quick Notes141 words
Retention strategy — quick notes
Retention — quick notes
| Surface | Key rule |
|---|---|
| Run-hosted data | Project retention; deleting a run removes its metadata, logs, artifacts and test results |
| Environment history | Separate deployment-history surface |
| Test data | Separate Test settings and required analysis/compliance horizon |
| Run-scoped artifacts | Lease/retain the run through rollback, or copy the exact artifact to durable storage |
| Feed packages | Separate configuration; deletion requires both version-count and recent-download criteria; views are exempt |
- Per-pipeline retention rules are no longer supported; use project settings and retention leases.
- Deleted feed packages remain in the recycle bin for 30 days.
- A saved upstream package protects availability only while the saved copy remains retained.
Sources: https://learn.microsoft.com/en-us/credentials/certifications/resources/study-guides/az-400 · https://learn.microsoft.com/en-us/azure/devops/pipelines/policies/retention · https://learn.microsoft.com/en-us/azure/devops/pipelines/artifacts/pipeline-artifacts · https://learn.microsoft.com/en-us/azure/devops/pipelines/process/environments · https://learn.microsoft.com/en-us/azure/devops/artifacts/how-to/delete-and-recover-packages · https://learn.microsoft.com/en-us/azure/devops/artifacts/concepts/package-graph · https://learn.microsoft.com/en-us/azure/well-architected/operational-excellence/workload-supply-chain · https://learn.microsoft.com/en-us/azure/developer/azure-developer-cli/publishing-workflows