Workbook opened via direct Azure Workbooks resource link shows "Query failed: could not connect to server" for a second user, but works when opened from the Application Insights resource

Question

Workbook opened via direct Azure Workbooks resource link shows "Query failed: could not connect to server" for a second user, but works when opened from the Application Insights resource

Gopi 0 Microsoft External Staff

We have an Azure Monitor Workbook charting from an Application Insights component. It works fully for the author. A second user needs to open it directly via the Azure Workbooks resource link and have all query tiles load.

Symptom: The second user can see the workbook (layout, titles, parameters all render), but every query tile fails with "Query failed: could not connect to server." This happens only when opening the standalone Azure Workbooks / Azure Monitor resource link. When the same workbook is opened from within the Application Insights resource → Workbooks, all queries run fine for the same user. And the same workbook works from everywhere for remaining users.

Correct directory selected, subscription visible in the portal subscription filter, and closing/reopening the tab does not help.

Pilladi Padma Sai Manisha 11,605 Reputation points Microsoft External Staff Moderator

2026-07-17T22:55:03.5433333+00:00

Hi @Gopi
Based on the information provided, the workbook itself appears to be functioning correctly because it works for the author, the affected user can successfully run the workbook when opening it from the Application Insights → Workbooks blade, and other users can access it from both entry points without any issues.

Since the issue occurs only for one user when opening the workbook through the standalone Azure Workbooks resource link, it is likely related to how the portal is resolving the workbook context for that specific user rather than a problem with the workbook queries themselves.

Please verify that the affected user has the appropriate RBAC permissions on both the Azure Workbook resource and the associated Application Insights (or Log Analytics workspace, if applicable). Also, review the workbook queries to ensure they explicitly reference the intended Application Insights resource instead of relying on the current portal context.

Additionally, ask the affected user to reproduce the issue in an InPrivate/Incognito browser session after signing out and back into the Azure portal, ensuring the correct tenant and subscription are selected.

If the issue continues after these checks, please capture a HAR trace and the browser console logs while reproducing the problem. These logs will help identify whether the failure is due to an authorization issue or a portal context resolution problem and will be useful for further investigation.
Pilladi Padma Sai Manisha 11,605 Reputation points Microsoft External Staff Moderator

2026-07-21T22:20:14.9966667+00:00

Hi @Gopi
We haven't heard back from you. Please reply if you have any questions in this matter and we will gladly continue the discussion.
Gopi 0 Reputation points Microsoft External Staff

2026-07-21T23:23:07.0333333+00:00

Hi @Pilladi Padma Sai Manisha ,

The user has Owner access at the subscription level, and I verified that for the referenced Application insights component user has that inherited owner permissions only and only this user having this access issue but the other user with inherited reader permissions can access without issues directly from the same workbook share link.

I also asked user to reproduce in private browser window and if still continues, asked user to share the HAR trace as you mentioned above in the comment. I have shared the HAR trace file with you over teams.

1 answer

Your answer

Pilladi Padma Sai Manisha 11,605 Reputation points Microsoft External Staff Moderator

2026-07-17T22:55:03.5433333+00:00

Hi @Gopi
Based on the information provided, the workbook itself appears to be functioning correctly because it works for the author, the affected user can successfully run the workbook when opening it from the Application Insights → Workbooks blade, and other users can access it from both entry points without any issues.

Since the issue occurs only for one user when opening the workbook through the standalone Azure Workbooks resource link, it is likely related to how the portal is resolving the workbook context for that specific user rather than a problem with the workbook queries themselves.

Please verify that the affected user has the appropriate RBAC permissions on both the Azure Workbook resource and the associated Application Insights (or Log Analytics workspace, if applicable). Also, review the workbook queries to ensure they explicitly reference the intended Application Insights resource instead of relying on the current portal context.

Additionally, ask the affected user to reproduce the issue in an InPrivate/Incognito browser session after signing out and back into the Azure portal, ensuring the correct tenant and subscription are selected.

If the issue continues after these checks, please capture a HAR trace and the browser console logs while reproducing the problem. These logs will help identify whether the failure is due to an authorization issue or a portal context resolution problem and will be useful for further investigation.
Pilladi Padma Sai Manisha 11,605 Reputation points Microsoft External Staff Moderator

2026-07-21T22:20:14.9966667+00:00

Hi @Gopi
We haven't heard back from you. Please reply if you have any questions in this matter and we will gladly continue the discussion.
Gopi 0 Reputation points Microsoft External Staff

2026-07-21T23:23:07.0333333+00:00

Hi @Pilladi Padma Sai Manisha ,

The user has Owner access at the subscription level, and I verified that for the referenced Application insights component user has that inherited owner permissions only and only this user having this access issue but the other user with inherited reader permissions can access without issues directly from the same workbook share link.

I also asked user to reproduce in private browser window and if still continues, asked user to share the HAR trace as you mentioned above in the comment. I have shared the HAR trace file with you over teams.

Answer 1

Christos Panagiotidis 3,301

The standalone link may not supply the Application Insights context that the resource blade supplies. Seeing the layout only proves the user can read the workbook; each query needs data-source permission and a resource scope.

Grant read access to the workbook and referenced Application Insights component. If it is workspace-based, verify the Log Analytics access mode and grant the required query/read role at the resource or workspace scope.

Edit the workbook and inspect failing queries. If the resource is “current resource” or inherited, create a Resource parameter defaulting to the Application Insights resource ID, then bind every query. Save and retest the standalone link in a portal session.

If only this user still fails, open the failed tile’s details and capture its correlation ID. This distinguishes missing context from an RBAC denial. Since the user succeeds from the Application Insights blade, explicit resource binding is the first difference to test.

Gopi 0 Reputation points Microsoft External Staff

2026-07-20T17:45:36.9933333+00:00

The user has Owner access at the subscription level, and I verified that for the referenced Application insights component user has that inherited owner permissions only and only this user having this access issue but the other user with inherited reader permissions can access without issues directly from the same workbook share link.