Microsoft/bcquality
1
0
Fork 0
mirror of https://github.com/microsoft/BCQuality.git synced 2026-10-05 14:46:55 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions 4
bcquality/microsoft/knowledge/privacy/featuretelemetry-customdimensions-no-pii.md
Jesper Schulz-Wedde 2b5550c346
Some checks failed
Validate knowledge index / validate-index (push) Has been cancelled
Details
Validate AL review fixtures / validate-review-fixtures (push) Has been cancelled
Details
Validate frontmatter and structure / validate (push) Has been cancelled
Details
Improve partner onboarding and documentation navigation (#174) 
Lead with a complete plugin quick start and add task-oriented usage, troubleshooting, customization, and contribution guides. Preserve the broader plugin framing, correct conflicting contract guidance, support Agents folder reviews, and align repository validation. Convert existing sample references to clickable links without changing knowledge rules.

Co-authored-by: Jesper Schulz-Wedde <jesper.schulzwedde@microsoft.com>
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
2026-09-09 17:31:03 +02:00

1.8 KiB
Raw Blame History

bc-version domain keywords technologies countries application-area
all
privacy
feature-telemetry
customdimensions
logusage
loguptake
logerror
pii
euii
eupi
al
w1
all

FeatureTelemetry CustomDimensions follow the same privacy rules as Session.LogMessage

Description

Codeunit "Feature Telemetry" is the second telemetry surface in AL. Its methods — LogUsage(), LogUptake() and LogError() — each accept a CustomDimensions dictionary parameter whose contents are sent to telemetry as-is. The platform does not classify per-dimension values for you, so any customer or employee data placed into the dictionary is logged verbatim. The privacy rules that apply to Session.LogMessage message text apply to every value in CustomDimensions: no customer or employee names, email addresses, phone numbers (CustomerContent/EUII); no employee codes, user IDs or user security IDs (EUPI); no user-provided content (addresses, descriptions, notes); no GetLastErrorText() output.

Best Practice

Pass only non-personal context through CustomDimensions — feature names, status enums, counts, error codes, durations. For uptake or usage signals that do not need per-call context, prefer the parameterless overload of LogUptake/LogUsage over a CustomDimensions dictionary that risks accreting PII over time.

See sample: featuretelemetry-customdimensions-no-pii.good.al.

Anti Pattern

CustomDimensions.Add('EmployeeNo', ExpenseHeader."Employee No.") followed by FeatureTelemetry.LogUsage(...) — the employee number is a pseudonymous user identifier (EUPI) and is now in telemetry. Same pattern with 'UserName', 'CustomerEmail', 'AttachmentName' etc.

See sample: featuretelemetry-customdimensions-no-pii.bad.al.