|
2 | 2 | title: Template functions - resources
|
3 | 3 | description: Describes the functions to use in an Azure Resource Manager template (ARM template) to retrieve values about resources.
|
4 | 4 | ms.topic: conceptual
|
5 |
| -ms.date: 08/22/2023 |
| 5 | +ms.date: 03/18/2024 |
6 | 6 | ms.custom: devx-track-arm-template
|
7 | 7 | ---
|
8 | 8 |
|
@@ -143,7 +143,7 @@ The possible uses of `list*` are shown in the following table.
|
143 | 143 | | Microsoft.BatchAI/workspaces/experiments/jobs | listoutputfiles |
|
144 | 144 | | Microsoft.BotService/botServices/channels | [listChannelWithKeys](https://github.com/Azure/azure-rest-api-specs/blob/master/specification/botservice/resource-manager/Microsoft.BotService/stable/2020-06-02/botservice.json#L553) |
|
145 | 145 | | Microsoft.Cache/redis | [listKeys](/rest/api/redis/redis/list-keys) |
|
146 |
| -| Microsoft.CognitiveServices/accounts | [listKeys](/rest/api/cognitiveservices/accountmanagement/accounts/listkeys) | |
| 146 | +| Microsoft.CognitiveServices/accounts | [listKeys](/rest/api/aiservices/accountmanagement/accounts/list-keys) | |
147 | 147 | | Microsoft.ContainerRegistry/registries | [listBuildSourceUploadUrl](/rest/api/containerregistry/registries%20(tasks)/get-build-source-upload-url) |
|
148 | 148 | | Microsoft.ContainerRegistry/registries | [listCredentials](/rest/api/containerregistry/registries/listcredentials) |
|
149 | 149 | | Microsoft.ContainerRegistry/registries | [listUsages](/rest/api/containerregistry/registries/listusages) |
|
@@ -414,7 +414,7 @@ In the templates with [symbolic names](./resource-declaration.md#use-symbolic-na
|
414 | 414 |
|
415 | 415 | `reference(symbolicName or resourceIdentifier, [apiVersion], ['Full'])`
|
416 | 416 |
|
417 |
| -Returns an object representing a resource's runtime state. To return an array of objects representing a resource collections's runtime states, see [references](#references). |
| 417 | +Returns an object representing a resource's runtime state. The output and behavior of the `reference` function highly relies on how each resource provider (RP) implements its PUT and GET responses. To return an array of objects representing a resource collections's runtime states, see [references](#references). |
418 | 418 |
|
419 | 419 | Bicep provide the reference function, but in most cases, the reference function isn't required. It's recommended to use the symbolic name for the resource instead. See [reference](../bicep/bicep-functions-resource.md#reference).
|
420 | 420 |
|
|
0 commit comments