bcquality/microsoft/knowledge/privacy/resolve-tobeclassified-before-release.md
Jesper Schulz-Wedde 5bcdc55df9 Sync knowledge articles with review agent instructions
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
2026-05-05 14:08:32 +02:00

1 KiB

bc-version domain keywords technologies countries application-area
all
privacy
tobeclassified
dataclassification
release
gdpr
placeholder
al
w1
all

Resolve ToBeClassified before release

Description

DataClassification = ToBeClassified is a development marker, not a releasable privacy state. It tells reviewers and tooling that the field still needs classification work. Shipping it prevents data-subject, retention, and telemetry tooling from making a correct decision about the field.

Best Practice

Replace every ToBeClassified value with the narrowest accurate classification before the PR ships to customers. If the field inherits a correct table-level DataClassification, remove the placeholder rather than leaving a field-level ToBeClassified override.

Anti Pattern

Treating ToBeClassified as a safe default because the field is new or because the final classification is uncertain. Uncertainty should bias toward a stronger classification, not toward an unresolved placeholder.