{"title":"Analyzing web service access key telemetry","url":"https://jonas-paprotka.de/docs/dev-itpro/administration/telemetry-webservices-access-key-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-webservices-access-key-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-webservices-access-key-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 web service access key telemetry in Business Central to monitor authentication attempts, identify failures, and plan migration away from access keys.","date":"2026-11-17","meta":{"topic":"concept-article"},"outline":[{"level":1,"title":"Analyzing web service access key telemetry","slug":"analyzing-web-service-access-key-telemetry","at":0,"chars":6083},{"level":2,"title":"Authentication with web service key succeeded","slug":"authentication-with-web-service-key-succeeded","at":920,"chars":1882},{"level":3,"title":"General dimensions","slug":"general-dimensions","at":1038,"chars":281},{"level":3,"title":"Custom dimensions","slug":"custom-dimensions","at":1319,"chars":1483},{"level":2,"title":"Authentication with web service key failed","slug":"authentication-with-web-service-key-failed","at":2802,"chars":3116},{"level":3,"title":"General dimensions","slug":"general-dimensions-1","at":3070,"chars":278},{"level":3,"title":"Custom dimensions","slug":"custom-dimensions-1","at":3348,"chars":1609},{"level":3,"title":"Example trace","slug":"example-trace","at":4957,"chars":961},{"level":2,"title":"Related information","slug":"related-information","at":5918,"chars":165}],"text":"# Analyzing web service access key telemetry\nAPPLIES TO: Business Central 2020 release wave 2, version 17.3, and later\nThe Business Central emits telemetry data about the success or failure of authenticating web service access keys on web service requests.\n> IMPORTANT\n> Starting October, 2022, the use of access keys (Basic Auth) for web service authentication is deprecated and not supported<../upgrade/deprecated-features-platform#accesskeys> in Business Central online. We recommend that you use OAuth2 instead. See Using OAuth to Authorize Business Central Web Services<../webservices/authenticate-web-services-using-oauth>.\nAs a partner or customer, this data lets you monitor the use of web service access keys on your environments in preparation for the deprecation of the feature.\nSee How to use an Access Key for SOAP and OData Web Service Authentication<../webservices/web-services-authentication#accesskey>.\n## Authentication with web service key succeeded\nOccurs when a web service access key was authenticated successfully.\n### General dimensions\nThe following table explains the general dimensions included in the trace. The table lists the dimensions that are specific to Business Central.\nDimension|Description or value\nmessage|Authentication with Web Service Key succeeded: {endpoint}\nseverityLevel|1\n### Custom dimensions\nThe following table explains the custom dimensions included in the trace.\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.\nalObjectId|Specifies the ID of the AL object in the current context, if available. The authentication event occurs before the requested object runs.\nauthenticationStatus|Succeeded\nauthenticationType|Specifies whether the service uses NavUserPassword or AccessControl authentication.\ncategory|Specifies the service type. Values include: Api, ODataV4, ODataV3, and SOAP.\ncomponent|Dynamics 365 Business Central Server\ncomponentVersion|Specifies the version number of the component that emits telemetry (see the component dimension.)\ndeprecatedKeys|A comma-separated list of all the keys that have been deprecated. The keys in this list are still supported but will eventually be removed in the next major release. We recommend that you update any queries that use these keys to use the new key name.\nendpoint|Specifies the endpoint for the request. Private and sensitive information is omitted from the endpoint.\nenvironmentType|Specifies the environment type for the tenant, such as Production, Sandbox, Trial. See tenant-admin-center-environments#types-of-environments.\neventId|RT0020\ntelemetrySchemaVersion|Specifies the version of the Business Central telemetry schema.\n## Authentication with web service key failed\nOccurs when a web service access key request reaches the authentication check but the user isn't authenticated. Requests rejected earlier, such as requests that use a disabled authentication method, don't emit this event.\n### General dimensions\nThe following table explains the general dimensions included in the trace. The table lists the dimensions that are specific to Business Central.\nDimension|Description or value\nmessage|Authentication with Web Service Key failed: {endpoint}\nseverityLevel|1\n### Custom dimensions\nThe following table explains the custom dimensions included in the trace.\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.\nalObjectId|Specifies the ID of the AL object in the current context, if available. The authentication event occurs before the requested object runs.\nauthenticationStatus|Failed\nauthenticationType|Specifies whether the service uses NavUserPassword or AccessControl authentication.\ncategory|Specifies the service type. Values include: Api, ODataV4, ODataV3, and SOAP.\ncomponent|Dynamics 365 Business Central Server\ncomponentVersion|Specifies the version number of the component that emits telemetry (see the component dimension.)\ndeprecatedKeys|A comma-separated list of all the keys that have been deprecated. The keys in this list are still supported but will eventually be removed in the next major release. We recommend that you update any queries that use these keys to use the new key name.\nendpoint|Specifies the endpoint for the request. Private and sensitive information is omitted from the endpoint.\nenvironmentType|Specifies the environment type for the tenant, such as Production, Sandbox, Trial. See tenant-admin-center-environments#types-of-environments.\neventId|RT0021\nfailureReason|Specifies why authentication failed. For a request whose user isn't authenticated, the value is `Not authorized.`.\ntelemetrySchemaVersion|Specifies the version of the Business Central telemetry schema.\n### Example trace\nThe following code snippet is a CustomDimensions example:\n```json\n{\"component\":\"Dynamics 365 Business Central Server\",\"category\":\"Api\",\"AadTenantId\":\"common\",\"environmentType\":\"Production\",\"Component\":\"Dynamics 365 Business Central Server\",\"AL Object Id\":\"0\",\"alObjectId\":\"0\",\"Telemetry schema version\":\"0.1\",\"telemetrySchemaVersion\":\"0.1\",\"authenticationType\":\"NavUserPassword\",\"componentVersion\":\"17.0.15855.0\",\"Component version\":\"17.0.15855.0\",\"eventId\":\"RT0021\",\"endpoint\":\"BC170/ODataV4/Company()/purchaseDocumentLines\",\"deprecatedKeys\":\"Company name, AL Object Id, AL Object type, AL Object name, AL Stack trace, Client type, Extension name, Extension App Id, Extension version, Telemetry schema version, Component, Component version, Telemetry schema version, AadTenantId, Environment name, Environment type\",\"aadTenantId\":\"common\",\"Environment type\":\"Production\",\"authenticationStatus\":\"Failed\",\"failureReason\":\"Not authorized.\"}\n```\n## Related information\nMonitoring and Analyzing Telemetry<telemetry-overview>\nEnable Sending Telemetry to Application Insights<telemetry-enable-application-insights>"}