Skip to content

Commit 57c824e

Browse files
committed
update
1 parent 7becf7d commit 57c824e

1 file changed

Lines changed: 4 additions & 4 deletions

File tree

articles/azure-resource-manager/templates/template-expressions.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -14,15 +14,15 @@ A template expression can't exceed 24,576 characters.
1414

1515
## Compile-time constrains
1616

17-
Template expressions are evaluated at runtime, but some properties in ARM templates and Bicep files must be known at compile time and therefore can't use expressions. These properties include:
17+
Template expressions are evaluated at runtime, but certain properties in ARM templates must be known at compile time and therefore cannot use expressions. These properties must be specified as literal strings so the deployment engine and compiler can validate resource schemas, dependencies, and supported properties before any expressions are evaluated.
18+
19+
Properties that must be compile-time literals include:
1820

1921
- The `type` and `apiVersion` of a resource.
2022
- The `name` of variables, parameters, and outputs.
2123
- Extension references.
2224

23-
These properties must be provided as literal strings because the deployment engine and compiler need to validate resource schemas, dependencies, and properties before evaluating expressions.
24-
25-
The following ARM template failed becasue the `type` property of the resource uses an expression:
25+
The following ARM template failed because the `type` property of the resource uses an expression:
2626

2727
```json
2828
{

0 commit comments

Comments
 (0)