|
| 1 | +--- |
| 2 | +title: Troubleshoot Work Item Integration Issues in Application Insights |
| 3 | +description: Provides general recommendations and specific suggestions for issues that affect work item integration in Application Insights. |
| 4 | +author: JarrettRenshaw |
| 5 | +ms.author: jarrettr |
| 6 | +manager: dcscontentpm |
| 7 | +ms.topic: troubleshooting |
| 8 | +ms.date: 10/28/2025 |
| 9 | +ms.service: azure-monitor |
| 10 | +ms.custom: sap:Application Insights portal experiences |
| 11 | +ms.reviewer: v-ryanberg, v-gsitser |
| 12 | +--- |
| 13 | +# Troubleshoot work item integration issues in Application Insights |
| 14 | + |
| 15 | +[Work item integration](/azure/azure-monitor/app/work-item-integration) in Application Insights enables you to create and link work items directly from telemetry data. If this feature isn't working as expected, the following guidance helps you to diagnose and resolve common issues. |
| 16 | + |
| 17 | +## The "Create work item" option doesn't appear in transaction details |
| 18 | + |
| 19 | +If you don't see the option to create a work item, it's likely that integration wasn't enabled or the resource isn't linked to Azure DevOps or GitHub. |
| 20 | + |
| 21 | +**What to do:** |
| 22 | + |
| 23 | +1. In Application Insights, navigate to **Work Items**, and verify that integration settings are configured. |
| 24 | +1. Start the process from the **Create a work item** flow, or use a workbook template. |
| 25 | + |
| 26 | +## On-premises Azure DevOps URL rejected |
| 27 | + |
| 28 | +This issue occurs if the URL format doesn't meet validation requirements. |
| 29 | + |
| 30 | +**What to do:** |
| 31 | + |
| 32 | +* Make sure that the URL uses the HTTPS protocol and matches the validation rule in the workbook parameter. |
| 33 | +* If you're using a self-hosted Azure DevOps instance, make sure that it's accessible from the Azure portal. |
| 34 | + |
| 35 | +## Authorization prompt doesn't appear or linking fails |
| 36 | + |
| 37 | +If you don't see the authorization prompt, or if linking fails, the cause might be a pop-up blocker or cached tokens. |
| 38 | + |
| 39 | +**What to do:** |
| 40 | + |
| 41 | +* Disable pop-up blockers and allow third-party cookies in your browser. |
| 42 | +* Clear your browser cache, and then try again to link. |
| 43 | +* If you're using OAuth, verify that the required scopes are granted. |
| 44 | + |
| 45 | +## Work item creation fails and returns permission errors |
| 46 | + |
| 47 | +Permission errors usually indicate that your account doesn't have sufficient rights in Azure DevOps or GitHub. |
| 48 | + |
| 49 | +**What to do:** |
| 50 | + |
| 51 | +* For Azure DevOps, ensure you have *Contribute* permissions. |
| 52 | +* For GitHub, confirm you have *Write* access to the repository. |
| 53 | +* If you're using a Personal Access Token (PAT), make sure it includes the *Work Items (read/write)* scope. |
| 54 | + |
| 55 | +## Template doesn't load or save |
| 56 | + |
| 57 | +This issue typically occurs because of region limitations or missing permissions. |
| 58 | + |
| 59 | +**What to do:** |
| 60 | + |
| 61 | +* Verify that the region supports the *Microsoft.Insights/workbooks* resource type. |
| 62 | +* Check that the resource provider is registered in your subscription. |
| 63 | +* Assign the *Microsoft.Insights/workbooks/write* role, or try saving the template in a supported region. |
| 64 | + |
| 65 | +## Contextual data is missing from created work items |
| 66 | + |
| 67 | +If the work item doesn't include expected data, the Kusto Query Language (KQL) query might not return the correct schema. |
| 68 | + |
| 69 | +**What to do:** |
| 70 | + |
| 71 | +* Run the query in **Logs** to verify the output fields. |
| 72 | +* Update the query or bindings to match the expected schema. |
| 73 | + |
| 74 | +## Template isn't visible to other users |
| 75 | + |
| 76 | +This issue usually occurs if the template is saved as private, or if role-based access control (RBAC) permissions are insufficient. |
| 77 | + |
| 78 | +**What to do:** |
| 79 | + |
| 80 | +* Make sure that the template is stored in a shared resource group and not saved as *My Reports*. |
| 81 | +* Grant other users at least *Reader* access to the resource. |
| 82 | + |
| 83 | +## Deleting a template doesn't remove existing links |
| 84 | + |
| 85 | +Removing a workbook doesn't automatically clear cached configuration. |
| 86 | + |
| 87 | +**What to do:** |
| 88 | + |
| 89 | +* Refresh the **Work Items** pane in Application Insights or clear your browser cache. |
| 90 | +* If links persist, manually unlink them in the resource settings. |
| 91 | + |
| 92 | +## GitHub issue or Azure DevOps item opens in the wrong repository or project |
| 93 | + |
| 94 | +This issue occurs if the default repository or organization URL is incorrect or multiple templates override settings. |
| 95 | + |
| 96 | +**What to do:** |
| 97 | + |
| 98 | +* Open the workbook, and verify the default repository or organization URL parameter. |
| 99 | +* Remove or update conflicting templates. |
| 100 | + |
| 101 | +[!INCLUDE [Azure Help Support](../../../includes/azure-help-support.md)] |
| 102 | + |
| 103 | +[!INCLUDE [Third-party contact disclaimer](~/includes/third-party-contact-disclaimer.md)] |
0 commit comments