Restrictions Not Displayed in 'Default Value' Section

[influential-eliot]

Restrictions For 'Default Value' Are Non-Existent Or Unclear

I would suggest that the restrictions on the Default Value are a bit too obfuscated and/or unlisted here.

A validation problem (at least when using VS Code - latest) occurs when attempting to use a Variable in the Default Value.

If this is a restricted ability, then it should be shown as such at the top of the Default Value section, perhaps in an ℹ️ panel, or something.

Clarification: I am not raising a validation incident here, merely raising that if such behaviour is restricted, then it should be displayed in the document.

---

Example

For example, let's say that I have the following parameters and variables:

{
    "parameters": {
        "environment": {
          "defaultValue": "[variables('env')]",
          "type": "String"
        }
    },
    "variables": {
        "env": "Some_text"
    }
}

This will produce a validation error akin to:

Template validation failed: The template resource 'environment' at ... is not valid: The template function 'variables' is not expected at this location.

This also occurs when wrapping a string() function around the variables() call in the defaultValue.

Further Details

There is a line which states the following:

You can't use the reference function or any of the list functions in the parameters section.

However that doesn't state that using a variable in a defaultValue will fail template validation.

---

Document Details

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

• ID: 4fc492d5-0ea7-dea9-5a16-0f4f9f16891c
• Version Independent ID: f977075c-5ff7-eff2-a9b6-aabc6669a39b
• Content: Parameters in templates - Azure Resource Manager
• Content Source: articles/azure-resource-manager/templates/parameters.md
• Service: azure-resource-manager
• Sub-service: templates
• GitHub Login: @mumian
• Microsoft Alias: jgao

[PesalaPavan]

@influential-eliot Thanks for your feedback! We will investigate and update as appropriate.

[AnuragSingh-MSFT]

@influential-eliot, thank you for the feedback.

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