While exploring the monitoring capabilities of Logic Apps Standard, I ran into an issue where the Runs tab in Application Insights would not display any workflow run history. Instead, it always showed the same error message indicating something was misconfigured.
This post walks you through the fix — both in Bicep (for automated deployments) and via the Azure Portal.
1. Recognizing the Problem
When opening the Runs tab in the Application Insights Monitoring view for Logic Apps Standard, you may encounter a message indicating that run history cannot be loaded.
This typically means that Telemetry is not configured correctly.
2. Step One — Ensure TelemetryVersion is Set to v2
The first step is to update your host.json file in your Logic App Standard project:
Setting TelemetryVersion to v2 is required for Logic Apps Standard to push the correct telemetry into Application Insights.
However — after fixing this, you may find that the Runs tab still does not work. That’s because one more configuration detail is missing
3. The Undocumented Fix — Add the Hidden Application Insights Tag
After some research, I discovered the missing piece:
Logic Apps Standard requires a hidden resource tag that links the Logic App to its Application Insights instance.
This tag is not documented by Microsoft, and you cannot set it through the Azure Portal.
Required Tag
- Tag name
hidden-link: /app-insights-resource-id - Tag value /subscriptions/${subscription().subscriptionId}/resourceGroups/${resourceGroup().name}/providers/microsoft.insights/components/${appInsightsName}
This hidden tag ensures that the Logic App is correctly associated with the Application Insights resource for run history visualization.
4. Adding the Tag Using Bicep (Recommended for Automated Deployments)
Update your Bicep file to include this tag under your Logic App resource:
Bicep
resource sites_logicappName_resource 'Microsoft.Web/sites@2024-11-01' = {
name: logicappName
location: location
kind: 'functionapp,workflowapp'
identity: {
type: 'SystemAssigned'
}
tags: {
'hidden-link: /app-insights-resource-id': '/subscriptions/${subscription().subscriptionId}/resourceGroups/${resourceGroup().name}/providers/microsoft.insights/components/${appInsightsName}'
}
After redeploying your Logic App, the Runs tab should now load your workflow run history correctly.
5. Alternative: Fixing It Through the Azure Portal (If Not Using Bicep)
If you’re not using Bicep, you can still achieve a working monitoring setup — but only if you configure Application Insights during Logic App creation.
Steps:
1. Create a new Logic App Standard instance.
2. In the Monitoring section, enable Application Insights.
3. Complete the deployment.
4. After deployment, ensure telemetry v2 is set in your host.json
Once configured, trigger a few workflows. You should now see your run history populated under the Runs tab.
6. Final Result
With both:
- TelemetryVersion v2 set in host.json
- The hidden Application Insights tag added
…the Runs tab in Application Insights will correctly display the workflow run history for Logic Apps Standard.
7. Reference
– By Jasper Meeusen, Cloud Integration Engineer
