Use a single, deterministic naming scheme for every content identifier, and follow the validator’s allowed formats.
Apply these rules: 1) Follow exact format/allowed-value rules for metadata/ids
^[a-z][a-z0-9]{0,49}$.publisherId.offerId.dnsresolution).id: use the agreed pattern (e.g., ProviderNameApplianceName).2) Enforce casing conventions for content fields
QualysHostDetectionV2_CL).description for each column.3) Treat stable customer keys as immutable
4) Handle reserved words and mapping consistency
title), escape/quote consistently in the schema and keep the KQL transform aligned.Example patterns
"publisherId": "securityscorecard", "offerId": "securityscorecard" (lowercase, regex-safe)"entities": ["dnsresolution", "IP", "URL"]"name": "QualysHostDetectionV2_CL" and column "name": "TimeGenerated" (PascalCase) with description.{ "name": "['title']", "type": "string" }TimeGenerated when required).5) Don’t “simplify” deterministic packaging outputs