{"title":"Analyzing permission error trace telemetry","url":"https://jonas-paprotka.de/docs/dev-itpro/administration/telemetry-permission-error-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-permission-error-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-permission-error-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 permission error telemetry in Business Central to identify missing permissions, inspect affected objects, and investigate errors reported to users.","date":"2026-11-17","meta":{"topic":"concept-article"},"outline":[{"level":1,"title":"Analyzing permission error trace telemetry","slug":"analyzing-permission-error-trace-telemetry","at":0,"chars":4443},{"level":2,"title":"Permission error shown","slug":"permission-error-shown","at":411,"chars":2561},{"level":3,"title":"General dimensions","slug":"general-dimensions","at":570,"chars":316},{"level":3,"title":"Custom dimensions","slug":"custom-dimensions","at":886,"chars":2086},{"level":2,"title":"Sample KQL code (permission error dialogs)","slug":"sample-kql-code-permission-error-dialogs","at":2972,"chars":1265},{"level":2,"title":"Related information","slug":"related-information","at":4237,"chars":206}],"text":"# Analyzing permission error trace telemetry\n> APPLIES TO: Business Central 2022 release wave 1 and later\nWhen a user gets an error dialog about lack of permissions while working in Business Central, a telemetry signal is emitted. This signal can be logged in an Application Insights resource.\nThis telemetry data lets you identify and analyze permission problems that users may experience in Business Central.\n## Permission error shown\nOccurs when a user gets a permissions-related error message in Business Central when they try to do an operation in the application.\n### General dimensions\nDimension|Description or value\nmessage|Permission error shown\nseverityLevel|1\nuser_Id|The user telemetry ID for the user. From the user card, you can use user_Id to identify the user who triggered this telemetry event. See telemetry-enable-application-insights#assign-a-telemetry-id-to-users.\n### Custom dimensions\nDimension|Description or value\neventId|RT0031\naadTenantId|The Microsoft Entra tenant ID that's used for Microsoft Entra authentication. For on-premises, if you aren't using Microsoft Entra authentication, this value is common.\nalObjectId|If there's no value or the value is 0, then the permission error wasn't related to a specific object, which typically happens when permissionArea is something other than Object.\nalObjectName|The name of the AL object that the user was trying to access, like a table or page.\nalObjectType|The type of the AL object that the user was trying to access, like a table or page.\nalStackTrace|The stack trace in AL.\nclientType|The type of client that attempted the operation, such as Background or WebClient. See ClientType option type<../developer/methods-auto/clienttype/clienttype-option>.\ncompanyName|The display name of the Business Central company that was used at time of execution\ncomponent|Dynamics 365 Business Central Server\ncomponentVersion|The version number of the component that emits telemetry (see the component dimension)\nenvironmentName|The name of the tenant environment. This dimension isn't included for Business Central on-premises environments. See Managing environments<tenant-admin-center-environments>.\nenvironmentType|The environment type for the tenant, such as Production, Sandbox, Trial. See tenant-admin-center-environments#types-of-environments.\nerrorMessage|The permission error message, with private information removed.\nextensionName|Specifies the name of the extension/app.\nextensionPublisher|Specifies the publisher of the extension/app.\nextensionVersion|Specifies the version of the extension.\nextensionId|Specifies the ID of the extension/app.\npermissionArea|The area that the permission error is related to. Possible values include: System, Entitlement, Company, Object.\npermissionType|The permission that the operation requires, but the user lacks. Possible values: Delete, Execute, Insert, Modify, Read, Undefined\ntelemetrySchemaVersion|The version of the Business Central telemetry schema.\n## Sample KQL code (permission error dialogs)\nThis KQL code can help you get started analyzing which permission error dialogs users see:\n```kql\ntraces\n| where timestamp > ago(60d) // adjust as needed\n| where customDimensions.eventId == 'RT0031'\n| project timestamp\n// in which environment/company did it happen\n, aadTenantId = customDimensions.aadTenantId\n, environmentName = customDimensions.environmentName\n, environmentType = customDimensions.environmentType\n, companyName = customDimensions.companyName\n// in which extension/app\n, extensionId = customDimensions.extensionId\n, extensionName = customDimensions.extensionName\n, extensionVersion = customDimensions.extensionVersion\n, extensionPublisher = customDimensions.extensionPublisher\n// in which object\n, alObjectId = customDimensions.alObjectId\n, alObjectName = customDimensions.alObjectName\n, alObjectType = customDimensions.alObjectType\n// which user got the error\n, usertelemetryId = case(\n  toint( substring(customDimensions.componentVersion,0,2)) >= 20, user_Id // user telemetry id was introduced in the platform in version 20.0\n, 'N/A'\n)\n// error information\n, clientType = customDimensions.clientType\n, errorMessage = customDimensions.errorMessage\n, alStackTrace = customDimensions.alStackTrace\n```\n## Related information\n../developer/devenv-upgrading-extensions\nMonitoring and Analyzing Telemetry<telemetry-overview>\nEnable Sending Telemetry to Application Insights<telemetry-enable-application-insights>"}