bcquality/microsoft/knowledge/privacy/table-level-data-classification-cascades.md
Jesper Schulz-Wedde aca3986fd0
Correct security and privacy knowledge guidance (#92)
* Correct security and privacy guidance

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>

Copilot-Session: 9c2eebc4-dcd5-4b85-8113-90772d818900

* Address security privacy review findings

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>

Copilot-Session: 9c2eebc4-dcd5-4b85-8113-90772d818900

---------

Co-authored-by: Jesper Schulz-Wedde <jesper.schulzwedde@microsoft.com>
2026-07-14 11:25:03 +02:00

1.1 KiB

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

Set DataClassification on every Normal table field

Description

AppSourceCop AS0016 requires every field whose FieldClass is Normal to declare DataClassification and use a value other than ToBeClassified. A table-level DataClassification property does not satisfy that field-level requirement. FlowFields and FlowFilters are handled separately by the platform and are covered by flowfield-flowfilter-classification-systemmetadata.md.

Best Practice

Classify each Normal field according to the data it stores, even when every field in the table has the same classification. Repeat the property explicitly so AS0016 can verify every field.

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

Anti Pattern

Relying on DataClassification at table scope and leaving Normal fields unclassified. The table property does not cascade in the way AS0016 requires, so the fields still fail AppSourceCop validation.