Label is ignored/incorrect in resource picker parameter (from JSON)

[johschmidt42]

Hi,

I've followed the documentation: Create a JSON list resource parameter (Content source) to create a parameter of type Resource picker. The name of the parameter is Applications and the data comes from a JSON list with labels defined (content is the one from the example):

[
    { "value":"/subscriptions/<sub-id>/resourceGroups/<resource-group>/providers/<resource-type>/acmeauthentication", "label": "acmeauthentication", "selected":true, "group":"Acme Backend" },
    { "value":"/subscriptions/<sub-id>/resourceGroups/<resource-group>/providers/<resource-type>/acmeweb", "label": "acmeweb", "selected":false, "group":"Acme Frontend" }
]

In the next Resource parameter options section, the value for {Applications:label} is shown to be acmefrontend. However, all I get in the preview AND when used in a query is this: /subscriptions/<sub-id>/resourceGroups/<resource-group>/providers/<resource-type>/acmeauthentication

This query

traces
| where message == {Applications:label}

is translated to this:

traces
| where message == /subscriptions/<sub-id>/resourceGroups/<resource-group>/providers/<resource-type>/acmeauthentication

All works fine if the type is changed to Dropdown, however, for my workbook I really need the Resource picker type. This is incredibly frustrating..

---

Document Details

⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

• ID: 8961ac12-6dfd-7ff9-373f-cd45d779122d
• Version Independent ID: fdd7bf95-c008-744c-432a-1b38bc10cddb
• Content: Azure Monitor workbook resource parameters - Azure Monitor
• Content Source: articles/azure-monitor/visualize/workbooks-resources.md
• Service: azure-monitor
• Sub-service: visualizations
• GitHub Login: @AbbyMSFT
• Microsoft Alias: abbyweisberg

[TPavanBalaji]

@johschmidt42 Thanks for your feedback! We will investigate and update as appropriate.

[AnuragSingh-MSFT]

@johschmidt42 thank you for the feedback.

@AbbyMSFT, could you please review this and share your thoughts. Thank you

[AnuragSingh-MSFT]

@johschmidt42, upon further review of the issue it appears that this is not primarily related to the doc. We use GitHub issues as the primary channel for customer and community feedback about the Azure documentation.

Could you please post this question on Microsoft Q&A, so that our technical community can review it and help with this issue.

Apologies for the inconvenience.