Skip to content

Commit 7d0e0e1

Browse files
committed
update
1 parent 97285ed commit 7d0e0e1

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

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

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -609,7 +609,7 @@ The following example template references a storage account that isn't deployed
609609

610610
`reference(symbolic name of a resource collection, ['Full'])`
611611

612-
`references` works similarly as [`reference`](#reference). In stead of returning an object presenting a resource's runtime state, 'references` returns an array of objects representing a collection of resource's runtime states. This function requires ARM template language version `1.10-experimental` and with [symbolic name](../bicep/file.md#resources) enabled:
612+
The `references` function works similarly as [`reference`](#reference). In stead of returning an object presenting a resource's runtime state, the `references` function returns an array of objects representing a collection of resource's runtime states. This function requires ARM template language version `1.10-experimental` and with [symbolic name](../bicep/file.md#resources) enabled:
613613

614614
```json
615615
{
@@ -620,13 +620,13 @@ The following example template references a storage account that isn't deployed
620620
}
621621
```
622622

623-
In Bicep, there is no explicit `references` function like [`reference`](../bicep/bicep-functions-resource.md#reference). Instead, symbolic collection usage is employed directly, and during code generation, Bicep translates it to an ARM template that utilizes the ARM template `references` function. The forthcoming release of Bicep will include a translation feature that converts symbolic collections to ARM templates using the references() function.
623+
In Bicep, there is no explicit `references` function. Instead, symbolic collection usage is employed directly, and during code generation, Bicep translates it to an ARM template that utilizes the ARM template `references` function. The forthcoming release of Bicep will include the translation feature that converts symbolic collections to ARM templates using the `references` function.
624624

625625
### Parameters
626626

627627
| Parameter | Required | Type | Description |
628628
|:--- |:--- |:--- |:--- |
629-
| Symbolic name of a resource collection |Yes |string |Symbolic name of a resource collection that is defined in the current template. |
629+
| Symbolic name of a resource collection |Yes |string |Symbolic name of a resource collection that is defined in the current template. The `references`` function does not support referencing resources external to the current template. |
630630
| 'Full' |No |string |Value that specifies whether to return an array of the full resource objects. The default value is `'Full'`. If you don't specify `'Full'`, only the properties objects of the resources are returned. The full object includes values such as the resource ID and location. |
631631

632632
### Return value

0 commit comments

Comments
 (0)