Privacy DataClassification fixes + keep Label-scope findings at minor#102
Merged
Conversation
JesperSchulz
approved these changes
Jul 14, 2026
There was a problem hiding this comment.
Pull request overview
This PR updates BCQuality’s AL guidance content to reduce false positives and improve severity calibration by correcting DataClassification defaults/coverage in the privacy knowledge article and ensuring label-scope findings remain actionable (minor) rather than suppressed (info) in the AL style review skill.
Changes:
- Corrected the privacy article to state that omitting
DataClassificationdefaults toToBeClassified, and clarified that bothToBeClassifiedandSystemMetadatacan be under-classifications when the field contains sensitive data. - Expanded the privacy article’s taxonomy guidance to include organization identifiers (
OrganizationIdentifiableInformation) and financial account identifiers (AccountData). - Updated AL style severity calibration so “Labels declared procedure-local instead of object scope” is treated as
minor(explicitly noting no analyzer enforces label scope), rather than being grouped with analyzer-enforcedinfoitems.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| microsoft/skills/review/al-style-review.md | Adjusts severity calibration text so label-scope findings remain minor (non-analyzer-enforced but with downstream translation impact). |
| microsoft/knowledge/privacy/data-classification-required-on-pii-fields.md | Fixes DataClassification default behavior and broadens recommended classifications to cover org/account identifiers. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Two data-grounded fixes from the online-eval false-positive analysis, targeting the worst-scoring cited articles.
1. Privacy article:
privacy/data-classification-required-on-pii-fields.mdThis article had 6 findings, 0 TP / 6 FP.
a. Correct the platform default (factual fix). The Description claimed the default value is
SystemMetadata. In AL, whenDataClassificationis omitted, the platform appliesToBeClassified(a "not yet reviewed" placeholder), notSystemMetadata. The wrong statement made the model fabricate contradictory consequences across findings (one claimed the default wasSystemMetadata, anotherToBeClassified), undermining credibility. Now states: omission →ToBeClassified; and both leaving PII asToBeClassifiedand settingSystemMetadatato silence the requirement are under-classifications.b. Broaden the classification taxonomy (scope fix). Best Practice only listed personal-PII values. Real findings flagged organization/account identifiers (a BE company VAT/registration number; a Swiss QR-Bill IBAN) with no correct value to point at. Added: company registration / VAT number →
OrganizationIdentifiableInformation; bank account number / IBAN →AccountData.2. Style skill:
skills/review/al-style-review.md(correction to the B1 severity-calibration paragraph)The B1 calibration listed "a
Labeldeclared at local instead of object scope" among conventions "a formal analyzer already flags", routing it toinfo(below the engine's Medium floor → dropped). Verified against the eval data this is wrong:labels-declared-at-object-scope.mdarticle cites no CodeCop rule (the other calibrated items all cite AA0248 / AA0074 / AA0218 / AA0002); its rationale is translation-pipeline fragility, a tooling concern the compiler does not check.infowould suppress genuinely valuable, adopted findings.Fix: move label-scope out of the analyzer-flagged (
info) list and into theminorlist ("concrete downstream impact the analyzer does not catch"), with a note that no analyzer enforces label scope. The other three calibrated items (AA0248/AA0218/AA0002) are correctly analyzer-enforced and stay atinfo.Scope
Privacy article: Description + Best Practice only (Anti Pattern and AL samples unchanged). Style skill: one sentence in the severity-calibration paragraph.