{"title":"Analyzing Azure Function integration telemetry","url":"https://jonas-paprotka.de/docs/dev-itpro/administration/telemetry-azure-function-integration-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-azure-function-integration-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-azure-function-integration-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 Azure Function integration telemetry in Business Central to monitor successful requests, failed requests, and OAuth authorization failures.","date":"2026-11-17","meta":{"topic":"reference"},"outline":[{"level":1,"title":"Analyzing Azure Function integration telemetry","slug":"analyzing-azure-function-integration-telemetry","at":0,"chars":4834},{"level":2,"title":"Custom dimensions available in all events","slug":"custom-dimensions-available-in-all-events","at":598,"chars":1426},{"level":2,"title":"Request sent to Azure function succeeded","slug":"request-sent-to-azure-function-succeeded","at":2024,"chars":352},{"level":3,"title":"General dimensions","slug":"general-dimensions","at":2151,"chars":103},{"level":3,"title":"Custom dimensions","slug":"custom-dimensions","at":2254,"chars":122},{"level":2,"title":"Request sent to Azure function failed","slug":"request-sent-to-azure-function-failed","at":2376,"chars":1009},{"level":3,"title":"General dimensions","slug":"general-dimensions-1","at":2497,"chars":118},{"level":3,"title":"Custom dimensions","slug":"custom-dimensions-1","at":2615,"chars":122},{"level":3,"title":"Sample KQL code","slug":"sample-kql-code","at":2737,"chars":648},{"level":2,"title":"Authorization failed to Azure function","slug":"authorization-failed-to-azure-function","at":3385,"chars":1097},{"level":3,"title":"General dimensions","slug":"general-dimensions-2","at":3551,"chars":119},{"level":3,"title":"Custom dimensions","slug":"custom-dimensions-2","at":3670,"chars":168},{"level":3,"title":"Sample KQL code","slug":"sample-kql-code-1","at":3838,"chars":644},{"level":2,"title":"Related information","slug":"related-information","at":4482,"chars":352}],"text":"# Analyzing Azure Function integration telemetry\nAzure Function integration telemetry gathers data about the success or failure of calls from Business Central to Azure Functions using the Azure Function module<https://github.com/microsoft/BCApps/tree/main/src/System%20Application/App/Azure%20Function> in the System Application.\nFailed operations result in a trace log entry that includes a reason for the failure.\nThese events use `TelemetryScope::All`. Successful requests use normal verbosity (severityLevel 1). Failed requests and authorization failures use error verbosity (severityLevel 3).\n## Custom dimensions available in all events\nThe following dimensions can be available in all events described below and aren't included in the individual event documentation. Some dimensions depend on the environment or the session's permissions.\nDimension|Description or value\naadTenantId|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.\nalCountryCode|Specifies the localization for the environment, such as US or DK.\nalFunctionHost|The host name of the Azure function called from Business Central, without the URL scheme or path.\nalIsAdmin|Whether the current user is a tenant admin or delegated admin.\nalIsEvaluationCompany|Whether the current company is an evaluation company.\nalTenantLicenseState|The license state of the tenant, such as Paid, Trial, Suspended, or Warning.\nclientType|Specifies the type of client that opened the session, such as Background or Web. For a list of the client types, see ClientType Option Type<../developer/methods-auto/clienttype/clienttype-option>.\ncompanyName|The current company name.\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.\n## Request sent to Azure function succeeded\nOccurs when a request to an Azure function on the host {alFunctionHost} succeeded.\n### General dimensions\nDimension|Description or value\nmessage|Request sent to Azure function succeeded\n### Custom dimensions\nDimension|Description or value\neventId|AL0000I74\nalStatusCode|The HTTP status code for the request.\n## Request sent to Azure function failed\nOccurs when a request to an Azure function on the host {alFunctionHost} failed.\n### General dimensions\nDimension|Description or value\nmessage|Request sent to Azure function failed: {alFunctionHost}\n### Custom dimensions\nDimension|Description or value\neventId|AL0000I7P\nalStatusCode|The HTTP status code for the request.\n### Sample KQL code\nThis KQL code can help you get started analyzing and alerting on request failures to Azure functions:\n```kql\ntraces\n| where timestamp > ago(5d) // adjust as needed\n| where customDimensions.eventId == 'AL0000I7P'\n| project timestamp\n, aadTenantId = customDimensions.aadTenantId\n, environmentName = customDimensions.environmentName\n, environmentType = customDimensions.environmentType\n, companyName = customDimensions.companyName\n, requestStatusCode = customDimensions.alStatusCode\n, functionHost = customDimensions.alFunctionHost\n```\nTo learn more about how to set up alerting on Business Central telemetry, see telemetry-alert.\n## Authorization failed to Azure function\nOccurs when OAuth authentication with a client secret or certificate doesn't return an access token for the Azure function.\n### General dimensions\nDimension|Description or value\nmessage|Authorization failed to Azure function: {alFunctionHost}\n### Custom dimensions\nDimension|Description or value\neventId|AL0000I75\nalErrorText|Authorization failed to Azure function: {alFunctionHost}\nalEventName|Acquiring token\n### Sample KQL code\nThis KQL code can help you get started analyzing and alerting on failures to authorize to Azure functions:\n```kql\ntraces\n| where timestamp > ago(5d) // adjust as needed\n| where customDimensions.eventId == 'AL0000I75'\n| project timestamp\n, aadTenantId = customDimensions.aadTenantId\n, environmentName = customDimensions.environmentName\n, environmentType = customDimensions.environmentType\n, companyName = customDimensions.companyName\n, errorText = customDimensions.alErrorText\n, functionHost = customDimensions.alFunctionHost\n```\nTo learn more about how to set up alerting on Business Central telemetry, see telemetry-alert.\n## Related information\nMonitoring and Analyzing Telemetry<telemetry-overview>\nEnable Sending Telemetry to Application Insights<telemetry-enable-application-insights>\ntelemetry-alert\nConnecting to Azure Functions<https://github.com/microsoft/BCApps/tree/main/src/System%20Application/App/Azure%20Function>\n../developer/devenv-system-application-overview"}