{"title":"Analyzing extension upload validation telemetry","url":"https://jonas-paprotka.de/docs/dev-itpro/administration/telemetry-pte-upload-validation-trace/","by":"JOP-AL","license":"Copyright (c) Microsoft Corporation. CC BY 4.0, https://creativecommons.org/licenses/by/4.0/; code samples MIT. From https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/administration/telemetry-pte-upload-validation-trace, MicrosoftDocs/dynamics365smb-devitpro-pb at 828b6ee (2026-11-19). Changed: includes filled in, links to this site, and for agents shortened without dropping a fact.","credit":"Microsoft Corporation, CC BY 4.0","origin":"https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/administration/telemetry-pte-upload-validation-trace","source":{"name":"Business Central developer and IT pro docs","repo":"https://github.com/MicrosoftDocs/dynamics365smb-devitpro-pb","commit":"828b6ee72fcd75755627cd6011f3d20899217ab2","date":"2026-11-19"},"checked":"2026-11-19","description":"Analyze Business Central per-tenant extension upload validation telemetry to track validation attempts, investigate failures, and configure alerts.","date":"2026-11-17","meta":{"topic":"concept-article"},"outline":[{"level":1,"title":"Analyzing extension upload validation telemetry","slug":"analyzing-extension-upload-validation-telemetry","at":0,"chars":20463},{"level":2,"title":"Per-tenant extension (PTE) validation started (LC0200)","slug":"per-tenant-extension-pte-validation-started-lc0200","at":1783,"chars":1054},{"level":3,"title":"General dimensions","slug":"general-dimensions","at":1936,"chars":192},{"level":3,"title":"Custom dimensions","slug":"custom-dimensions","at":2128,"chars":709},{"level":2,"title":"PTE submission diagnostic reported (LC0201)","slug":"pte-submission-diagnostic-reported-lc0201","at":2837,"chars":1649},{"level":3,"title":"General dimensions","slug":"general-dimensions-1","at":3143,"chars":195},{"level":3,"title":"Custom dimensions","slug":"custom-dimensions-1","at":3338,"chars":1148},{"level":2,"title":"Extension validation started (LC0204)","slug":"extension-validation-started-lc0204","at":4486,"chars":1466},{"level":3,"title":"General dimensions","slug":"general-dimensions-2","at":4629,"chars":466},{"level":3,"title":"Custom dimensions","slug":"custom-dimensions-2","at":5095,"chars":857},{"level":2,"title":"Extension validation completed successfully (LC0205)","slug":"extension-validation-completed-successfully-lc0205","at":5952,"chars":1455},{"level":3,"title":"General dimensions","slug":"general-dimensions-3","at":6069,"chars":481},{"level":3,"title":"Custom dimensions","slug":"custom-dimensions-3","at":6550,"chars":857},{"level":2,"title":"Extension validation diagnostic reported (LC0210)","slug":"extension-validation-diagnostic-reported-lc0210","at":7407,"chars":3261},{"level":3,"title":"General dimensions","slug":"general-dimensions-4","at":7544,"chars":468},{"level":3,"title":"Custom dimensions","slug":"custom-dimensions-4","at":8012,"chars":1402},{"level":3,"title":"Sample KQL code (Extension Validation diagnostic reported)","slug":"sample-kql-code-extension-validation-diagnostic-reported","at":9414,"chars":1254},{"level":2,"title":"Extension validation completed with failures (LC0206)","slug":"extension-validation-completed-with-failures-lc0206","at":10668,"chars":1535},{"level":3,"title":"General dimensions","slug":"general-dimensions-5","at":10792,"chars":482},{"level":3,"title":"Custom dimensions","slug":"custom-dimensions-5","at":11274,"chars":929},{"level":2,"title":"Dependent extension validation started (LC0207)","slug":"dependent-extension-validation-started-lc0207","at":12203,"chars":1539},{"level":3,"title":"General dimensions","slug":"general-dimensions-6","at":12409,"chars":466},{"level":3,"title":"Custom dimensions","slug":"custom-dimensions-6","at":12875,"chars":867},{"level":2,"title":"Dependent extension validation completed successfully (LC0208)","slug":"dependent-extension-validation-completed-successfully-lc0208","at":13742,"chars":1479},{"level":3,"title":"General dimensions","slug":"general-dimensions-7","at":13879,"chars":481},{"level":3,"title":"Custom dimensions","slug":"custom-dimensions-7","at":14360,"chars":861},{"level":2,"title":"Dependent extension validation completed with failures (LC0209)","slug":"dependent-extension-validation-completed-with-failures-lc0209","at":15221,"chars":1569},{"level":3,"title":"General dimensions","slug":"general-dimensions-8","at":15365,"chars":482},{"level":3,"title":"Custom dimensions","slug":"custom-dimensions-8","at":15847,"chars":943},{"level":2,"title":"Per-tenant extension (PTE) validation completed successfully (LC0202)","slug":"per-tenant-extension-pte-validation-completed-successfully-lc0202","at":16790,"chars":1146},{"level":3,"title":"General dimensions","slug":"general-dimensions-9","at":17006,"chars":226},{"level":3,"title":"Custom dimensions","slug":"custom-dimensions-9","at":17232,"chars":704},{"level":2,"title":"Per-tenant extension (PTE) validation completed with failures (LC0203)","slug":"per-tenant-extension-pte-validation-completed-with-failures-lc0203","at":17936,"chars":2362},{"level":3,"title":"General dimensions","slug":"general-dimensions-10","at":18159,"chars":208},{"level":3,"title":"Custom dimensions","slug":"custom-dimensions-10","at":18367,"chars":779},{"level":3,"title":"Sample KQL code (per-tenant extension (PTE) validation completed with failures)","slug":"sample-kql-code-per-tenant-extension-pte-validation-completed-with-failures","at":19146,"chars":1152},{"level":2,"title":"Related information","slug":"related-information","at":20298,"chars":165}],"text":"# Analyzing extension upload validation telemetry\n> APPLIES TO: Business Central online\nIn the Business Central service, when a user or administrator uploads a per-tenant extension to an environment from the Extension Management page, Business Central proactively validates it against the environment.\nWith this telemetry, partners can monitor these attempts for customers and set up alerts on failures so that they know up-front which customers will need help.\nFailed operations result in a trace log entry that includes a reason for the failure.\nThe validation flow is as follows:\n```text\nThe PTE submission validation flow is as follows:\n\nPTE submission validation request started (LC0200). This includes the main extension to be validated and a list of extensions it depends on.\nFor each extension (main + dependent extensions)\n        For the main extension:\n                Extension validation started (LC0204)\n                Either\n                        Extension validation completed successfully (LC0205)\n                or\n                        Validation diagnostic reported (LC0210)\n                        Extension validation completed with failures (LC0206)\n        For each dependent extension:\n                Dependent extension validation started (LC0207)\n                Either\n                        Dependent extension validation completed successfully (LC0208)\n                or\n                        Validation diagnostic reported (LC0210)\n                        Dependent extension validation completed with failures (LC0209)\n\nThen either\n        PTE submission validation request completed successfully (LC0202)\nor\n        PTE submission diagnostic reported (LC0201)\n        PTE submission validation request completed with failures (LC0203)\n```\n## Per-tenant extension (PTE) validation started (LC0200)\nOccurs when a new per-tenant extension (PTE) validation attempt is started on the environment.\n### General dimensions\nDimension|Description or value\nmessage|PTE validation started: request {submissionId} <br /><br /> `{submissionId}` indicates the identifier for the validation attempt.\n### Custom dimensions\nDimension|Description or value\neventId|LC0200\nenvironmentId|Specifies the Microsoft Entra tenant ID used for Microsoft Entra authentication. For on-premises, if you aren't using Microsoft Entra authentication, this value is common.\nenvironmentName|Specifies the name of the tenant environment. See Managing Environments<tenant-admin-center-environments>.\nenvironmentType|Specifies the environment type for the tenant, such as Production or Sandbox. See tenant-admin-center-environments#types-of-environments.\nmainExtension|A JSON structure that contains information about the extension that is being uploaded.\nsubmissionOperationId|A unique identifier (GUID) for the validation attempt.\n## PTE submission diagnostic reported (LC0201)\nOccurs during the PTE submission validation request to report diagnostics related to the submission itself. For example, it could be that a submission has duplicate object IDs. This signal isn't necessarily an error, but can also be a warning or information.\n### General dimensions\nDimension|Description or value\nmessage|Diagnostic reported on PTE submission validation request: {submissionId}\nseverityLevel|1 for information, 2 for warning, 3 for error\n### Custom dimensions\nDimension|Description or value\neventId|LC0201\nenvironmentId|Specifies the Microsoft Entra tenant ID used for Microsoft Entra authentication. For on-premises, if you aren't using Microsoft Entra authentication, this value is common.\nenvironmentName|Specifies the name of the tenant environment. See Managing Environments<tenant-admin-center-environments>.\nenvironmentType|Specifies the environment type for the tenant, such as Production or Sandbox. See tenant-admin-center-environments#types-of-environments.\nmainExtension|A JSON structure that contains information about the extension that is being uploaded.\nsubmissionOperationId|A unique identifier (GUID) for the validation attempt.\ndependentExtensions|A JSON structure that contains information about the dependent extensions.\ndiagnosticCode|Specifies a diagnostics code emitted by the AL compiler. See AL compiler diagnostics<../developer/diagnostics/diagnostics-overview>\ndiagnosticMessage|Specifies a diagnostics message emitted by the AL compiler.\ndiagnosticSeverity|Specifies the severity of diagnostics message emitted by the AL compiler, such as Error or Warning.\n## Extension validation started (LC0204)\nOccurs for each extension in the upload. This event is emitted for the main extension being uploaded.\n### General dimensions\nDimension|Description or value\nmessage|Extension validation started: extension {extensionName} version {extensionVersion} by {extensionPublisher} ({extensionId}) <br /><br /> `{extensionName}` indicates the name of the extension.<br /><br /> `{extensionVersion}` indicates the version of the extension.<br /><br /> `{extensionPublisher}` indicates the publisher of the extension.<br /><br /> `{extensionId}` indicates the ID of the extension.\n### Custom dimensions\nDimension|Description or value\neventId|LC0204\nenvironmentId|Specifies the Microsoft Entra tenant ID used for Microsoft Entra authentication. For on-premises, if you aren't using Microsoft Entra authentication, this value is common.\nenvironmentName|Specifies the name of the tenant environment. See Managing Environments<tenant-admin-center-environments>.\nenvironmentType|Specifies the environment type for the tenant, such as Production or Sandbox. See tenant-admin-center-environments#types-of-environments.\nextensionName|Specifies the name of the extension that was to be validated.\nextensionId|Specifies the ID of the extension/app.\nextensionPublisher|Specifies the publisher of the extension/app.\nextensionVersion|Specifies the version of the extension.\nsubmissionOperationId|A unique identifier (GUID) for the validation attempt.\n## Extension validation completed successfully (LC0205)\nOccurs if the extension can compile against the environment.\n### General dimensions\nDimension|Description or value\nmessage|Extension validation completed successfully: extension {extensionName} version {extensionVersion} by {extensionPublisher} ({extensionId}) <br /><br /> `{extensionName}` indicates the name of the extension.<br /><br /> `{extensionVersion}` indicates the version of the extension.<br /><br /> `{extensionPublisher}` indicates the publisher of the extension.<br /><br /> `{extensionId}` indicates the ID of the extension.\n### Custom dimensions\nDimension|Description or value\neventId|LC0205\nenvironmentId|Specifies the Microsoft Entra tenant ID used for Microsoft Entra authentication. For on-premises, if you aren't using Microsoft Entra authentication, this value is common.\nenvironmentName|Specifies the name of the tenant environment. See Managing Environments<tenant-admin-center-environments>.\nenvironmentType|Specifies the environment type for the tenant, such as Production or Sandbox. See tenant-admin-center-environments#types-of-environments.\nextensionName|Specifies the name of the extension that was to be validated.\nextensionId|Specifies the ID of the extension/app.\nextensionPublisher|Specifies the publisher of the extension/app.\nextensionVersion|Specifies the version of the extension.\nsubmissionOperationId|A unique identifier (GUID) for the validation attempt.\n## Extension validation diagnostic reported (LC0210)\nOccurs if something was not right when validating the extension on the environment.\n### General dimensions\nDimension|Description or value\nmessage|Validation diagnostic reported: extension {extensionName} version {extensionVersion} by {extensionPublisher} ({extensionId}) <br /><br /> `{extensionName}` indicates the name of the extension.<br /><br /> `{extensionVersion}` indicates the version of the extension.<br /><br /> `{extensionPublisher}` indicates the publisher of the extension.<br /><br /> `{extensionId}` indicates the id of the extension.\n### Custom dimensions\nDimension|Description or value\neventId|LC0210\nenvironmentId|Specifies the Microsoft Entra tenant ID used for Microsoft Entra authentication. For on-premises, if you aren't using Microsoft Entra authentication, this value is common.\nenvironmentName|Specifies the name of the tenant environment. See Managing Environments<tenant-admin-center-environments>.\nenvironmentType|Specifies the environment type for the tenant, such as Production or Sandbox. See tenant-admin-center-environments#types-of-environments.\nextensionName|Specifies the name of the extension that was to be validated.\nextensionId|Specifies the ID of the extension/app.\nextensionPublisher|Specifies the publisher of the extension/app.\nextensionVersion|Specifies the version of the extension.\ndiagnosticCode|Specifies a diagnostics code emitted by the AL compiler. See AL compiler diagnostics<../developer/diagnostics/diagnostics-overview>\ndiagnosticMessage|Specifies a diagnostics message emitted by the AL compiler.\ndiagnosticSeverity|Specifies the severity of diagnostics message emitted by the AL compiler, such as Error or Warning.\ndiagnosticSourceLocation|Specifies where in the app code the AL compiler emitted the diagnostics.\ndiagnosticSourcePath|Specifies where in a file in the app the AL compiler emitted the diagnostics.\nsubmissionOperationId|The operation ID for the validation submission of the app.\n### Sample KQL code (Extension Validation diagnostic reported)\nThis KQL code can help you get started analyzing validation failures for an extension/app:\n```kql\n// Extension Validation diagnostic reported (LC0210)\ntraces\n| where customDimensions has \"LC0210\"\n| where customDimensions.eventId == \"LC0210\"\n| where timestamp > ago(30d) // adjust as needed\n| project timestamp\n// which environment is being validated\n, aadTenantId = customDimensions.environmentId\n, environmentName = customDimensions.environmentName\n, environmentType = customDimensions.environmentType\n// which extension/app is being validated\n, extensionId = customDimensions.extensionId\n, extensionPublisher = customDimensions.extensionPublisher\n, extensionVersion = customDimensions.extensionVersion\n, extensionName = customDimensions.extensionName\n, mainExtension = customDimensions.mainExtension\n// validation info\n, diagnosticSourceLocation = customDimensions.diagnosticSourceLocation\n, diagnosticMessage = customDimensions.diagnosticMessage\n, diagnosticSourcePath = customDimensions.diagnosticSourcePath\n, diagnosticCode = customDimensions.diagnosticCode\n, diagnosticSeverity = customDimensions.diagnosticSeverity\n, submissionOperationId = customDimensions.submissionOperationId\n```\n## Extension validation completed with failures (LC0206)\nOccurs if the extension could not compile against the environment.\n### General dimensions\nDimension|Description or value\nmessage|Extension validation completed with failures: extension {extensionName} version {extensionVersion} by {extensionPublisher} ({extensionId}) <br /><br /> `{extensionName}` indicates the name of the extension.<br /><br /> `{extensionVersion}` indicates the version of the extension.<br /><br /> `{extensionPublisher}` indicates the publisher of the extension.<br /><br /> `{extensionId}` indicates the ID of the extension.\n### Custom dimensions\nDimension|Description or value\neventId|LC0206\nenvironmentId|Specifies the Microsoft Entra tenant ID used for Microsoft Entra authentication. For on-premises, if you aren't using Microsoft Entra authentication, this value is common.\nenvironmentName|Specifies the name of the tenant environment. See Managing Environments<tenant-admin-center-environments>.\nenvironmentType|Specifies the environment type for the tenant, such as Production or Sandbox. See tenant-admin-center-environments#types-of-environments.\nextensionName|Specifies the name of the extension that was to be validated.\nextensionId|Specifies the ID of the extension/app.\nextensionPublisher|Specifies the publisher of the extension/app.\nextensionVersion|Specifies the version of the extension.\nsubmissionOperationId|A unique identifier (GUID) for the validation attempt.\nfailureReason|The overall reason that the extension failed to validate.\n## Dependent extension validation started (LC0207)\nOccurs for each dependent extension in the upload. This event is emitted for extensions that the main extension depends on, not the main extension itself.\n### General dimensions\nDimension|Description or value\nmessage|Extension validation started: extension {extensionName} version {extensionVersion} by {extensionPublisher} ({extensionId}) <br /><br /> `{extensionName}` indicates the name of the extension.<br /><br /> `{extensionVersion}` indicates the version of the extension.<br /><br /> `{extensionPublisher}` indicates the publisher of the extension.<br /><br /> `{extensionId}` indicates the ID of the extension.\n### Custom dimensions\nDimension|Description or value\neventId|LC0207\nenvironmentId|Specifies the Microsoft Entra tenant ID used for Microsoft Entra authentication. For on-premises, if you aren't using Microsoft Entra authentication, this value is common.\nenvironmentName|Specifies the name of the tenant environment. See Managing Environments<tenant-admin-center-environments>.\nenvironmentType|Specifies the environment type for the tenant, such as Production or Sandbox. See tenant-admin-center-environments#types-of-environments.\nextensionName|Specifies the name of the dependent extension that was to be validated.\nextensionId|Specifies the ID of the extension/app.\nextensionPublisher|Specifies the publisher of the extension/app.\nextensionVersion|Specifies the version of the extension.\nsubmissionOperationId|A unique identifier (GUID) for the validation attempt.\n## Dependent extension validation completed successfully (LC0208)\nOccurs if the dependent extension can compile against the environment.\n### General dimensions\nDimension|Description or value\nmessage|Extension validation completed successfully: extension {extensionName} version {extensionVersion} by {extensionPublisher} ({extensionId}) <br /><br /> `{extensionName}` indicates the name of the extension.<br /><br /> `{extensionVersion}` indicates the version of the extension.<br /><br /> `{extensionPublisher}` indicates the publisher of the extension.<br /><br /> `{extensionId}` indicates the ID of the extension.\n### Custom dimensions\nDimension|Description or value\neventId|LC0208\nenvironmentId|Specifies the Microsoft Entra tenant ID used for Microsoft Entra authentication. For on-premises, if you aren't using Microsoft Entra authentication, this value is common.\nenvironmentName|Specifies the name of the tenant environment. See Managing Environments<tenant-admin-center-environments>.\nenvironmentType|Specifies the environment type for the tenant, such as Production or Sandbox. See tenant-admin-center-environments#types-of-environments.\nextensionName|Specifies the name of the dependent extension that was validated.\nextensionId|Specifies the ID of the extension/app.\nextensionPublisher|Specifies the publisher of the extension/app.\nextensionVersion|Specifies the version of the extension.\nsubmissionOperationId|A unique identifier (GUID) for the validation attempt.\n## Dependent extension validation completed with failures (LC0209)\nOccurs if the dependent extension could not compile against the environment.\n### General dimensions\nDimension|Description or value\nmessage|Extension validation completed with failures: extension {extensionName} version {extensionVersion} by {extensionPublisher} ({extensionId}) <br /><br /> `{extensionName}` indicates the name of the extension.<br /><br /> `{extensionVersion}` indicates the version of the extension.<br /><br /> `{extensionPublisher}` indicates the publisher of the extension.<br /><br /> `{extensionId}` indicates the ID of the extension.\n### Custom dimensions\nDimension|Description or value\neventId|LC0209\nenvironmentId|Specifies the Microsoft Entra tenant ID used for Microsoft Entra authentication. For on-premises, if you aren't using Microsoft Entra authentication, this value is common.\nenvironmentName|Specifies the name of the tenant environment. See Managing Environments<tenant-admin-center-environments>.\nenvironmentType|Specifies the environment type for the tenant, such as Production or Sandbox. See tenant-admin-center-environments#types-of-environments.\nextensionName|Specifies the name of the dependent extension that was validated.\nextensionId|Specifies the ID of the extension/app.\nextensionPublisher|Specifies the publisher of the extension/app.\nextensionVersion|Specifies the version of the extension.\nsubmissionOperationId|A unique identifier (GUID) for the validation attempt.\nfailureReason|The overall reason that the dependent extension failed to validate.\n## Per-tenant extension (PTE) validation completed successfully (LC0202)\nOccurs when a per-tenant extension (PTE) validation attempt is completed successfully on the environment (so that the extension was uploaded).\n### General dimensions\nDimension|Description or value\nmessage|PTE submission validation request completed successfully: request {submissionId} <br /><br /> `{submissionId}` indicates the identifier for the validation attempt.\n### Custom dimensions\nDimension|Description or value\neventId|LC0202\nenvironmentId|Specifies the Microsoft Entra tenant ID used for Microsoft Entra authentication. For on-premises, if you aren't using Microsoft Entra authentication, this value is common.\nenvironmentName|Specifies the name of the tenant environment. See Managing Environments<tenant-admin-center-environments>.\nenvironmentType|Specifies the environment type for the tenant, such as Production or Sandbox. See tenant-admin-center-environments#types-of-environments.\nmainExtension|A JSON structure that contains information about the extension that was uploaded.\nsubmissionOperationId|A unique identifier (GUID) for the validation attempt.\n## Per-tenant extension (PTE) validation completed with failures (LC0203)\nOccurs when a new per-tenant extension (PTE) validation attempt completed with failures on the environment (so that the extension was not uploaded).\n### General dimensions\nDimension|Description or value\nmessage|PTE validation completed with failures: request {submissionId} <br /><br /> `{submissionId}` indicates the identifier for the validation attempt.\n### Custom dimensions\nDimension|Description or value\neventId|LC0203\nenvironmentId|Specifies the Microsoft Entra tenant ID used for Microsoft Entra authentication. For on-premises, if you aren't using Microsoft Entra authentication, this value is common.\nenvironmentName|Specifies the name of the tenant environment. See Managing Environments<tenant-admin-center-environments>.\nenvironmentType|Specifies the environment type for the tenant, such as Production or Sandbox. See tenant-admin-center-environments#types-of-environments.\nmainExtension|A JSON structure that contains information about the extension that is being uploaded.\nsubmissionOperationId|A unique identifier (GUID) for the validation attempt.\nfailureReason|The overall reason that the extension failed to upload.\n### Sample KQL code (per-tenant extension (PTE) validation completed with failures)\nThis KQL code can help you get started analyzing validation failures for uploading an extension to the environment:\n```kql\n// PTE submission validation request completed with failures: request <submission id>\ntraces\n| where customDimensions has \"LC0203\"\n| where customDimensions.eventId == \"LC0203\"\n| where timestamp > ago(30d) // adjust as needed\n| extend mainExtension = parse_json(tostring( customDimensions.mainExtension ))\n| project timestamp\n// in which environment is the extension being validated\n, aadTenantId = customDimensions.aadTenantId\n, environmentId = customDimensions.environmentId\n, environmentName = customDimensions.environmentName\n// which extension/app is being validated\n, mainExtensionId = mainExtension.Id\n, mainExtensionPublisher = mainExtension.Publisher\n, mainExtensionVersion = mainExtension.Version\n, mainExtensionName = mainExtension.Name\n, dependentExtensions = customDimensions.dependentExtensions\n// validation info\n, submissionOperationId = customDimensions.submissionOperationId\n, failureReason = customDimensions.failureReason\n```\n## Related information\nMonitoring and Analyzing Telemetry<telemetry-overview>\nEnable Sending Telemetry to Application Insights<telemetry-enable-application-insights>"}