{"title":"AppSourceCop Warning AS0092","url":"https://jonas-paprotka.de/docs/dev-itpro/developer/analyzers/appsourcecop-as0092/","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/developer/analyzers/appsourcecop-as0092, 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/developer/analyzers/appsourcecop-as0092","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":"The app.json file must specify an Azure Application Insights resource for monitoring operations related to this extension.","date":"2026-10-01","meta":{"topic":"reference"},"outline":[{"level":1,"title":"AppSourceCop Warning AS0092","slug":"appsourcecop-warning-as0092","at":0,"chars":3109},{"level":2,"title":"Description","slug":"description","at":101,"chars":271},{"level":2,"title":"How to fix this diagnostic?","slug":"how-to-fix-this-diagnostic","at":372,"chars":1333},{"level":3,"title":"When targeting runtime version 7.2 or higher?","slug":"when-targeting-runtime-version-72-or-higher","at":819,"chars":430},{"level":3,"title":"When targeting a runtime version lower than 7.2?","slug":"when-targeting-a-runtime-version-lower-than-72","at":1249,"chars":456},{"level":2,"title":"Code examples triggering the rule","slug":"code-examples-triggering-the-rule","at":1705,"chars":660},{"level":2,"title":"Benefits of using the Application Insights","slug":"benefits-of-using-the-application-insights","at":2365,"chars":177},{"level":2,"title":"Usage of Application Insights during the validation of AppSource submissions","slug":"usage-of-application-insights-during-the-validation-of-appsource-submissions","at":2542,"chars":420},{"level":2,"title":"Related information","slug":"related-information","at":2962,"chars":147}],"text":"# AppSourceCop Warning AS0092\nThe app.json file must specify an Azure Application Insights resource.\n## Description\nThe app.json file must specify an Azure Application Insights resource for monitoring operations related to this extension. See https://learn.microsoft.com/dynamics365/business-central/dev-itpro/administration/telemetry-overview for additional information.\n## How to fix this diagnostic?\nThis diagnostic can be fixed by specifying an Azure Application Insights resource for the extension.\nFor more information about enabling Application Insights, see Monitoring and Analyzing Telemetry<../../administration/telemetry-overview> and Environment Telemetry<../../administration/tenant-admin-center-telemetry>.\nFor additional information about the manifest of extensions (app.json), see ../devenv-json-files.\n### When targeting runtime version 7.2 or higher?\nIf your extension is targeting runtime `7.2` (i.e. Business Central 2021 release wave 1 update 18.2), you can fix this diagnostic by specifying the connection string of the Azure Application Insights resource setup to monitor the operations related to this extension.\n```json\n{\n    \"applicationInsightsConnectionString\": \"<your-azure-application-insight-connection-string>\"\n}\n```\n### When targeting a runtime version lower than 7.2?\nIf your extension is targeting a lower runtime version than `7.2`, you can fix this diagnostic by specifying the instrumentation key of the Azure Application Insights resource setup to monitor the operations related to this extension.\nOr before `7.2` - Business Central 2021 release wave 1 update 18.2:\n```json\n{\n    \"applicationInsightsKey\": \"<your-azure-application-insight-instrumentationKey>\"\n}\n```\n## Code examples triggering the rule\nThis rule is triggered when both the 'applicationInsightsConnection' and the 'applicationInsightsKey' properties are not specified in the manifest (app.json) of the extension, or when its value is set to the empty string/GUID as shown below:\n```json\n{\n    \"applicationInsightsConnectionString\": \"\"\n}\n```\n```json\n{\n    \"applicationInsightsKey\": \"00000000-0000-0000-0000-000000000000\"\n}\n```\nThis rule is also triggered when specifying 'applicationInsightsKey' and targeting a runtime version higher or equal to `7.2`.\n```json\n{\n    \"applicationInsightsKey\": \"241514be-e378-4455-a2d3-bf7e40b7d41d\",\n    \"runtime\": \"7.2\"\n}\n```\n## Benefits of using the Application Insights\nUsing Application Insights provides telemetry to troubleshoot, understand, and fix issues related to your extension in production.\n## Usage of Application Insights during the validation of AppSource submissions\nThe Azure Application Insights resource specified in the manifest of the extension submitted to AppSource will be used to log detailed information about the validation process for your AppSource submission. See Analyzing AppSource Submission Validation Trace Telemetry<../../administration/telemetry-appsource-submission-validation-trace>.\n## Related information\nAppSourceCop Analyzer<appsourcecop>\nGet Started with AL<../devenv-get-started>\nDeveloping Extensions<../devenv-dev-overview>"}