Skip to content

Commit 9691a3b

Browse files
committed
update a link
1 parent 6dcd749 commit 9691a3b

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/azure-resource-manager/bicep/key-vault-parameter.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Key Vault secret with Bicep
33
description: Shows how to pass a secret from a key vault as a parameter during Bicep deployment.
44
ms.topic: conceptual
55
ms.custom: devx-track-azurepowershell, devx-track-azurecli, devx-track-bicep
6-
ms.date: 04/29/2024
6+
ms.date: 05/06/2024
77
---
88

99
# Use Azure Key Vault to pass secure parameter value during Bicep deployment
@@ -155,7 +155,7 @@ When using a key vault with the Bicep file for a [Managed Application](../manage
155155

156156
You can use the [getSecret function](./bicep-functions-resource.md#getsecret) in Bicep files to obtain a key vault secret. Note that the `getSecret` function is exclusively applicable to a `Microsoft.KeyVault/vaults` resource. Additionally, it's restricted to usage within the `params` section of a module and can only be used with parameters with the `@secure()` decorator.
157157

158-
Another function called `az.getSecret()` function can be used in Bicep parameter files to retrieve key vault secrets. For more information, see [Reference secrets in parameters file](#reference-secrets-in-parameters-file).
158+
Another function called `az.getSecret()` function can be used in Bicep parameter files to retrieve key vault secrets. For more information, see [Retrieve secrets in parameters file](#retrieve-secrets-in-parameters-file).
159159

160160
Because the `getSecret` function can only be used in the `params` section of a module. Let's create a *sql.bicep* in the same directory as the *main.bicep* file with the following content:
161161

0 commit comments

Comments
 (0)