|
| 1 | +--- |
| 2 | +title: Troubleshoot Work Item Integration Issues in Application Insights |
| 3 | +description: Provides general recommendations and specific suggestions for issues with work item integration in Application Insights. |
| 4 | +ms.date: 10/28/2025 |
| 5 | +ms.service: azure-monitor |
| 6 | +ms.custom: sap:Application Insights portal experiences |
| 7 | +--- |
| 8 | +# Troubleshoot work item integration issues in Application Insights |
| 9 | + |
| 10 | +[Work item integration](/azure/azure-monitor/app/work-item-integration) in Application Insights might not work as expected. This article offers general recommendations and specific troubleshooting steps. |
| 11 | + |
| 12 | +## Create work item doesn't appear in end-to-end transaction details |
| 13 | + |
| 14 | +First, create a template or start with **Start with a workbook template** from the **Create a work item** flow. |
| 15 | + |
| 16 | +## On-premises Azure DevOps URL is rejected |
| 17 | + |
| 18 | +To match your host, update the workbook's repository URL text parameter and its validation rule (regular expression). |
| 19 | + |
| 20 | +## Authorization prompt doesn't appear or linking fails |
| 21 | + |
| 22 | +Confirm that popup blockers are disabled for the Azure portal and that your browser allows third-party cookies. Then try linking again. |
| 23 | + |
| 24 | +## Work item creation fails with permission errors** |
| 25 | + |
| 26 | +Verify that your Azure DevOps or GitHub account has permission to create issues or work items in the selected repository or project. You might need **Contribute** (DevOps) or **Write** (GitHub) permissions. |
| 27 | + |
| 28 | +## Template fails to load or save |
| 29 | + |
| 30 | +Ensure the selected region supports the `Microsoft.Insights/workbooks` resource type and that your role includes `Microsoft.Insights/workbooks/write`. Try saving in a different region if necessary. |
| 31 | + |
| 32 | +## Contextual data missing from created work items |
| 33 | + |
| 34 | +Check that the Kusto Query Language (KQL) section of the workbook template returns data in the expected schema. If fields were renamed or the resource ID changed, update the query or bindings. |
| 35 | + |
| 36 | +## Template not visible to other users |
| 37 | + |
| 38 | +Workbook-based templates are stored as Azure resources. Ensure the resource is in a shared resource group and that other users have at least **Reader** access to that resource. |
| 39 | + |
| 40 | +## Template deletion doesn't remove existing links |
| 41 | + |
| 42 | +Removing the workbook doesn't automatically clear cached configuration. Refresh the **Work Items** blade in Application Insights or clear your browser cache to update the list. |
| 43 | + |
| 44 | +## GitHub issue or DevOps item opens in wrong repository/project |
| 45 | + |
| 46 | +Open the workbook and confirm the default repository or organization URL parameter is set correctly. If you have multiple templates, check which is currently linked to the resource. |
| 47 | + |
| 48 | +[!INCLUDE [Azure Help Support](../../../includes/azure-help-support.md)] |
0 commit comments