#177 Add retention policy knowledge to the privacy domain
Added guidance to the privacy domain in BCQuality about registering extension-owned tables for retention policies and shipping default retention policy setups, addressing common mistakes in how extensions handle log table cleanup.
- 8files
- 7AL files
- 0objects
Pull request · merged into main on 2026-10-05 by JeremyVyska · 8 files (+333 -2), 7 AL · feature · tier official · reviewed (checked by Opus)
What changed
- Two new knowledge articles in microsoft/knowledge/privacy/ with good and bad AL code examples
- Covers proper registration in both install and upgrade code with guards, and creating disabled default policy setups
- Addresses anti-patterns like hand-rolled DeleteAll and enabled policies without tenant approval
- Integrated into al-privacy-review skill for detection during code reviews
- References platform claims from BC admin documentation and the Retention Policy module
AL objects touched
microsoft/knowledge/privacy/register-owned-log-tables-for-retention-policies.bad.al: added, not in the BC? snapshot yetmicrosoft/knowledge/privacy/register-owned-log-tables-for-retention-policies.good.al: added, not in the BC? snapshot yetmicrosoft/knowledge/privacy/register-owned-log-tables-for-retention-policies.md: added, not in the BC? snapshot yetmicrosoft/knowledge/privacy/ship-a-default-retention-policy-setup.bad.al: added, not in the BC? snapshot yetmicrosoft/knowledge/privacy/ship-a-default-retention-policy-setup.good.al: added, not in the BC? snapshot yetmicrosoft/knowledge/privacy/ship-a-default-retention-policy-setup.md: added, not in the BC? snapshot yetmicrosoft/skills/review/al-privacy-review.md: modified, not in the BC? snapshot
Context
- Systems: administration, development
Source: metadata of a merged pull request in microsoft/BCQuality (bcquality): title, labels, changed paths and counts, with a summary in our words. No source text and no description beyond one short quote (D10, D61).