bcquality/microsoft/knowledge/privacy/table-level-data-classification-cascades.md
wenjiefan a668920e96 Correct table-level data classification guidance
Document that valid table-level classifications are inherited by fields and update the privacy fixture and related guidance accordingly.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
2026-08-17 13:16:12 +02:00

1.5 KiB

bc-version domain keywords technologies countries application-area
all
privacy
data-classification
table-level
field-inheritance
appsourcecop
as0016
false-positive
al
w1
all

Table-level DataClassification is inherited by fields

Description

A valid table-level DataClassification is the effective default for fields that do not declare their own value. A field-level value overrides that default only for the field on which it is set. AppSourceCop AS0016 accepts Normal fields that inherit a valid table classification; they do not remain ToBeClassified. FlowFields and FlowFilters are handled separately by the platform and are covered by flowfield-flowfilter-classification-systemmetadata.md.

Best Practice

Use a table-level classification when it accurately describes the table's fields, and add a field-level classification only where a field stores a different kind of data. Do not flag a Normal field solely because it omits an explicit property when its table supplies a valid default; verify whether the inherited value matches the field's data instead.

See sample: table-level-data-classification-cascades.good.al.

Anti Pattern

Reporting every Normal field without an explicit DataClassification when the table already supplies a valid default, or requiring redundant field-level declarations that repeat the table value. A real issue exists when neither scope supplies a valid classification, or when a field's data requires an override of the inherited value.