Azure / Azure/AzureMonitor

Are Azure Workbook capabilities versioned based upon subscription age (version)?

Open
#10 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
No language data
Stars
1
Forks
8
PR merge metrics
No merged PRs in 30d

Description

We are building Workbooks inside Application Insights (not the Azure Monitor Workbook gallery), and we are consistently missing capabilities that appear in Microsoft documentation and examples.
Our subscription was created in 2016, and Copilot suggests that older subscriptions may still be running a legacy Workbook host that does not receive newer features.

Here are the specific limitations we are encountering

1. No ability to place tiles side‑by‑side
In the Workbook editor inside Application Insights:
- There is no option to create column layouts
- No “Add group above”
- No drag‑and‑drop
- No layout selector
- All visualizations stack vertically
We would like to place a dropdown in the left column and a graph in the right column, with a full‑width table below — but the UI does not support any horizontal layout.

2. Missing parameter capabilities
Documentation shows support for:
- Default value
- Default value query
- “Pick first item” behavior
- Parameter binding
However, in our environment, the parameter editor does not include these fields.
Dropdowns always remember the last‑used value and cannot be configured to select the most recent item.

3. Restricted placement inside the Azure UI
Workbooks created inside Application Insights:
- Cannot be moved to the Azure Monitor Workbook gallery
- Cannot be pinned with full fidelity to dashboards
- Appear to use an older UI and feature set
This suggests the Application Insights Workbook host may be running on an older engine.

Question
Is the Workbook experience inside Application Insights intentionally running on a legacy version of the Workbook engine?
If so:
- Is this tied to subscription age, region, or resource type?
- Are there plans to update the Application Insights Workbook host to match the capabilities shown in current documentation?
We want to confirm whether these limitations are expected or if our environment is misconfigured.
Thank you for any clarification you can provide

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.